Grammar, tone, spelling, and typography pass (jf: 1/x) (#2512)

* Update javascript-v3-as-skill.md

* wip

* Update bot-service-channel-directline-extension-net-bot.md

* Incorporate Emily's feedback.

* Fix Markdown.

* Update bot-service-channel-directline-extension-net-bot.md

Co-authored-by: Emily Olshefski <[email protected]>

articles/bot-service-channel-directline-extension-net-bot.md

@@ -1,7 +1,7 @@
 ---
-title: .NET bot with direct line app service extension
+title: .NET bot with Direct Line App Service extension
 titleSuffix: Bot Service
-description: Learn how to configure .NET bots to work with named pipes. See how to enable direct line app service extensions and how to configure bots to use the extensions.
+description: Learn how to configure .NET bots to work with named pipes. See how to enable the Direct Line App Service extension and how to configure bots to use the extension.
 services: bot-service
 manager: kamrani
 ms.service: bot-service
@@ -14,29 +14,28 @@ ms.date: 01/16/2020
 
 [!INCLUDE [applies-to-v4](includes/applies-to-v4-current.md)]
 
-This article describes how to update a bot to work with **named pipes**, and how to enable the Direct Line app service extension in the **Azure App Service** resource where the bot is hosted.
+This article describes how to update a bot to work with named pipes, and how to enable the Direct Line App Service extension in the Azure App Service resource where the bot is hosted.
 
 ## Prerequisites
 
-To perform the steps described next, you need to have a **Web App Bot**(your bot) created in Azure.
+To perform the steps described next, you need to have a web app bot created in Azure.
 
-## Enable Direct Line app service extension
+## Enable Direct Line App Service extension
 
-This section describes how to enable the Direct Line app service extension using the app service extension key from your bot's Direct Line channel configuration.
+This section describes how to enable the Direct Line App Service extension using the App Service extension key from your bot's Direct Line channel configuration.
 
 ### Update bot code
 
 > [!NOTE]
-> `Microsoft.Bot.Builder.StreamingExtensions` preview packages have been deprecated. The SDK v4.8 now contains the [Streaming library](https://github.com/microsoft/botbuilder-dotnet/tree/master/libraries/Microsoft.Bot.Builder/Streaming). If a bot previously made use of the preview packages they must be removed before following the steps below.
+> The **Microsoft.Bot.Builder.StreamingExtensions** NuGet preview packages have been deprecated. Starting with v4.8, the SDK contains a `Microsoft.Bot.Builder.Streaming` namespace. If a bot previously made use of the preview packages they must be removed before following the steps below.
 
 1. In Visual Studio, open your bot project.
-1. Make sure the project uses version 4.8 or higher of the Bot Builder SDK.
-1. Allow your app to use the **Bot Framework NamedPipe**:
-    - Open the `Startup.cs` file.
-    - In the ``Configure`` method, add code to ``UseNamedPipes``
+1. Make sure the project uses version 4.8 or later of the Bot Framework SDK.
+1. Allow your app to use named pipes:
+    - Open the **Startup.cs** file.
+    - In the `Configure` method, add a call to the `UseNamedPipes` method.
 
     ```csharp
-
     public void Configure(IApplicationBuilder app, IHostingEnvironment env)
     {
         if (env.IsDevelopment())
@@ -58,88 +57,84 @@ This section describes how to enable the Direct Line app service extension using
     }
     ```
 
-1. Save the `Startup.cs` file.
+1. Save the **Startup.cs** file.
 
-1. **Publish** the bot to your Azure Web App Bot resource to deploy the updated code.
+1. Publish the bot to your Azure web app bot resource to deploy the updated code.
 
-### Enable bot Direct Line app service extension
+### Enable bot Direct Line App Service extension
 
 1. In the Azure portal, locate your **Web App Bot** resource.
-1. From the left panel menu under *Bot management* click on **Channels** to configure the **Azure Bot Service** channels your bot accepts messages from.
+1. From the left panel menu under **Bot management** click on **Channels** to configure the **Azure Bot Service** channels your bot accepts messages from.
 1. If it is not already enabled, click on the **Direct Line** channel and follow instructions to enable the channel.
-1. In the **Connect to channels** table click on the **Edit** link on the Direct Line row.
-1. Scroll down to the **App Service Extension Keys** section.
-1. Click on the **Show** link to reveal one of the keys. You will use this value in the steps below.
+1. In the **Connect to channels** table click on the **Edit** link on the **Direct Line** row.
+1. Scroll down to the **App Service extension Keys** section.
+1. Click on the **Show** link to reveal one of the keys. Copy this value for use later.
 
-    ![App service extension keys](./media/channels/direct-line-extension-extension-keys.png)
+    ![App Service extension keys](./media/channels/direct-line-extension-extension-keys.png)
 
-1. Navigate to the home page, click the **App Services** icon at the top of the page. You can also display the portal menu, and then click the **App Services** menu item, in the left panel. The  App Services page is displayed.
+1. Navigate to the home page, click the **App Services** icon at the top of the page. You can also display the portal menu, and then click the **App Services** menu item, in the left panel. The **App Services** page is displayed.
 1. In the search box enter your **Web App Bot** resource name. Your resource will be listed.
-Notice that if you mouseover the icon or the menu item, you get the list of the last resources you viewed. Chances are your **Web App Bot** resource will be listed.
+Notice that if you hover over the icon or the menu item, you get the list of the last resources you viewed. Chances are your **Web App Bot** resource will be listed.
 1. Click your resource link.
 1. In the **Settings** section, click the **Configuration** menu item.
 1. In the right panel, add the following new settings:
 
     |Name|Value|
     |---|---|
-    |DirectLineExtensionKey|<App_Service_Extension_Key>|
+    |DirectLineExtensionKey|The value of the App Service extension key you copied earlier.|
     |DIRECTLINE_EXTENSION_VERSION|latest|
 
-    Where the *App_Service_Extension_Key* is the value you saved earlier.
-
-1. If your bot is hosted in a sovereign or otherwise restricted Azure cloud (i.e. you do not access Azure via the [public portal](https://portal.azure.com)) you will also need to add the following new setting:
+1. If your bot is hosted in a sovereign or otherwise restricted Azure cloud, where you don't access Azure via the [public portal](https://portal.azure.com), you will also need to add the following new setting:
 
     |Name|Value|
     |---|---|
-    |DirectLineExtensionABSEndpoint|<URL_of_Direct_Line_App_Gateway>|
-
-    Where *URL_of_Direct_Line_App_Gateway* is specific to the Azure cloud your bot is hosted in. For USGov this value is `https://directline.botframework.azure.us/v3/extension`.
+    |DirectLineExtensionABSEndpoint|The endpoint specific to the Azure cloud your bot is hosted in. For the USGov cloud for example, the endpoint is `https://directline.botframework.azure.us/v3/extension`.|
 
-1. Still within the *Configuration* section, click on the **General** settings section and turn on **Web sockets**
+1. Still within the **Configuration** section, click on the **General** settings section and turn on **Web sockets**.
 1. Click on **Save** to save the settings. This restarts the Azure App Service.
 
-## Confirm Direct Line app extension and the bot are configured
+## Confirm the extension and the bot are configured
 
 In your browser, navigate to `https://<your_app_service>.azurewebsites.net/.bot`.
-If everything is correct, the page will return this JSON content: `{"v":"123","k":true,"ib":true,"ob":true,"initialized":true}`. This is the information you obtain when **everything works correctly**, where
+If everything is correct, the page will return this JSON content: `{"v":"123","k":true,"ib":true,"ob":true,"initialized":true}`. This is the information you obtain when *everything works correctly*, where
 
-- **v** displays the build version of the Direct Line App Service Extension (ASE).
-- **k** determines whether Direct Line ASE can read an App Service Extension Key from its configuration.
-- **initialized** determines whether Direct Line ASE can use the App Service Extension Key to download the bot metadata from Azure Bot Service
-- **ib** determines whether Direct Line ASE can establish an inbound connection with the bot.
-- **ob** determines whether Direct Line ASE can establish an outbound connection with the bot.
+- **v** displays the build version of the Direct Line App Service extension.
+- **k** determines whether the extension can read an extension key from its configuration.
+- **initialized** determines whether the extension can use the extension key to download the bot metadata from Azure Bot Service.
+- **ib** determines whether the extension can establish an inbound connection with the bot.
+- **ob** determines whether the extension can establish an outbound connection with the bot.
 
 ## Troubleshooting
 
-- If the *ib* and *ob* values displayed by the **.bot endpoint* are false this means the bot and the Direct Line app service extension are unable to connect to each other.
+- If the **ib** and **ob** values displayed by the **.bot endpoint** are false this means the bot and the Direct Line App Service extension are unable to connect to each other.
     1. Double check the code for using named pipes has been added to the bot.
     1. Confirm the bot is able to start up and run at all. Useful tools are **Test in WebChat**, connecting an additional channel, remote debugging, or logging.
     1. Restart the entire **Azure App Service** the bot is hosted within, to ensure a clean start up of all processes.
 
-- If you are receiving "HTTP Error 500.34 - ANCM Mixed Hosting" it is due to your bot attempting to use the *InProcess* Hosting Model. This is remedied by explicitly setting the bot to run *OutOfProcess* instead. See [Out of Process Hosting Model.](https://docs.microsoft.com/aspnet/core/host-and-deploy/aspnet-core-module?view=aspnetcore-3.1&preserve-view=true#out-of-process-hosting-model)
+- If you receive an "HTTP Error 500.34 - ANCM Mixed Hosting", your bot is attempting to use the `InProcess` Hosting Model. This is remedied by explicitly setting the bot to run `OutOfProcess` instead. See [Out-of-process hosting model](https://docs.microsoft.com/aspnet/core/host-and-deploy/aspnet-core-module?view=aspnetcore-3.1&preserve-view=true#out-of-process-hosting-model) in the AZP.NET Core documentation for more information.
 
-- If the *initialized* value of the **.bot endpoint** is false it means the Direct Line app service extension is unable to validate the **App Service Extension Key** added to the bot's *Application Settings* above.
+- If the **initialized** value of the **.bot endpoint** is false it means the Direct Line App Service extension is unable to validate the App Service extension key added to the bot's **Application Settings** above.
     1. Confirm the value was correctly entered.
-    1. Switch to the alternative **App Service Extension Key** shown on your bot's **Direct Line channel configuration page**.
+    1. Switch to the alternate extension key shown on your bot's **Configure Direct Line** page.
 
-- If attempting to use OAuth with the Direct Line App Service Extension and encountering the error "Unable to get the bot AppId from the audience claim." a *ClaimsIdentity* with the *AudienceClaim* assigned needs to be set on the *BotFrameworkHttpAdapter*. In order to accomplish this a developer may subclass the adapter similar to the example below:
+- If you attempt to use OAuth with the Direct Line App Service extension and encounter the error "Unable to get the bot AppId from the audience claim." A `ClaimsIdentity` with the `AudienceClaim` assigned needs to be set on the `BotFrameworkHttpAdapter`. In order to accomplish this a developer may subclass the adapter similar to the example below:
 
 ```csharp
 public class AdapterWithStaticClaimsIdentity : BotFrameworkHttpAdapter
 {
- public AdapterWithStaticClaimsIdentity(IConfiguration configuration, ILogger<BotFrameworkHttpAdapter> logger, ConversationState conversationState = null)
-            : base(configuration, logger)
- {
-            // Manually create the ClaimsIdentity and create a Claim with a valid AudienceClaim and the AppID for a bot using the Direct Line App Service Extension.
-            var appId = configuration.GetSection(MicrosoftAppCredentials.MicrosoftAppIdKey)?.Value;
-            ClaimsIdentity = new ClaimsIdentity(new List<Claim>{
-                new Claim(AuthenticationConstants.AudienceClaim, appId)
-            });
- }
+    public AdapterWithStaticClaimsIdentity(IConfiguration configuration, ILogger<BotFrameworkHttpAdapter> logger, ConversationState conversationState = null)
+        : base(configuration, logger)
+    {
+        // Manually create the ClaimsIdentity and create a Claim with a valid AudienceClaim and the AppID for a bot using the Direct Line App Service extension.
+        var appId = configuration.GetSection(MicrosoftAppCredentials.MicrosoftAppIdKey)?.Value;
+        ClaimsIdentity = new ClaimsIdentity(new List<Claim>{
+            new Claim(AuthenticationConstants.AudienceClaim, appId)
+        });
+    }
 }
 ```
 
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Use Web Chat with the Direct Line app service extension](./bot-service-channel-directline-extension-webchat-client.md)
+> [Use Web Chat with the Direct Line App Service extension](./bot-service-channel-directline-extension-webchat-client.md)

articles/rest-api/bot-framework-rest-direct-line-3-0-start-conversation.md

@@ -1,6 +1,6 @@
 ---
 title: Start a conversation - Bot Service
-description: Learn how to use version 3.0 of the Direct Line API to start conversations with bots. Find out how the Start Conversation and Generate Token operations differ.
+description: Learn how to use version 3.0 of the Direct Line API to start conversations with bots. Find out how the start conversation and generate token operations differ.
 author: RobStand
 ms.author: kamrani
 manager: kamrani
@@ -22,7 +22,7 @@ POST https://directline.botframework.com/v3/directline/conversations
 Authorization: Bearer SECRET_OR_TOKEN
 ```
 
-The following snippets provide an example of the Start Conversation request and response.
+The following snippets provide an example of the start conversation request and response.
 
 ### Request
 
@@ -49,16 +49,16 @@ HTTP/1.1 201 Created
 }
 ```
 
-Typically, a Start Conversation request is used to open a new conversation and an **HTTP 201** status code is returned if the new conversation is successfully started. However, if a client submits a Start Conversation request with a Direct Line token in the `Authorization` header that has previously been used to start a conversation using the Start Conversation operation, an **HTTP 200** status code will be returned to indicate that the request was acceptable but no conversation was created (as it already existed).
+Typically, a start conversation request is used to open a new conversation and an **HTTP 201** status code is returned if the new conversation is successfully started. However, if a client submits a start conversation request with a Direct Line token in the `Authorization` header that has previously been used to start a conversation using the start conversation operation, an **HTTP 200** status code will be returned to indicate that the request was acceptable but no conversation was created (as it already existed).
 
 > [!TIP]
 > You have 60 seconds to connect to the WebSocket stream URL. If the connection cannot be established during this time, you can [reconnect to the conversation](bot-framework-rest-direct-line-3-0-reconnect-to-conversation.md) to generate a new stream URL.
 
-## Start Conversation versus Generate Token
+## Start conversation versus generate token
 
-The Start Conversation operation (`POST /v3/directline/conversations`) is similar to the [Generate Token](bot-framework-rest-direct-line-3-0-authentication.md#generate-token) operation (`POST /v3/directline/tokens/generate`) in that both operations return a `token` that can be used to access a single conversation. However, the Start Conversation operation also starts the conversation, contacts the bot, and creates a WebSocket stream URL, whereas the Generate Token operation does none of these things. 
+The start conversation operation (`POST /v3/directline/conversations`) is similar to the [generate token](bot-framework-rest-direct-line-3-0-authentication.md#generate-token) operation (`POST /v3/directline/tokens/generate`) in that both operations return a `token` that can be used to access a single conversation. However, the start conversation operation also starts the conversation, contacts the bot, and creates a WebSocket stream URL, whereas the generate token operation does none of these things.
 
-If you intend to start the conversation immediately with your client, use the Start Conversation operation. If you plan to distribute the token to clients and want them to initiate the conversation, use the [Generate Token](bot-framework-rest-direct-line-3-0-authentication.md#generate-token) operation instead. 
+If you intend to start the conversation immediately with your client, use the start conversation operation. If you plan to distribute the token to clients and want them to initiate the conversation, use the [generate token](bot-framework-rest-direct-line-3-0-authentication.md#generate-token) operation instead.
 
 ## Additional resources