Fix git push error for protected CLA branch

articles/bot-service-channel-directline-extension-webchat-client.md

@@ -24,7 +24,7 @@ https://github.com/Jeffders/DirectLineAppServiceExtensionPreview/tree/master/lib
 
 ## Integrate WebChat client
 
-Generally speaking, the approach is the same as before. With the exception that a new version of **WebChat** has been created that supports two-way **WebSocket** traffic, which instead of connecting to https://directline.botframework.com/ connects directly to your hosted bot.
+Generally speaking, the approach is the same as before. With the exception that a new version of **WebChat** has been created that supports two-way **WebSocket** traffic, which instead of connecting to [https://directline.botframework.com/](https://directline.botframework.com/) connects directly to your hosted bot.
 The direct line URL for your bot will be `https://<your_app_service>.azurewebsites.net/.bot/`, where the `/.bot/` extension is the Direct Line **endpoint** on your App Service.
 If you can configure your own domain name you still must append the `/.bot/` path to access the direct line REST APIs.
 

articles/bot-service-resources-user-agent.md

@@ -10,7 +10,7 @@ ms.date: 12/13/2017
 ---
 # Bot Framework User-Agent requests
 
-If you’re reading this message, you’ve probably received a request from a Microsoft Bot Framework service. This guide will help you understand the nature of these requests and provide steps to stop them, if so desired.
+If you’re reading this message, you may have received a request from a Microsoft Bot Framework service. This guide will help you understand the nature of these requests and provide steps to stop them, if so desired.
 
 If you received a request from our service, it likely had a User-Agent header formatted similar to the string below:
 

articles/bot-service-troubleshoot-bot-configuration.md

@@ -7,12 +7,12 @@ ms.author: kamrani
 manager: kamrani
 ms.topic: article
 ms.service: bot-service
-ms.date: 4/30/2019
+ms.date: 2/20/2020
 ---
 
 # Troubleshoot bot configuration issues
 
-The first step in troubleshooting a bot is to test it in Web Chat. This will allow you to determine if the problem is specific to your bot (bot doesn't work in any channel) or to a particular channel (bot works in some channels but not others).
+A bot can generate different types of errors, such as not being able to respond, throwing errors, or working in one channel but not in another. The first step in troubleshooting a bot is to test it in Web Chat. This will allow you to determine if the problem is specific to your bot (bot doesn't work in any channel) or to a particular channel (bot works in some channels but not others).
 
 ## Test in Web Chat
 
@@ -26,14 +26,19 @@ If the bot does not respond with the expected output, go to [Bot does not work i
 
 ## Bot does not work in Web Chat
 
-There could be a number of reasons why a bot doesn't work. Most likely, the bot application is down and cannot receive messages, or the bot receives the messages but fails to respond.
+There could be a number of reasons why a bot doesn't work. Most likely, the bot application is down and cannot receive messages, or the bot receives the messages but fails to respond. Here are some of the possible causes:
+
+- The bot is down and cannot be reached.
+- The bot is crashing.
+- The bot's endpoint is incorrect.
+- The bot is successfully receiving your messages but cannot respond.
 
 To see if the bot is running:
 
 1. Open the **Overview** pane.
 1. Copy the **Messaging endpoint** and paste it into your browser.
 
-If the endpoint returns HTTP Error 405, that means the bot is reachable and the bot is able to respond to messages. You should investigate whether your bot [times out](https://github.com/daveta/analytics/blob/master/troubleshooting_timeout.md) or [fails with an HTTP 5xx error](bot-service-troubleshoot-500-errors.md).
+If the endpoint returns HTTP Error 404 or 405, that means the bot is reachable and the bot is able to respond to messages. To investigate timeout issues, see [times out](https://github.com/daveta/analytics/blob/master/troubleshooting_timeout.md) or [fails with an HTTP 5xx error](bot-service-troubleshoot-500-errors.md) articles.
 
 If the endpoint returns an error "This site can't be reached" or "can't reach this page", that means that your bot is down and you need to redeploy it.
 
@@ -52,12 +57,12 @@ If the bot works as expected in Web Chat but fails in some other channel, possib
 
 ### Channel configuration issues
 
-It's possible that channel configuration parameters have been set incorrectly or have changed externally. For example, a bot has configured the Facebook channel for a particular page and the page was later deleted. The simplest solution is remove the channel and redo the channel configuration anew.
+It's possible that channel configuration parameters, such as the bot's username and password have been set incorrectly or have changed externally. For example, a bot was configured with the Facebook channel for a particular page and the page was later deleted. The simplest solution is remove the channel and redo the channel configuration anew.
 
 The links below provide instructions for configuring channels supported by the Bot Framework:
 
 - [Cortana](bot-service-channel-connect-cortana.md)
-- [DirectLine](bot-service-channel-connect-directline.md)
+- [Direct Line](bot-service-channel-connect-directline.md)
 - [Email](bot-service-channel-connect-email.md)
 - [Facebook](bot-service-channel-connect-facebook.md)
 - [GroupMe](bot-service-channel-connect-groupme.md)
@@ -71,7 +76,7 @@ The links below provide instructions for configuring channels supported by the B
 
 ### Channel-specific behavior
 
-Implementation of some features can differ by channel. For example, not all channels support Adaptive Cards. Most channels support Buttons, but they are rendered in a channel-specific way. If you see differences in how some message types work in different channels, consult the [channels reference](bot-service-channels-reference.md) article.
+Implementation of some features can differ by channel. For example, not all channels support Adaptive Cards. Most channels support Actions (buttons), but they are rendered in a channel-specific way. If you see differences in how some message types work in different channels, consult the [channels reference](bot-service-channels-reference.md) article.
 
 Below are some additional links that can help with individual channels:
 
@@ -83,7 +88,7 @@ Below are some additional links that can help with individual channels:
 
 ### Channel outage
 
-Occasionally, some channels might have an interruption of service. Usually, such outages don't last long. However, if you suspect an outage, consult a channel web site or social media.
+Occasionally, some channels might have an interruption of service. Usually, such outages don't last long. However, if you suspect an outage, consult the channel's web site or social media.
 
 Another way to determine if a channel has an outage is to create a test bot (such as a simple Echo Bot) and add a channel. If the test bot works with some channels but not others, that would indicate that the problem is not in your production bot.