links

Author: eric-urban

articles/cognitive-services/Speech-Service/includes/containers-speech-config.md

@@ -85,6 +85,6 @@ speech_config = speechsdk.SpeechConfig(
 ::: zone-end
 
 ::: zone pivot="programming-language-cli"
-For information about how to configure the Speech CLI, see [Get started with the Azure Speech CLI](spx-basics.md?tabs=dockerinstall#download-and-install).
+For information about how to configure the Speech CLI, see [Get started with the Azure Speech CLI](../spx-basics.md?tabs=dockerinstall#download-and-install).
 ::: zone-end
 

articles/cognitive-services/Speech-Service/includes/release-notes/release-notes-containers.md

@@ -156,7 +156,7 @@ Bug fixes for [speech-language-detection](~/articles/cognitive-services/speech-s
 ### 2022-March release
 
 #### Custom speech-to-text Container v3.1.0
-Add support to [get display models](../../speech-container-howto.md#display-model-download-on-the-custom-speech-to-text-container).
+Add support to [get display models](../../speech-container-cstt.md#display-model-download-on-the-custom-speech-to-text-container).
 
 ### 2022-January release
 

articles/cognitive-services/Speech-Service/language-support.md

@@ -75,7 +75,7 @@ Each prebuilt neural voice model is available at 24kHz and high-fidelity 48kHz.
 
 Please note that the following neural voices are retired.
 
-- The English (United Kingdom) voice `en-GB-MiaNeural` retired on October 30, 2021. All service requests to `en-GB-MiaNeural` will be redirected to `en-GB-SoniaNeural` automatically as of October 30, 2021. If you're using container Neural TTS, [download](speech-container-howto.md#get-the-container-image-with-docker-pull) and deploy the latest version. Starting from October 30, 2021, all requests with previous versions will not succeed.
+- The English (United Kingdom) voice `en-GB-MiaNeural` retired on October 30, 2021. All service requests to `en-GB-MiaNeural` will be redirected to `en-GB-SoniaNeural` automatically as of October 30, 2021. If you're using container Neural TTS, [download](speech-container-ntts.md#get-the-container-image-with-docker-pull) and deploy the latest version. Starting from October 30, 2021, all requests with previous versions will not succeed.
 - The `en-US-JessaNeural` voice is retired and replaced by `en-US-AriaNeural`. If you were using "Jessa" before, convert  to "Aria." 
 
 ### Custom Neural Voice

articles/cognitive-services/Speech-Service/speech-container-batch-processing.md

@@ -18,7 +18,7 @@ Use the batch processing kit to complement and scale out workloads on Speech con
 
 :::image type="content" source="media/containers/general-diagram.png" alt-text="A diagram showing an example batch-kit container workflow.":::
 
-The batch kit container is available for free on [GitHub](https://github.com/microsoft/batch-processing-kit) and   [Docker hub](https://hub.docker.com/r/batchkit/speech-batch-kit/tags). You are only [billed](speech-container-howto.md#billing) for the Speech containers you use.
+The batch kit container is available for free on [GitHub](https://github.com/microsoft/batch-processing-kit) and   [Docker hub](https://hub.docker.com/r/batchkit/speech-batch-kit/tags). You are only [billed](speech-container-overview.md#billing) for the Speech containers you use.
 
 | Feature  | Description  |
 |---------|---------|

articles/cognitive-services/Speech-Service/speech-container-configuration.md

@@ -23,7 +23,7 @@ The Speech container runtime environment is configured using the `docker run` co
 [!INCLUDE [Container shared configuration settings table](../../../includes/cognitive-services-containers-configuration-shared-settings-table.md)]
 
 > [!IMPORTANT]
-> The [`ApiKey`](#apikey-configuration-setting), [`Billing`](#billing-configuration-setting), and [`Eula`](#eula-setting) settings are used together, and you must provide valid values for all three of them; otherwise your container won't start. For more information about using these configuration settings to instantiate a container, see [Billing](speech-container-howto.md#billing).
+> The [`ApiKey`](#apikey-configuration-setting), [`Billing`](#billing-configuration-setting), and [`Eula`](#eula-setting) settings are used together, and you must provide valid values for all three of them; otherwise your container won't start. For more information about using these configuration settings to instantiate a container, see [Billing](speech-container-overview.md#billing).
 
 ## ApiKey configuration setting
 
@@ -47,7 +47,7 @@ This setting can be found in the following place:
 
 | Required | Name | Data type | Description |
 | -------- | ---- | --------- | ----------- |
-| Yes | `Billing` | String | Billing endpoint URI. For more information on obtaining the billing URI, see [gather required parameters](speech-container-howto.md#gather-required-parameters). For more information and a complete list of regional endpoints, see [Custom subdomain names for Cognitive Services](../cognitive-services-custom-subdomains.md). |
+| Yes | `Billing` | String | Billing endpoint URI. For more information on obtaining the billing URI, see [billing](speech-container-overview.md#billing). For more information and a complete list of regional endpoints, see [Custom subdomain names for Cognitive Services](../cognitive-services-custom-subdomains.md). |
 
 ## Eula setting
 

articles/cognitive-services/Speech-Service/speech-container-faq.yml

@@ -126,7 +126,7 @@ sections:
       - question: |
           What API protocols are supported, REST or WS?
         answer: |
-          For speech-to-text and custom speech-to-text containers, we currently only support the websocket based protocol. The SDK only supports calling in WS but not REST. Always refer to the official documentation, see [query prediction endpoints](speech-container-howto.md#query-the-containers-prediction-endpoint).
+          For speech-to-text and custom speech-to-text containers, we currently only support the websocket based protocol. The SDK only supports calling in WS but not REST. For more information, see [host URLs](speech-container-howto.md#use-the-speech-service).
           
       - question: |
           Why am I getting errors when attempting to call LUIS prediction endpoints?
@@ -238,7 +238,7 @@ sections:
       - question: |
           Why am I getting 404 errors when attempting to POST data to speech-to-text container?
         answer: |        
-          Speech-to-text containers do not support REST API. The Speech SDK uses WebSockets. Always refer to the official documentation, see [query prediction endpoints](speech-container-howto.md#query-the-containers-prediction-endpoint).
+          Speech-to-text containers do not support REST API. The Speech SDK uses WebSockets. For more information, see [host URLs](speech-container-howto.md##use-the-speech-service).
           
           
       - question:  Why is the container running as a non-root user? What issues might occur because of this?

articles/cognitive-services/Speech-Service/speech-container-howto.md

@@ -50,7 +50,7 @@ The <a href="https://docs.docker.com/engine/reference/commandline/run/" target="
 > [!IMPORTANT]
 > These subscription keys are used to access your Cognitive Services API. Don't share your keys. Store them securely. For example, use Azure Key Vault. We also recommend that you regenerate these keys regularly. Only one key is necessary to make an API call. When you regenerate the first key, you can use the second key for continued access to the service.
 
-The container needs the billing argument values to run. These values allow the container to connect to the billing endpoint. The container reports usage about every 10 to 15 minutes. If the container doesn't connect to Azure within the allowed time window, the container continues to run but doesn't serve queries until the billing endpoint is restored. The connection is attempted 10 times at the same time interval of 10 to 15 minutes. If it can't connect to the billing endpoint within the 10 tries, the container stops serving requests. See the [Cognitive Services container FAQ](../articles/cognitive-services/containers/container-faq.yml#how-does-billing-work) for an example of the information sent to Microsoft for billing.
+The container needs the billing argument values to run. These values allow the container to connect to the billing endpoint. The container reports usage about every 10 to 15 minutes. If the container doesn't connect to Azure within the allowed time window, the container continues to run but doesn't serve queries until the billing endpoint is restored. The connection is attempted 10 times at the same time interval of 10 to 15 minutes. If it can't connect to the billing endpoint within the 10 tries, the container stops serving requests. See the [Cognitive Services container FAQ](../containers/container-faq.yml#how-does-billing-work) for an example of the information sent to Microsoft for billing.
 
 For more information about these options, see [Configure containers](speech-container-configuration.md).
 
@@ -72,15 +72,15 @@ Core and memory correspond to the `--cpus` and `--memory` settings, which are us
 
 > [!NOTE]
 > The minimum and recommended allocations are based on Docker limits, *not* the host machine resources.
-> For example, speech-to-text containers memory map portions of a large language model. We recommend that the entire file should fit in memory. You need to add an additional 4 to 8 GB to load the speech modesl (see above table).
+> For example, speech-to-text containers memory map portions of a large language model. We recommend that the entire file should fit in memory. You need to add an additional 4 to 8 GB to load the speech models (see above table).
 > Also, the first run of either container might take longer because models are being paged into memory.
 
 ## Host computer requirements and recommendations
 
 The host is an x64-based computer that runs the Docker container. It can be a computer on your premises or a Docker hosting service in Azure, such as:
 
-* [Azure Kubernetes Service](../articles/aks/index.yml).
-* [Azure Container Instances](../articles/container-instances/index.yml).
+* [Azure Kubernetes Service](~/articles/aks/index.yml).
+* [Azure Container Instances](~/articles/container-instances/index.yml).
 * A [Kubernetes](https://kubernetes.io/) cluster deployed to [Azure Stack](/azure-stack/operator). For more information, see [Deploy Kubernetes to Azure Stack](/azure-stack/user/azure-stack-solution-template-kubernetes-deploy).
 
 
@@ -159,7 +159,7 @@ For more information on using WSS and HTTPS protocols, see [Container security](
 When you start or run the container, you might experience issues. Use an output [mount](speech-container-configuration.md#mount-settings) and enable logging. Doing so allows the container to generate log files that are helpful when you troubleshoot issues.
 
 > [!TIP]
-> For more troubleshooting information and guidance, see [Cognitive Services containers frequently asked questions (FAQ)](../container-faq.yml).
+> For more troubleshooting information and guidance, see [Cognitive Services containers frequently asked questions (FAQ)](../containers/container-faq.yml).
 
 
 ### Logging settings
@@ -235,7 +235,7 @@ Placeholder | Value | Format or example |
  `{MEMORY_SIZE}` | The appropriate size of memory to allocate for your container.<br/><br/>For example: `4g` |
 | `{NUMBER_CPUS}` | The appropriate number of CPUs to allocate for your container.<br/><br/>For example: `4` |
 | `{LICENSE_MOUNT}` | The path where the license will be located and mounted.<br/><br/>For example: `/host/license:/path/to/license/directory` |
-| `{OUTPUT_PATH}` | The output path for logging [usage records](../disconnected-containers.md#usage-records).<br/><br/>For example: `/host/output:/path/to/output/directory` |
+| `{OUTPUT_PATH}` | The output path for logging [usage records](../containers/disconnected-containers.md#usage-records).<br/><br/>For example: `/host/output:/path/to/output/directory` |
 | `{CONTAINER_LICENSE_DIRECTORY}` | Location of the license folder on the container's local filesystem.<br/><br/>For example: `/path/to/license/directory` |
 | `{CONTAINER_OUTPUT_DIRECTORY}` | Location of the output folder on the container's local filesystem.<br/><br/>For example: `/path/to/output/directory` |
 

articles/cognitive-services/Speech-Service/speech-container-overview.md

@@ -39,9 +39,9 @@ The following table lists the Speech containers available in the Microsoft Conta
 
 ## Request approval to run the container
 
-To use the Speech containers, you must submit a request form and wait for approval. Fill out and submit a request form to request access to a connected or disconnected container. 
-* For connected containers, you must submit [this request form](https://aka.ms/csgate) and wait for approval.
-* For disconnected containers (not connected to the internet), you must submit [this request form](https://aka.ms/csdisconnectedcontainers) and wait for approval. When you are approved for a disconnected container, you are also permitted to use the corresponding connected container. For more information about applying and purchasing a commitment plan to use containers in disconnected environments, see [Use containers in disconnected environments](../containers/disconnected-containers.md#request-access-to-use-containers-in-disconnected-environments).
+To use the Speech containers, you must submit one of the following request forms and wait for approval:
+-	[Connected containers request form](https://aka.ms/csgate) if you want to run containers regularly, in environments that are only connected to the internet.
+-	[Disconnected Container request form](https://aka.ms/csdisconnectedcontainers) if you want to run containers in environments that can either be connected or disconnected from the internet. For more information about applying and purchasing a commitment plan to use containers in disconnected environments, see [Use containers in disconnected environments](../containers/disconnected-containers.md#request-access-to-use-containers-in-disconnected-environments).
 
 The form requests information about you, your company, and the user scenario for which you'll use the container. 
 
@@ -54,17 +54,14 @@ After you submit the form, the Azure Cognitive Services team reviews it and emai
 > [!IMPORTANT]
 > To use the Speech containers, your request must be approved. 
 
-While you're waiting for approval, you can [setup the prerequisites](speech-containers-howto.md#prerequisites) on your host computer. You can also download the container from the Microsoft Container Registry (MCR). You can run the container after your request is approved.
-
+While you're waiting for approval, you can [setup the prerequisites](speech-container-howto.md#prerequisites) on your host computer. You can also download the container from the Microsoft Container Registry (MCR). You can run the container after your request is approved.
 
 ## Billing
 
 The Speech containers send billing information to Azure by using a Speech resource on your Azure account. 
 
 Speech containers aren't licensed to run without being connected to Azure for metering. You must configure your container to communicate billing information with the metering service at all times. For more information, see [billing arguments](speech-container-howto.md#billing-arguments). 
 
-
-
 ## Next steps
 
 * [Install and run Speech containers](speech-container-howto.md)

articles/cognitive-services/Speech-Service/speech-container-stt.md

@@ -171,18 +171,18 @@ Starting in v2.6.0 of the speech-to-text container, you can get the output with
 To configure a phrase list, you need to add your own phrases when you make the call. For example:
 
 ```python
-    phrase="the tall man"
-    recognizer = speechsdk.SpeechRecognizer(
-        speech_config=dict_speech_config,
-        audio_config=audio_config)
-    phrase_list_grammer = speechsdk.PhraseListGrammar.from_recognizer(recognizer)
-    phrase_list_grammer.addPhrase(phrase)
-    
-    dict_speech_config.set_service_property(
-        name='setflight',
-        value='xonlineinterp',
-        channel=speechsdk.ServicePropertyChannel.UriQueryParameter
-    )
+phrase="the tall man"
+recognizer = speechsdk.SpeechRecognizer(
+    speech_config=dict_speech_config,
+    audio_config=audio_config)
+phrase_list_grammer = speechsdk.PhraseListGrammar.from_recognizer(recognizer)
+phrase_list_grammer.addPhrase(phrase)
+
+dict_speech_config.set_service_property(
+    name='setflight',
+    value='xonlineinterp',
+    channel=speechsdk.ServicePropertyChannel.UriQueryParameter
+)
 ```
 
 If you have multiple phrases to add, call `.addPhrase()` for each phrase to add it to the phrase list.

articles/cognitive-services/containers/container-faq.yml

@@ -97,7 +97,7 @@ sections:
           * [Face](../face/overview.md)
           * [Form Recognizer](../../applied-ai-services/form-recognizer/containers/form-recognizer-container-install-run.md#billing)
           * [Language Understanding (LUIS)](../luis/luis-container-howto.md#billing)
-          * [Speech Service API](../speech-service/speech-container-howto.md#billing)
+          * [Speech service](../speech-service/speech-container-overview.md#billing)
           * [Language service - sentiment analysis](../language-service/sentiment-opinion-mining/how-to/use-containers.md#billing)
           * [Language service - Text Analytics for health](../language-service/text-analytics-for-health/how-to/use-containers.md#billing)
           * [Language service - language detection](../language-service/language-detection/how-to/use-containers.md#billing)