Release 09-12-2017 (#287)

RobStand · web-flow · commit f6daa3b7dd04 · 2017-09-12T11:58:25.000-07:00
* merge branch 'live' into master * Changing pluralization of SDKs to SDK (#283) * Community content live sync work (#271) * Update bot-builder-dotnet-quickstart.md Restoring links to the controller & dialog templates that were present in previous documentation * ISO 639-2 recommends use of the language codes in lower case (#175) * Grammar correction. Whose, not Who's (#33) * Updated to correct version of IISExpress (#35) * Update resources-tools-downloads.md (#31) * Update resources-tools-downloads.md Add information for how to install the Visual Studio project templates. * Update resources-tools-downloads.md * Changed AttachmentLayouts to AttachmentLayoutTypes (#38) The types of Attachment Layouts class is called AttachmentLayoutTypes and not AttachmentLayouts. https://docs.botframework.com/en-us/csharp/builder/sdkreference/d7/d87/class_microsoft_1_1_bot_1_1_connector_1_1_attachment_layout_types.html * Removing bad metadata (#183) * Conversation designer (#178) * requires (#186) * Dialog next steps (#177) * Added clarification for ListStyle in Prompts.choice * Minor copy edits. * Add reference to Manage state data topic. * Saving progress... * Bind actions to dialog * Types table link to section instead. * Confirm interruptions * Added some more details and made some minor edits. * Update links to reflect new file name for the 'Handle user actions' topic. * Fix broken link. * minor edits to the Actions topic and cross linking. * fixed broken link * Redirecting to the new topic. * Revised content ready for review. * fix broken links. * Fixed Action node to live under Dialog. * Edit based on revision comments. * Fix broken link to "Action precedence" section. * Dialog Overview - edited based on review feedback. * Added a "Next step" section to each topics. * Reorder Dialog TOC topics * with revisions from paper notes * Update bot-builder-dotnet-quickstart.md Restoring links to the controller & dialog templates that were present in previous documentation * Removing bad metadata (#183) * Conversation designer (#178) * requires (#186) * Added Next step and move Dialogs before Messages in the TOC. * Update referece to te persistCoversatioData flag...it's enabled by default. * Clarify reference to global actions and added new section for customAction to the topic. * Updated Next step to use button instead of link. * Remove "Null response" section based on SteveIckman feedback. * Update section to say "Next steps" for consistencies. * Removing extraneous Additional Resources section * Subscribe to bot events, always show bot online (#189) Slack doc update * Changing author alias (#193) * links to best current samples, User Story 17067 (#185) Fixed sample references. * Second effort for PR181 (#187) Next Steps and Requirement about .NET 4.6 * Groupme screencaps (#191) GroupMe screen changes. * Fixed broken anchor links from table to section in topic. (#195) * Adding NoIndex, NoFollow to metadata (#196) * Removing broken video * Update bot-builder-nodejs-cortana-skill.md Fixed bug reported by PM. Removed "Sign In Card" for Cortana channel link due to a security bug that we recently discovered. * added dotnet scorable dialogs (#180) * added dotnet scorable dialogs * edited links, fixed typos to scorables article * added date/title/header, grammar change * Updated bot-builder-dotnet-scorable-dialogs.md * Update filenames.md * Added entries about the documentation (#206) * Slack review (#204) * Scorable review (#203) * Resolve syncing conflicts from live-sync-work to live (#39) * Release 07-07-2017 (#176) * ISO 639-2 recommends use of the language codes in lower case (#175) * Update bot-builder-dotnet-quickstart.md Restoring links to the controller & dialog templates that were present in previous documentation * Removing bad metadata (#183) * Release 07-14-2017 (#184) * Conversation designer (#178) * Conversation Designer going live (#188) * convert external Twilio links to HTML style target="_blank" to open in new tab. * Secure bot reminder and ngrok command. If you're debugging through Cortana, then the Microsoft App credentials need to specified in both the Bot Framework portal and the Web.config file. I also found that bots always ran on port 3979. And lastly, unless I specified the host header the requests would fail with 400. * convert external links to open in new tab * update external links to open in new tab * Update bot-builder-nodejs-global-handlers.md Added missing comma's in the examples of trigger actions * Fixing link * Revert "Merging upstream into public" This reverts commit ed2438b, reversing changes made to f4200df. * Dotnet form flow updates (#161) * Updated .NET FormFlow articles to add links to sample code on GitHub. * Fixed broken link. * Updated .NET FormFlow articles to move Sample code section. * Fixed broken link. * Update IActivity.xml * Update IActivity.xml Fixing indentation. * Updating summary for ChannelData * Updating IActivity docs with ChannelData remarks * bugfix: domain parameter and log=false for compliance (#164) * fix bug - domain parameter * section link, class definition * document log=off for privacy compliance * fix heading * Change .NET Framework target version (#166) * Adding DirectLine to REST card (#167) * Typo fix * Removing location control from hub * little fixes (#169) Add an optional extended description… * clicking on a speech bubble reveals the JSON data underlying the message. (#171) * Microsoft.Bot.Builder template requires IIS Express; added download link. (#170) * The Microsoft.Bot.Builder template requires IIS Express, so now there's a link where you can download it. * occasional requirement: IIS Express download, a bit hard to find this link so now it's noted near the place where it's (occasionally) needed. * section: dialog-based proactive message - fix broken sample code & link to botadaptor.js file * add back comment with note about session.userData * fix typo * Anchor links (#173) * Promoting questions to H2s for anchor links * Updating title and H1 * Fixing outdated anchor links * VS Community isn't supported by the template * Update dos-and-donts.md * Update style-and-voice.md * Update style-and-voice.md * Fixing link to botadapter.js * section: dialog-based proactive message - fix broken sample code & link to botadaptor.js file * add back comment with note about session.userData * fix typo * ISO 639-2 recommends use of the language codes in lower case (#175) * Update bot-builder-dotnet-quickstart.md Restoring links to the controller & dialog templates that were present in previous documentation * Removing bad metadata (#183) * Conversation designer (#178) * requires (#186) * Dialog next steps (#177) * Added clarification for ListStyle in Prompts.choice * Minor copy edits. * Add reference to Manage state data topic. * Saving progress... * Bind actions to dialog * Types table link to section instead. * Confirm interruptions * Added some more details and made some minor edits. * Update links to reflect new file name for the 'Handle user actions' topic. * Fix broken link. * minor edits to the Actions topic and cross linking. * fixed broken link * Redirecting to the new topic. * Revised content ready for review. * fix broken links. * Fixed Action node to live under Dialog. * Edit based on revision comments. * Fix broken link to "Action precedence" section. * Dialog Overview - edited based on review feedback. * Added a "Next step" section to each topics. * Reorder Dialog TOC topics * with revisions from paper notes * Update bot-builder-dotnet-quickstart.md Restoring links to the controller & dialog templates that were present in previous documentation * Removing bad metadata (#183) * Conversation designer (#178) * requires (#186) * Added Next step and move Dialogs before Messages in the TOC. * Update referece to te persistCoversatioData flag...it's enabled by default. * Clarify reference to global actions and added new section for customAction to the topic. * Updated Next step to use button instead of link. * Remove "Null response" section based on SteveIckman feedback. * Update section to say "Next steps" for consistencies. * Removing extraneous Additional Resources section * Release 7-20-2017 * Added clarification for ListStyle in Prompts.choice * Minor copy edits. * Add reference to Manage state data topic. * Saving progress... * Bind actions to dialog * Types table link to section instead. * Confirm interruptions * Added some more details and made some minor edits. * Update links to reflect new file name for the 'Handle user actions' topic. * Fix broken link. * minor edits to the Actions topic and cross linking. * fixed broken link * Redirecting to the new topic. * Revised content ready for review. * fix broken links. * Fixed Action node to live under Dialog. * Edit based on revision comments. * Fix broken link to "Action precedence" section. * Dialog Overview - edited based on review feedback. * Added a "Next step" section to each topics. * Reorder Dialog TOC topics * with revisions from paper notes * Update bot-builder-dotnet-quickstart.md Restoring links to the controller & dialog templates that were present in previous documentation * Removing bad metadata (#183) * Conversation designer (#178) * requires (#186) * Added Next step and move Dialogs before Messages in the TOC. * Update referece to te persistCoversatioData flag...it's enabled by default. * Clarify reference to global actions and added new section for customAction to the topic. * Updated Next step to use button instead of link. * Remove "Null response" section based on SteveIckman feedback. * Update section to say "Next steps" for consistencies. * Removing extraneous Additional Resources section * Subscribe to bot events, always show bot online (#189) Slack doc update * Changing author alias (#193) * links to best current samples, User Story 17067 (#185) Fixed sample references. * Second effort for PR181 (#187) Next Steps and Requirement about .NET 4.6 * Groupme screencaps (#191) GroupMe screen changes. * Updates to Slack, GroupMe, sample links, next steps (#194) * Fixed broken anchor links from table to section in topic. (#195) * Adding NoIndex, NoFollow to metadata (#196) * Release 7-24-2017 (#197) * Removing broken video * Update bot-builder-nodejs-cortana-skill.md Fixed bug reported by PM. Removed "Sign In Card" for Cortana channel link due to a security bug that we recently discovered. * Update bot-builder-nodejs-cortana-skill.md (#198) Fixed bug reported by PM. Removed "Sign In Card" for Cortana channel link due to a security bug that we recently discovered. * added dotnet scorable dialogs (#180) * added dotnet scorable dialogs * edited links, fixed typos to scorables article * added date/title/header, grammar change * Updated bot-builder-dotnet-scorable-dialogs.md * Update filenames.md * Added entries about the documentation (#206) * Slack review (#204) * Scorable review (#203) * Grammar correction. Whose, not Who's (#33) * Updated to correct version of IISExpress (#35) * Changed AttachmentLayouts to AttachmentLayoutTypes (#38) The types of Attachment Layouts class is called AttachmentLayoutTypes and not AttachmentLayouts. https://docs.botframework.com/en-us/csharp/builder/sdkreference/d7/d87/class_microsoft_1_1_bot_1_1_connector_1_1_attachment_layout_types.html * Update resources-tools-downloads.md (#31) * Update resources-tools-downloads.md Add information for how to install the Visual Studio project templates. * Update resources-tools-downloads.md * Release 08-01-2017 (#207) * Updating next step * Fixing illegal bookmark usage * Fixing build warning in dotnet reference * Fixing build warning in dotnet reference * Staging for fix from nuget release * Cropped out wechat icon. wechat is not supported (#209) * three downloads for one template (#212) * Initialize open publishing repository: https://github.com/MicrosoftDocs/bot-docs-pr of branch live * Initialize open publishing repository: https://github.com/MicrosoftDocs/bot-docs-pr of branch master * Fix for bug# 17564. Add gitter.im, specifically the BotBuilder ROOM (#216) Bug details: https://fuselabs.visualstudio.com/BFDocs/_workitems/edit/17564 * Release 08-03-2017 (#217) * Release 08-04-2017 (#221) * 17561 deploy from local git (#215) * add ms.date metadata (#219) * Fixing search scope * Resolve syncing conflicts from live-sync-work to live (#40) * Delete duplicate section, correct info on how to select ListStyle (#41) * Update bot-design-conversation-flow.md (#42) * Update bot-builder-nodejs-send-suggested-actions.md (#43) * Added ConsoleConnector language and example (#44) * Update bot-builder-nodejs-send-suggested-actions.md * Added ConsoleConnector language and example * Add Teams as channel that supports TextFormat xml (#49) * use numeric prompt for qry of ppl in reservation (#48) * fix formatting for initial npm init invocation (#46) * Update erroneous link to code snippet (#45) * Update live branch 09-08-17 (ABS Fix) * Just a little correction in spelling of visible (#50)
diff --git a/.openpublishing.publish.config.json b/.openpublishing.publish.config.json
@@ -138,4 +138,4 @@
     "dotnet/api"
   ],
   "toc_path_need_to_split": "dotnet/api/toc.yml"
-}
+}
diff --git a/articles/bot-builder-overview-getstarted.md b/articles/bot-builder-overview-getstarted.md
@@ -1,6 +1,6 @@
 ---
 title: Start building bots with the Bot Framework | Microsoft Docs
-description: Get started building powerful bots with the Bot Framework and Bot Builder SDKs.
+description: Get started building powerful bots with the Bot Framework and Bot Builder SDK.
 author: kbrandl
 ms.author: kibrandl
 manager: rstand
@@ -9,9 +9,10 @@ ms.prod: bot-framework
 ms.date: 08/04/2017
 ---
 
+
 # Start building bots with the Bot Framework
 
-The Bot Framework includes Bot Builder to give you the tools you need to develop bots. Bot Builder is an open-source SDK with support for .NET, Node.js, and REST. Using Bot Builder, you can get started and have a working bot in just a few minutes.
+The Bot Framework includes Bot Builder to help you develop bots. Bot Builder is an open-source SDK with support for .NET, Node.js, and REST. Using Bot Builder, you can get started and have a working bot in just a few minutes.
 
 ## Bot Builder SDK for .NET
 
diff --git a/articles/bot-design-conversation-flow.md b/articles/bot-design-conversation-flow.md
@@ -70,4 +70,4 @@ There is no *right* answer to this question, as the best solution will depend up
 
 Managing the user's navigation across dialogs and designing conversation flow in a manner that enables 
 users to achieve their goals (even in a non-linear fashion) is a fundamental challenge of bot design. 
-The [next article](~/bot-design-navigation.md) reviews some common pitfalls of poorly designed navigation and discuss strategies for avoiding those traps. 
+The [next article](~/bot-design-navigation.md) reviews some common pitfalls of poorly designed navigation and discusses strategies for avoiding those traps. 
diff --git a/articles/dotnet/bot-builder-dotnet-create-messages.md b/articles/dotnet/bot-builder-dotnet-create-messages.md
@@ -58,7 +58,7 @@ These styles are supported when `TextFormat` is set to "xml":
 | hyperlink | \<a href="http://www.bing.com"\>bing\</a\> | <a href="http://www.bing.com">bing</a> |
 
 > [!NOTE]
-> The `TextFormat` **xml** is supported only by the Skype channel. 
+> The `TextFormat` **xml** is supported only by the Microsoft Teams and Skype channels. 
 
 ## Attachments
 
@@ -146,7 +146,7 @@ The `Speak` property of a message activity can be used to specify the text to be
 
 ## Suggested actions
 
-The `SuggestedActions` property of a message activity can be used to present buttons that the user can tap to provide input. Unlike buttons that appear within rich cards (which remain visable and accessible to the user even after being tapped), buttons that appear within the suggested actions pane will disappear after the user makes a selection. For details, see [Add suggested actions to messages](bot-builder-dotnet-add-suggested-actions.md).
+The `SuggestedActions` property of a message activity can be used to present buttons that the user can tap to provide input. Unlike buttons that appear within rich cards (which remain visible and accessible to the user even after being tapped), buttons that appear within the suggested actions pane will disappear after the user makes a selection. For details, see [Add suggested actions to messages](bot-builder-dotnet-add-suggested-actions.md).
 
 ## Next steps
 
diff --git a/articles/includes/code/node-getstarted.js b/articles/includes/code/node-getstarted.js
@@ -1,4 +1,15 @@
+// <consolebot>
+
+var builder = require('botbuilder');
+
+var connector = new builder.ConsoleConnector().listen();
+var bot = new builder.UniversalBot(connector, function (session) {
+    session.send("You said: %s", session.message.text);
+});
+// </consolebot>
+
 // <echobot>
+
 var restify = require('restify');
 var builder = require('botbuilder');
 
@@ -21,4 +32,4 @@ server.post('/api/messages', connector.listen());
 var bot = new builder.UniversalBot(connector, function (session) {
     session.send("You said: %s", session.message.text);
 });
-// </echobot>
+// </echobot>
diff --git a/articles/index.md b/articles/index.md
@@ -351,7 +351,7 @@ description:
                                             </div>
                                         </div>
                                         <div class="cardText">
-                                            <h3>SDKs and tools</h3>
+                                            <h3>SDK and tools</h3>
                                             <p>Get the Bot Framework SDK and tools for building bots.</p>
                                         </div>
                                     </div>
diff --git a/articles/nodejs/bot-builder-nodejs-concepts.md b/articles/nodejs/bot-builder-nodejs-concepts.md
@@ -27,6 +27,8 @@ For an example that demonstrates using these classes, see [Create a bot with the
 
 The Connector also normalizes the messages that the bot sends to channels so that you can develop your bot in a platform-agnostic way. Normalizing a message involves converting it from the Bot Framework’s schema into the channel’s schema. In cases where the channel does not support all aspects of the framework’s schema, the Connector will try to convert the message to a format that the channel supports. For example, if the bot sends a message that contains a card with action buttons to the SMS channel, the Connector may render the card as an image and include the actions as links in the message’s text. The [Channel Inspector][ChannelInspector] is a web tool that shows you how the Connector renders messages on various channels.
 
+The `ChatConnector` requires an API endpoint to be setup within your bot. With the Node.js SDK, this is usually accomplished by installing the `restify` Node.js module. Bots can also be created for the console using the [ConsoleConnector][ConsoleConnector], which does not require an API endpoint.
+
 ## Messages
 
 Messages can consist of text to be displayed, text to be spoken, attachments, rich cards, and suggested actions. You use the [session.send][SessionSend] method to send messages in response to a message from the user. Your bot may call `send` as many times as it likes in response to a message from the user. For an example that demonstrates this, see [Respond to user messages][RespondMessages].
@@ -75,6 +77,7 @@ Bot Builder lets you use LUIS to add natural language understanding to your bot
 [PersistConversationData]: https://docs.botframework.com/en-us/node/builder/chat-reference/interfaces/_botbuilder_d_.iuniversalbotsettings.html#persistconversationdata
 [UniversalBot]: https://docs.botframework.com/en-us/node/builder/chat-reference/classes/_botbuilder_d_.universalbot.html
 [ChatConnector]: https://docs.botframework.com/en-us/node/builder/chat-reference/classes/_botbuilder_d_.chatconnector.html
+[ConsoleConnector]: https://docs.botframework.com/en-us/node/builder/chat-reference/classes/_botbuilder_d_.consoleconnector.html
 
 [ChannelInspector]: https://docs.botframework.com/en-us/channel-inspector/channels/Skype
 
diff --git a/articles/nodejs/bot-builder-nodejs-dialog-manage-conversation-flow.md b/articles/nodejs/bot-builder-nodejs-dialog-manage-conversation-flow.md
@@ -44,7 +44,7 @@ var bot = new builder.UniversalBot(connector, [
     },
     function (session, results) {
         session.dialogData.reservationDate = builder.EntityRecognizer.resolveTime([results.response]);
-        builder.Prompts.text(session, "How many people are in your party?");
+        builder.Prompts.number(session, "How many people are in your party?");
     },
     function (session, results) {
         session.dialogData.partySize = results.response;
diff --git a/articles/nodejs/bot-builder-nodejs-handle-conversation-events.md b/articles/nodejs/bot-builder-nodejs-handle-conversation-events.md
@@ -58,4 +58,4 @@ For trigger actions you can provide an [onInterrupted][onInterrupted] handler to
 [SendTyping]: https://docs.botframework.com/en-us/node/builder/chat-reference/classes/_botbuilder_d_.session#sendtyping
 [IMessage]: http://docs.botframework.com/en-us/node/builder/chat-reference/interfaces/_botbuilder_d_.imessage
 [ChatConnector]: https://docs.botframework.com/en-us/node/builder/chat-reference/classes/_botbuilder_d_.chatconnector.html
-[session_userData]: https://docs.botframework.com/en-us/node/builder/chat-reference/classes/_botbuilder_d_.session.html#userdata
+[session_userData]: https://docs.botframework.com/en-us/node/builder/chat-reference/classes/_botbuilder_d_.session.html#userdata
diff --git a/articles/nodejs/bot-builder-nodejs-quickstart.md b/articles/nodejs/bot-builder-nodejs-quickstart.md
@@ -28,33 +28,67 @@ Get started by completing the following prerequisite tasks:
 2. Create a folder for your bot.
 3. From a command prompt or terminal, navigate to the folder you just created.
 4. Run the following **npm** command:
+
 ```nodejs
 npm init
 ```
 
 Follow the prompt on the screen to enter information about your bot and npm will create a **package.json** file that contains the information you provided. 
 
 ## Install the SDK
-Next, install the Bot Builder SDK for Node.js and <a href="http://restify.com/" target="_blank">restify</a> by running the following **npm** commands:
+Next, install the Bot Builder SDK for Node.js by running the following **npm** command:
 
 ```nodejs
 npm install --save botbuilder
-npm install --save restify
 ```
 
-Once you have the SDK and Restify in place, you're ready to write your bot.
-
-## Create your bot
+Once you have the SDK installed, you are ready to write your first bot.
 
 For your first bot, you will create a bot that simply echoes back any user input. To create your bot, follow these steps:
 
 1. In the folder that you created earlier for your bot, create a new file named **app.js**.
 2. Open **app.js** in a text editor or an IDE of your choice. Add the following code to the file: 
 
+   [!code-javascript[consolebot code sample Node.js](../includes/code/node-getstarted.js#consolebot)]
+
+3. Save the file. Now you are ready to run and test out your bot.
+
+### Start your bot
+
+Navigate to your bot's directory in a console window and start your bot:
+
+```nodejs
+node app.js
+```
+
+Your bot is now running locally. Try out your bot by typing a few messages in the console window.
+You should see that the bot responds to each message you send by echoing back your message prefixed with the text *"You said:"*.
+
+## Install Restify
+
+Console bots are good text-based clients, but in order to use any of the Bot Framework channels (or run your bot in the emulator), your bot will need to run on an API endpoint. Install <a href="http://restify.com/" target="_blank">restify</a> by running the following **npm** command:
+
+```nodejs
+npm install --save restify
+```
+
+Once you have Restify in place, you're ready to make some changes to your bot.
+
+## Edit your bot
+
+You will need to make some changes to your **app.js** file. 
+
+1. Add a line to require the `restify` module.
+2. Change the `ConsoleConnector` to a `ChatConnector`.
+3. Include your Microsoft App ID and App Password.
+4. Have the connector listen on an API endpoint.
+
    [!code-javascript[echobot code sample Node.js](../includes/code/node-getstarted.js#echobot)]
 
 3. Save the file. Now you are ready to run and test out your bot.
 
+Please note that you do not need a Microsoft App ID or App Password to run your bot in the Bot Framework Emulator.
+
 ## Test your bot
 Next, test your bot by using the [Bot Framework Emulator](../debug-bots-emulator.md) to see it in action. The emulator is a desktop application that lets you test and debug your bot on localhost or running remotely through a tunnel.
 
@@ -86,4 +120,4 @@ You've successfully created your first bot using the Bot Builder SDK for Node.js
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Bot Builder SDK for Node.js](bot-builder-nodejs-overview.md)
+> [Bot Builder SDK for Node.js](bot-builder-nodejs-overview.md)
diff --git a/articles/nodejs/bot-builder-nodejs-send-suggested-actions.md b/articles/nodejs/bot-builder-nodejs-send-suggested-actions.md
@@ -30,6 +30,8 @@ This code example shows how to send a message that presents three suggested acti
 
 When the user taps one of the suggested actions, the bot will receive a message from the user that contains the `value` of the corresponding action.
 
+Be aware that the `imBack` method will post the `value` to the chat window of the channel you are using. If this is not the desired effect, you can use the `postBack` method, which will still post the selection back to your bot, but will not display the selection in the chat window. Some channels do not support `postBack`, however, and in those instances the method will behave like `imBack`.
+
 ## Additional resources
 
 * [Preview features with the Channel Inspector][inspector]
@@ -45,4 +47,4 @@ When the user taps one of the suggested actions, the bot will receive a message
 
 [inspector]: ../portal-channel-inspector.md
 
-[channelInspector]: https://docs.botframework.com/en-us/channel-inspector/channels/Skype/
+[channelInspector]: https://docs.botframework.com/en-us/channel-inspector/channels/Skype/
diff --git a/articles/overview-how-bot-framework-works.md b/articles/overview-how-bot-framework-works.md
@@ -18,7 +18,7 @@ Bots are apps that offer a conversational interface as the best solution to the
 ![Architecture overview diagram](~/media/how-it-works/architecture-resize.png)
 
 ### Bot Builder
-To help you build bots with C# or JavaScript, the Bot Framework includes Bot Builder SDKs. The SDKs provide libraries, samples, and tools to help you build and debug bots. The SDKs contain built-in dialogs to handle user interactions ranging from a basic Yes/No to complex disambiguation. Built-in recognizers and event handlers help guide the user through a conversation. 
+To help you build bots with C# or JavaScript, the Bot Framework includes Bot Builder SDK. The SDK provides libraries, samples, and tools to help you build and debug bots. The SDK contains built-in dialogs to handle user interactions ranging from a basic Yes/No to complex disambiguation. Built-in recognizers and event handlers help guide the user through a conversation. 
 
 The [Bot Builder SDK for .NET](~/dotnet/bot-builder-dotnet-overview.md) leverages C# to provide a familiar way for .NET developers to write bots. It is a powerful framework for constructing bots that can handle both free-form interactions and more guided conversations where the user selects from possible values.
 
diff --git a/articles/overview-introduction-bot-framework.md b/articles/overview-introduction-bot-framework.md
@@ -30,7 +30,7 @@ Bots are rapidly becoming an integral part of digital experiences. They are beco
 Developers writing bots all face the same problems: bots require basic I/O, they must have language and dialog skills, and they must connect to users, preferably in any conversation experience and language the user chooses. The Bot Framework provides powerful tools and features to help solve these problems.
 
 ### Bot Builder
-To help you build your bot, the Bot Framework includes [Bot Builder](bot-builder-overview-getstarted.md), which provides rich and full-featured SDKs for the .NET and Node.js platforms. The SDKs provide features that make interactions between bots and users much simpler. Bot Builder also includes an emulator for debugging your bots, as well as a large set of sample bots you can use as building blocks.
+To help you build your bot, the Bot Framework includes [Bot Builder](bot-builder-overview-getstarted.md), which provides rich and full-featured SDK for the .NET and Node.js platforms. The SDK provides features that make interactions between bots and users much simpler. Bot Builder also includes an emulator for debugging your bots, as well as a large set of sample bots you can use as building blocks.
 
 ### Bot Framework portal
 Managing your bot is easy with the Bot Framework  portal. The Bot Framework  portal gives you one convenient place to register, connect, and manage your bot. It also provides diagnostic tools and a web chat control you can use to embed your bot on a web page.
diff --git a/articles/resources-tools-downloads.md b/articles/resources-tools-downloads.md
@@ -9,9 +9,9 @@ ms.prod: bot-framework
 ms.date: 06/27/2017
 ms.reviewer:
 ---
-# Bot Framework SDKs and tools
+# Bot Framework SDK and tools
 
-The Bot Builder SDKs provide libraries, samples, and tools to help you build and debug bots. To get started building bots, download the SDK for the platform you are using, either C# on .NET or Node.js. You can download the SDKs as packages or you can get the source code.
+The Bot Builder SDK provides libraries, samples, and tools to help you build and debug bots. To get started building bots, download the SDK for the platform you are using, either C# on .NET or Node.js. You can download the SDK as packages or you can get the source code.
 
 ## Get the Bot Builder SDK for .NET
 The Bot Builder SDK for .NET leverages C# to provide a familiar way for .NET developers to write bots. It is a powerful framework for constructing bots that can handle both free-form interactions and more guided conversations where the user selects from possible values.
diff --git a/styleguide/hub-ia.md b/styleguide/hub-ia.md
@@ -2,7 +2,7 @@
 	- What is the Bot Framework?
 	- Scenarios
 	- Key Concepts
-	- SDKs and Tools
+	- SDK and Tools
 - Developing Bots
 	- Build Your First Bot in 5 Minutes
 	- Designing Bots
