assistant docs update

solutions/Custom-Assistant/docs/customassistant-responses.md

@@ -2,24 +2,34 @@
 
 ## Overview
 
-Your Custom Assistant can respond in a variety of ways depending on the scenario and the users active device or conversation canvas. Through the use of the Bot Framework Activity schema both Text and Speak variations of a response are returned enabling the device to make the most appropriate choice.
+Your Custom Assistant can respond in a variety of ways depending on the scenario and the users active device or conversation canvas. Through use of the Bot Framework Activity schema, both `Text` and `Speak` variations of a response are returned enabling the device to make the most appropriate choice.
 
-The same Activity schema supports the attachment of User Experience elements (Adaptive Cards) which can be rendered across a broad range of devices and platforms enabling UX support of responses where appropriate. Where Azure Bot Service Channels (e.g. WebChat, Teams) are being used the Azure Bot Service automatically transforms messages to and from the target canvas meaning Developers don't have to worry about canvas specifics.
+The same Activity schema supports the attachment of User Experience elements through use of [Adaptive Cards](https://www.adaptivecards.io) which can be rendered across a broad range of devices and platforms enabling visual support of responses where appropriate. Where Azure Bot Service Channels (e.g. WebChat, Teams) are being used, the Azure Bot Service automatically transforms messages to and from the target canvas meaning Developers don't have to worry about differences across channel capabilities.
 
-In [device integration](./customassistant-deviceintegration.md) scenarios you receive the Activity and Attachments enabling integration into the native experience.  
+In [device integration](./customassistant-deviceintegration.md) scenarios you receive messages adhering to the Activity schema which may include Attachments thus enabling integration into the native experience.  
 
 ## Activity schema
 
-The Activity schema for the Azure Bot Service can be found [here](https://docs.microsoft.com/en-us/azure/bot-service/bot-service-activities-entities?view=azure-bot-service-4.0). The Activity schema is used for all messages including [Events](./customassistant-events.md).
+The Activity schema for the Azure Bot Service can be found [here](https://github.com/Microsoft/BotBuilder/blob/hub/specs/botframework-activity/botframework-activity.md). The Activity schema is used for all messages including [Events](./customassistant-events.md).
 
 ## Messages and Events
 
-Messages are a specific Type of Activity set through the `ActivityType` property and relate to Messages to and from a user that should be shown/spoken. Events are a different `ActivityType` enabling messages to be *whispered* between the client and Bot and provide an elegant mecahnism for the client to trigger events within the Custom Assistant and vice versa to perform an operation on the device. More information is in the [events](./customassistant-events.md) section. 
-
+Messages are a specific Type of Activity set through the `ActivityType` property and relate to Messages to and from a user that should be shown/spoken. Events are a different `ActivityType` enabling messages to be *whispered* between the client and Bot and provide an elegant mecahnism for the client to trigger events within the Custom Assistant and vice versa to perform an operation on the device. More information is in the [events](./customassistant-events.md) section.
 
 ## Adaptive Cards
 
-Adaptive Cards provide the ability for your Custom Assistant to return User Experience elements (e.g. Cards, Images, Buttons) alongside text base responses. If the device or conversation canvas has a screen these Adaptive Cards can be rendered across a broad range of devices and platforms providing supporting User Experience where appropriate.
+[Adaptive Cards](https://adaptivecards.io) provide the ability for your Custom Assistant to return User Experience elements (e.g. Cards, Images, Buttons) alongside text base responses. If the device or conversation canvas has a screen these Adaptive Cards can be rendered across a broad range of devices and platforms providing supporting User Experience where appropriate.
+
+Sample Adaptive Cards are available on the Adaptive Cards website with the [Calendar](https://adaptivecards.io/samples/WeatherLarge.html) sample being a good example of what's possible.
+
 >TODO Add Adaptive Card links
 >TODO Add Adaptive card example
 
+## Input Hints
+
+Speech scenarios require indication from the Custom Assistant whether further input is required so the client or device can automatically open the microphone. The `inputHint` field on the [Activity](https://github.com/Microsoft/BotBuilder/blob/hub/specs/botframework-activity/botframework-activity.md) provides the mechanism to enable this.
+
+There are three types of Input Hint to consider within your client application.
+- Accepting Input: The Custom Assistant is ready for input but not awaiting a response. This will typically cause the client to close the microphone.
+- Expecting Input: The Custom Assistant is actively awaiting a response and this should cause the client to open the microphone.
+- Ignoring Input: The Custom Assistant is not ready to receive input which would cause the client to not offer the ability to accept input.

solutions/Custom-Assistant/docs/customassistant-skills-productivity-calendar.md

@@ -21,7 +21,7 @@ The following scenarios are currently supported by the Skill:
 
 Your Authentication Connection and corresponding Application Registration should have the following Scopes added:
 
-- User.Read 
+- User.Read
 - Calendars.ReadWrite
 - People.Read