Release 'live' 03-28-2019 (#1389)

Author: Kaiqb

articles/TOC.md

@@ -7,8 +7,8 @@
 ### [.NET](dotnet/bot-builder-dotnet-sdk-quickstart.md)
 ### [JavaScript](javascript/bot-builder-javascript-quickstart.md)
 # Tutorials
-## [Create and deploy a basic bot](v4sdk/bot-builder-tutorial-basic-deploy.md)
-## [Add QnA Maker and redeploy a bot](v4sdk/bot-builder-tutorial-add-qna.md)
+## [1. Create and deploy a basic bot](v4sdk/bot-builder-tutorial-basic-deploy.md)
+## [2. Add QnA Maker and redeploy a bot](v4sdk/bot-builder-tutorial-add-qna.md)
 ## [Add authentication to your bot](bot-builder-tutorial-authentication.md)
 # Samples
 ## [botbuilder-samples repo on GitHub](https://github.com/Microsoft/BotBuilder-Samples/blob/master/README.md)

articles/bot-service-migrate-bot.md

@@ -7,14 +7,12 @@ manager: kamrani
 ms.topic: article
 ms.service: bot-service
 ms.subservice: abs
-ms.date: 6/22/2017
+ms.date: 3/22/2019
 monikerRange: 'azure-bot-service-3.0'
 ---
 
 # Migrate your bot to Azure
 
-
-
 All **Azure Bot Service (Preview)** bots created in the [Bot Framework Portal](http://dev.botframework.com) must migrate to the new Bot Service in Azure. The service was made generally available (GA) in December 2017. 
 
 Note that, registration bots connected only to the following channels are *not* required to migrate: **Teams**, **Skype**, or **Cortana**. For example, a registration bot connected to **Facebook** and **Skype** *is required* to migrate but a registration bot connected to **Skype** and **Cortana** *is not required* to migrate.
@@ -50,7 +48,7 @@ to `module.exports = connector.listen();`
 6.	Test your bot locally by running the Functions bot using the Bot Framework Emulator. More info on how to run the *funcpack* bot [here](https://github.com/Azure/azure-functions-pack#how-to-run). 
 7.	Upload your code back to Azure. Make sure the `.funcpack` directory is uploaded. You do not need to upload the **node_modules** directory.
 8. Test your remote bot to make sure it responds as expected.
-9. [Migrate your bot](#migrate-your-bot-to-azure) using the steps above.
+9. Migrate your bot using the steps above.
 
 ## Migration under the hood
 

articles/index.md

@@ -8,7 +8,7 @@ ms.topic: landing-page
 layout: LandingPage
 ms.service: bot-service
 ms.subservice: sdk
-ms.date: 01/16/2019
+ms.date: 03/28/2019
 ---
 ::: moniker range="azure-bot-service-3.0"
 
@@ -97,8 +97,8 @@ ms.date: 01/16/2019
 </div>
 
 <h2 style="margin-top: 36px">Step-by-Step Tutorials</h2>
-<p><a href="/bot-framework/bot-builder-tutorial-basic-deploy">Create and deploy a basic bot</a></p>
-<p><a href="/bot-framework/bot-builder-tutorial-add-qna">Add QnA Maker and redeploy a bot</a></p>
+<p><a href="/bot-framework/bot-builder-tutorial-basic-deploy">1. Create and deploy a basic bot</a></p>
+<p><a href="/bot-framework/bot-builder-tutorial-add-qna">2. Add QnA Maker and redeploy a bot</a></p>
 <h2 style="margin-top: 36px">Reference</h2>
 <ul class="panelContent cardsD">
     <li>

articles/v4sdk/bot-builder-concept-dialog.md

@@ -116,7 +116,7 @@ You can use the dialog context to begin, continue, replace, or end a dialog. You
 
 Dialogs can be thought of as a programmatic stack, which we call the *dialog stack*, with the turn handler as the one directing it and serving as the fallback if the stack is empty. The topmost item on that stack is considered the *active dialog*, and the dialog context directs all input to the active dialog.
 
-When a dialog begins, it is pushed onto the stack, and is now the active dialog. It remains the active dialog until it either ends, it is removed by the [replace dialog](#repeating-a-dialog) method, or another dialog is pushed onto the stack (by either the turn handler or active dialog itself) and becomes the active dialog. When that new dialog ends, it is popped off the stack and the next dialog down becomes the active dialog again. This allows for [branching and looping](#looping-and-branching), discussed below.
+When a dialog begins, it is pushed onto the stack, and is now the active dialog. It remains the active dialog until it either ends, it is removed by the [replace dialog](#repeating-a-dialog) method, or another dialog is pushed onto the stack (by either the turn handler or active dialog itself) and becomes the active dialog. When that new dialog ends, it is popped off the stack and the next dialog down becomes the active dialog again. This allows for branching and looping, discussed below.
 
 ### Create the dialog context