update master README.md

- add entry for sample 13.core-bot.tests
- add entry for sample 46.teams-auth
- add entry for sample 47.inspection
- update bgts in sample 47's README.md

Author: sgellock

README.md

@@ -29,6 +29,7 @@ Samples are designed to illustrate scenarios you'll need to implement to build g
 |8.suggested-actions    | Demonstrates how to enable your bot to present buttons that the user can tap to provide input.                                      |[View][cs#8] |[View][js#8] |              |             | |
 |11.qnamaker            | Demonstrates how to use QnA Maker to have simple single-turn conversations     |[View][cs#11]|[View][js#11]|              |             | |
 |13.core-bot            | Core bot shows how to use cards, dialog, and Langugage Understanding (LUIS).                         |[View][cs#13]|[View][js#13]|[View][wa#13] |             |[View][ts#13]|
+|13.core-bot.tests            | Unit test project Core bot shows how to use use Bot Framework testing framework.                         |[View][cs#13.b]|   |   |             |  |
 |14.nlp-with-dispatch   | Demonstrates how to dispatch across LUIS and QnA Maker.                            |[View][cs#14]|[View][js#14]|              |             | |
 |15.handling-attachments| Demonstrates how to listen for/handle user provided attachments.                |[View][cs#15]|[View][js#15]|              |             | |
 |16.proactive-messages  | Demonstrates how to send proactive messages to users.                           |[View][cs#16]|[View][js#16]|              |             | |
@@ -42,6 +43,8 @@ Samples are designed to illustrate scenarios you'll need to implement to build g
 |43.complex-dialog      | Demonstrates different ways for composing dialogs. |[View][cs#43]|[View][js#43] |              |             | |
 |44.prompt-for-user-input | Demonstrates how to implement your own _basic_ prompts to ask the user for information. |[View][cs#44]|[View][js#44]|              |             | |
 |45.state-management    | Demonstrates how to use state management and storage objects to manage and persist state. | [View][cs#45] | [View][js#45]   |              |             |  |
+|46.teams-auth    | Demonstrates how to use authentication for a bot running in Microsoft Teams. | [View][cs#46] | [View][js#46]   |              |             |  |
+|47.inspection    | Demonstrates how to use middleware to allow the Bot Framework Emulator to debug traffic into and out of the bot in addition to looking at the current state of the bot. | [View][cs#47] | [View][js#47]   |              |             |  |
 |70.styling-webchat     | This sample shows how to create a web page with custom Web Chat component.|         |          |              |  [View][es#70] |     |
 
 [cs#1]:samples/csharp_dotnetcore/01.console-echo
@@ -53,6 +56,7 @@ Samples are designed to illustrate scenarios you'll need to implement to build g
 [cs#8]:samples/csharp_dotnetcore/08.suggested-actions
 [cs#11]:samples/csharp_dotnetcore/11.qnamaker
 [cs#13]:samples/csharp_dotnetcore/13.core-bot
+[cs#13.b]:samples/csharp_dotnetcore/13.core-bot.tests
 [cs#14]:samples/csharp_dotnetcore/14.nlp-with-dispatch
 [cs#15]:samples/csharp_dotnetcore/15.handling-attachments
 [cs#16]:samples/csharp_dotnetcore/16.proactive-messages
@@ -67,6 +71,8 @@ Samples are designed to illustrate scenarios you'll need to implement to build g
 [cs#43]:samples/csharp_dotnetcore/43.complex-dialog
 [cs#44]:samples/csharp_dotnetcore/44.prompt-users-for-input
 [cs#45]:samples/csharp_dotnetcore/45.state-management
+[cs#46]:samples/csharp_dotnetcore/46.teams-auth
+[cs#47]:samples/csharp_dotnetcore/47.inspection
 [cs#52]:https://github.com/Microsoft/AI/tree/master/templates/Enterprise-Template
 
 [wa#13]:samples/csharp_webapi/13.core-bot
@@ -103,6 +109,8 @@ Samples are designed to illustrate scenarios you'll need to implement to build g
 [js#43]:samples/javascript_nodejs/43.complex-dialog
 [js#44]:samples/javascript_nodejs/44.prompt-for-user-input
 [js#45]:samples/javascript_nodejs/45.state-management
+[js#46]:samples/javascript_nodejs/46.teams-auth
+[js#47]:samples/javascript_nodejs/47.inspection
 
 
 ## Contributing

samples/csharp_dotnetcore/47.inspection/README.md

@@ -1,12 +1,11 @@
-# EchoBot
+# Inspection Bot
 
 Bot Framework v4 Inspection Middleware sample.
 
-This bot demonstrates a feature called Inspection. This feature allows the bot emulator to debug traffic into and out of the bot in addition to
-looking at the current state of the bot. This is done by having this data sent to the emulator using trace messages.
+This bot demonstrates a feature called Inspection. This feature allows the Bot Framework Emulator to debug traffic into and out of the bot in addition to looking at the current state of the bot. This is done by having this data sent to the emulator using trace messages.
 
 This bot has been created using [Bot Framework](https://dev.botframework.com), it shows how to create a simple bot that accepts input from the user and echoes it back.
-Included in this echo are two counters maintained in User and Conversation state to demonstrate the ability to look at state.
+Included in this sample are two counters maintained in User and Conversation state to demonstrate the ability to look at state.
 
 This runtime behavior is achieved by simply adding a middleware to the bot. In this sample you can find that being done in the
 AdapterWithInspection class.
@@ -30,7 +29,7 @@ More details are available [here](https://github.com/microsoft/BotFramework-Emul
     git clone https://github.com/Microsoft/botbuilder-samples.git
     ```
 
-- In a terminal, navigate to `samples/csharp_dotnetcore/02.echo-bot`
+- In a terminal, navigate to `samples/csharp_dotnetcore/47.inspection`
 - Run the bot from a terminal or from Visual Studio, choose option A or B.
 
   A) From a terminal
@@ -62,9 +61,9 @@ More details are available [here](https://github.com/microsoft/BotFramework-Emul
 
 ### Special Instructions for Running Inspection
 
-(Note the follow applies if you are using two emulators. More recnt builds hide the need to type /INSPECT open.)
+(Note the follow applies if you are using two emulators. More recent builds of the Bot Framework Emulator hide the need to type /INSPECT open.)
 
-- Lanuch a second Emulator - this will act as the debugger
+- Launch a second Emulator - this will act as the debugger
 - In this second Emulator type /INSPECT open
 - The result is a trace activity which contains a statement that looks like /INSPECT attach < identifier >
 - In the chat session that you want to inspect type this command exact as it is (you can use cut and paste)