Sweep++

Author: IEvangelist

articles/cognitive-services/Speech-Service/direct-line-speech.md

@@ -8,11 +8,11 @@ manager: nitinme
 ms.service: cognitive-services
 ms.subservice: speech-service
 ms.topic: conceptual
-ms.date: 01/31/2020
+ms.date: 03/11/2020
 ms.author: dapine
 ---
 
-# About Direct Line Speech
+# What is Direct Line Speech?
 
 **Direct Line Speech** is a robust, end-to-end solution for creating a flexible, extensible voice assistant. It is powered by the Bot Framework and its Direct Line Speech channel, that is optimized for voice-in, voice-out interaction with bots.
 

articles/cognitive-services/Speech-Service/index-voice-assistants.yml

@@ -15,32 +15,22 @@ metadata:
   ms.author: dapine
 
 landingContent:
-- title: About Voice Assistants
+- title: About voice assistants
   linkLists:
     - linkListType: overview
       links:
       - text: What is a voice assistant?
         url: voice-assistants.md
-      - text: What is Custom Commands?
+      - text: What are Custom Commands?
         url: custom-commands.md
       - text: What is Direct Line Speech?
         url: direct-line-speech.md
     - linkListType: reference
       links:
-        - text: Pricing
-          url: https://azure.microsoft.com/pricing/details/cognitive-services/speech-services
         - text: Voice assistants FAQ
           url: faq-voice-assistants.md
-- title: Develop with Custom Keyword
-  linkLists:
-    - linkListType: how-to-guide
-      links:
-        - text: Create a Custom Keyword
-          url: speech-devices-sdk-create-kws.md
-    - linkListType: reference
-      links:
-        - text: Custom Keyword naming guidelines
-          url: speech-devices-sdk-kws-guidelines.md
+        - text: Voice assistants pricing
+          url: https://azure.microsoft.com/pricing/details/cognitive-services/speech-services
 - title: Develop with Custom Commands
   linkLists:
     - linkListType: quickstart
@@ -55,15 +45,13 @@ landingContent:
           url: quickstart-custom-speech-commands-speech-sdk.md
     - linkListType: how-to-guide
       links:
-      - text: Custom Commands with the Speech SDK
+      - text: Handle Custom Commands on the client
         url: how-to-custom-speech-commands-fulfill-sdk.md
-      - text: Fulfill Custom Commands with the Speech SDK
-        url: how-to-custom-speech-commands-fulfill-sdk.md
-      - text: Add parameter validation to a Custom Command
+      - text: Add parameter validation
         url: how-to-custom-speech-commands-validations.md
-      - text: Add a confirmation to a Custom Command
+      - text: Add a confirmation
         url: how-to-custom-speech-commands-confirmations.md
-      - text: Add a one-step correction to a Custom Command
+      - text: Add a one-step correction
         url: how-to-custom-speech-commands-one-step-correction.md
 - title: Develop with Direct Line Speech
   linkLists:
@@ -78,4 +66,14 @@ landingContent:
     - linkListType: tutorial
       links:
         - text: Voice enable your bot with Speech SDK
-          url: tutorial-voice-enable-your-bot-speech-sdk.md
+          url: tutorial-voice-enable-your-bot-speech-sdk.md
+- title: Develop with Custom Keyword
+  linkLists:
+    - linkListType: how-to-guide
+      links:
+        - text: Create a Custom Keyword
+          url: speech-devices-sdk-create-kws.md
+    - linkListType: reference
+      links:
+        - text: Custom Keyword naming guidelines
+          url: speech-devices-sdk-kws-guidelines.md

articles/cognitive-services/Speech-Service/speech-devices-sdk-kws-guidelines.md

@@ -8,7 +8,7 @@ manager: nitinme
 ms.service: cognitive-services
 ms.subservice: speech-service
 ms.topic: conceptual
-ms.date: 12/11/2019
+ms.date: 03/11/2020
 ms.author: dapine
 ---
 
@@ -20,21 +20,15 @@ Creating an effective keyword is vital to ensuring your device will consistently
 
 Consider the following guidelines when you choose a keyword:
 
-* Your keyword should be an English word or phrase.
-
-* It should take no longer than two seconds to say.
-
-* Words of 4 to 7 syllables work best. For example, "Hey, Computer" is a good keyword. Just "Hey" is a poor one.
-
-* Keywords should follow common English pronunciation rules.
-
-* A unique or even a made-up word that follows common English pronunciation rules might reduce false positives. For example, "computerama" might be a good keyword.
-
-* Do not choose a common word. For example, "eat" and "go" are words that people say frequently in ordinary conversation. They might be false triggers for your device.
-
-* Avoid using a keyword that might have alternative pronunciations. Users would have to know the "right" pronunciation to get their device to respond. For example, "509" can be pronounced "five zero nine," "five oh nine," or "five hundred and nine." "R.E.I." can be pronounced "r-e-i" or "ray." "Live" can be pronounced "/līv/" or "/liv/".
-
-* Do not use special characters, symbols, or digits. For example, "Go#" and "20 + cats" could be problematic keywords. However, "go sharp" or "twenty plus cats" might work. You can still use the symbols in your branding and use marketing and documentation to reinforce the proper pronunciation.
+> [!div class="checklist"]
+> * Your keyword should be an English word or phrase.
+> * It should take no longer than two seconds to say.
+> * Words of 4 to 7 syllables work best. For example, "Hey, Computer" is a good keyword. Just "Hey" is a poor one.
+> * Keywords should follow common English pronunciation rules.
+> * A unique or even a made-up word that follows common English pronunciation rules might reduce false positives. For example, "computerama" might be a good keyword.
+> * Do not choose a common word. For example, "eat" and "go" are words that people say frequently in ordinary conversation. They might be false triggers for your device.
+> * Avoid using a keyword that might have alternative pronunciations. Users would have to know the "right" pronunciation to get their device to respond. For example, "509" can be pronounced "five zero nine," "five oh nine," or "five hundred and nine." "R.E.I." can be pronounced "r-e-i" or "ray." "Live" can be pronounced "/līv/" or "/liv/".
+> * Do not use special characters, symbols, or digits. For example, "Go#" and "20 + cats" could be problematic keywords. However, "go sharp" or "twenty plus cats" might work. You can still use the symbols in your branding and use marketing and documentation to reinforce the proper pronunciation.
 
 > [!NOTE]
 > If you choose a trademarked word as your keyword, be sure that you own that trademark or that you have permission from the trademark owner to use the word. Microsoft is not liable for any legal issues that might arise from your choice of keyword.

articles/cognitive-services/Speech-Service/toc.yml

@@ -386,13 +386,13 @@
               href: quickstart-custom-speech-commands-speech-sdk.md
         - name: How-to guides
           items:
-            - name: Fulfill Custom Commands with the Speech SDK
+            - name: Handle Custom Commands
               href: how-to-custom-speech-commands-fulfill-sdk.md
-            - name: Add parameter validation to a Custom Command
+            - name: Add parameter validation
               href: how-to-custom-speech-commands-validations.md
-            - name: Add a confirmation to a Custom Command
+            - name: Add a confirmation
               href: how-to-custom-speech-commands-confirmations.md
-            - name: Add a one-step correction to a Custom Command
+            - name: Add a one-step correction
               href: how-to-custom-speech-commands-one-step-correction.md
     - name: Direct Line Speech
       items: