Merge pull request #97771 from markamos/v-ammark-dec18

[Cog Svcs] Fix "Speech service" terminology

Author: American-Dipper

articles/cognitive-services/Speech-Service/record-custom-voice-samples.md

@@ -1,5 +1,5 @@
 ---
-title: "Record custom voice samples - Speech Service"
+title: "Record custom voice samples - Speech service"
 titleSuffix: Azure Cognitive Services
 description: Make a production-quality custom voice by preparing a robust script, hiring good voice talent, and recording professionally.
 services: cognitive-services

articles/cognitive-services/Speech-Service/regions.md

@@ -1,7 +1,7 @@
 ---
-title: Regions - Speech Service
+title: Regions - Speech service
 titleSuffix: Azure Cognitive Services
-description: A list of available regions and endpoints for the Speech Service, including speech-to-text, text-to-speech, and speech translation.
+description: A list of available regions and endpoints for the Speech service, including speech-to-text, text-to-speech, and speech translation.
 services: cognitive-services
 author: mahilleb-msft
 manager: nitinme
@@ -13,7 +13,7 @@ ms.author: panosper
 ms.custom: seodec18
 ---
 
-# Speech Service supported regions
+# Speech service supported regions
 
 The Speech service allows your application to convert audio to text, perform speech translation, and covert text to speech. The service is available in multiple regions with unique endpoints for the Speech SDK and REST APIs.
 

articles/cognitive-services/Speech-Service/releasenotes.md

@@ -1,7 +1,7 @@
 ---
-title: Release Notes - Speech Service
+title: Release Notes - Speech service
 titleSuffix: Azure Cognitive Services
-description: See a running log of feature releases, improvements, bug fixes, and known issues for the Speech Service.
+description: See a running log of feature releases, improvements, bug fixes, and known issues for the Speech service.
 services: cognitive-services
 author: BrianMouncer
 manager: nitinme
@@ -172,7 +172,7 @@ This is a JavaScript-only release. No features have been added. The following fi
 
 **Bug fixes**
 
-- Mac/iOS: A bug that led to a long wait when a connection to the Speech Service could not be established was fixed.
+- Mac/iOS: A bug that led to a long wait when a connection to the Speech service could not be established was fixed.
 - Python: improve error handling for arguments in Python callbacks.
 - JavaScript: Fixed wrong state reporting for speech ended on RequestSession.
 
@@ -188,7 +188,7 @@ This is a bug fix release and only affecting the native/managed SDK. It is not a
 
 **New Features**
 
-- The Speech SDK supports selection of the input microphone through the AudioConfig class. This allows you to stream audio data to the Speech Services from a non-default microphone. For more information, see the documentation describing [audio input device selection](how-to-select-audio-input-devices.md). This feature is not yet available from JavaScript.
+- The Speech SDK supports selection of the input microphone through the AudioConfig class. This allows you to stream audio data to the Speech service from a non-default microphone. For more information, see the documentation describing [audio input device selection](how-to-select-audio-input-devices.md). This feature is not yet available from JavaScript.
 - The Speech SDK now supports Unity in a beta version. Provide feedback through the issue section in the [GitHub sample repository](https://aka.ms/csspeech/samples). This release supports Unity on Windows x86 and x64 (desktop or Universal Windows Platform applications), and Android (ARM32/64, x86). More information is available in our [Unity quickstart](~/articles/cognitive-services/Speech-Service/quickstarts/speech-to-text-from-microphone.md?pivots=programming-language-csharp&tabs=unity).
 - The file `Microsoft.CognitiveServices.Speech.csharp.bindings.dll` (shipped in previous releases) isn't needed anymore. The functionality is now integrated into the core SDK.
 

articles/cognitive-services/Speech-Service/rest-speech-to-text.md

@@ -1,5 +1,5 @@
 ---
-title: Speech-to-text API reference (REST) - Speech Service
+title: Speech-to-text API reference (REST) - Speech service
 titleSuffix: Azure Cognitive Services
 description: Learn how to use the speech-to-text REST API. In this article, you'll learn about authorization options, query options, how to structure a request and receive a response.
 services: cognitive-services
@@ -14,7 +14,7 @@ ms.author: erhopf
 
 # Speech-to-text REST API
 
-As an alternative to the [Speech SDK](speech-sdk.md), Speech Services allows you to convert speech-to-text using a REST API. Each accessible endpoint is associated with a region. Your application requires a subscription key for the endpoint you plan to use.
+As an alternative to the [Speech SDK](speech-sdk.md), the Speech service allows you to convert speech-to-text using a REST API. Each accessible endpoint is associated with a region. Your application requires a subscription key for the endpoint you plan to use.
 
 Before using the speech-to-text REST API, understand:
 
@@ -47,12 +47,12 @@ This table lists required and optional headers for speech-to-text requests.
 
 |Header| Description | Required / Optional |
 |------|-------------|---------------------|
-| `Ocp-Apim-Subscription-Key` | Your Speech Services subscription key. | Either this header or `Authorization` is required. |
+| `Ocp-Apim-Subscription-Key` | Your Speech service subscription key. | Either this header or `Authorization` is required. |
 | `Authorization` | An authorization token preceded by the word `Bearer`. For more information, see [Authentication](#authentication). | Either this header or `Ocp-Apim-Subscription-Key` is required. |
 | `Content-type` | Describes the format and codec of the provided audio data. Accepted values are `audio/wav; codecs=audio/pcm; samplerate=16000` and `audio/ogg; codecs=opus`. | Required |
 | `Transfer-Encoding` | Specifies that chunked audio data is being sent, rather than a single file. Only use this header if chunking audio data. | Optional |
-| `Expect` | If using chunked transfer, send `Expect: 100-continue`. The Speech Services acknowledges the initial request and awaits additional data.| Required if sending chunked audio data. |
-| `Accept` | If provided, it must be `application/json`. The Speech Services provides results in JSON. Some request frameworks provide an incompatible default value. It is good practice to always include `Accept`. | Optional, but recommended. |
+| `Expect` | If using chunked transfer, send `Expect: 100-continue`. The Speech service acknowledges the initial request and awaits additional data.| Required if sending chunked audio data. |
+| `Accept` | If provided, it must be `application/json`. The Speech service provides results in JSON. Some request frameworks provide an incompatible default value. It is good practice to always include `Accept`. | Optional, but recommended. |
 
 ## Audio formats
 
@@ -64,7 +64,7 @@ Audio is sent in the body of the HTTP `POST` request. It must be in one of the f
 | OGG | OPUS | 16-bit | 16 kHz, mono |
 
 >[!NOTE]
->The above formats are supported through REST API and WebSocket in the Speech Services. The [Speech SDK](speech-sdk.md) currently only supports the WAV format with PCM codec.
+>The above formats are supported through REST API and WebSocket in the Speech service. The [Speech SDK](speech-sdk.md) currently only supports the WAV format with PCM codec.
 
 ## Sample request
 
@@ -94,7 +94,7 @@ The HTTP status code for each response indicates success or common errors.
 
 ## Chunked transfer
 
-Chunked transfer (`Transfer-Encoding: chunked`) can help reduce recognition latency. It allows the Speech Services to begin processing the audio file while it is transmitted. The REST API does not provide partial or interim results.
+Chunked transfer (`Transfer-Encoding: chunked`) can help reduce recognition latency. It allows the Speech service to begin processing the audio file while it is transmitted. The REST API does not provide partial or interim results.
 
 This code sample shows how to send audio in chunks. Only the first chunk should contain the audio file's header. `request` is an HTTPWebRequest object connected to the appropriate REST endpoint. `audioFile` is the path to an audio file on disk.
 

articles/cognitive-services/Speech-Service/rest-text-to-speech.md

@@ -1,5 +1,5 @@
 ---
-title: Text-to-speech API reference (REST) - Speech Service
+title: Text-to-speech API reference (REST) - Speech service
 titleSuffix: Azure Cognitive Services
 description: Learn how to use the text-to-speech REST API. In this article, you'll learn about authorization options, query options, how to structure a request and receive a response.
 services: cognitive-services
@@ -14,7 +14,7 @@ ms.author: erhopf
 
 # Text-to-speech REST API
 
-The Speech Services allow you to [convert text into synthesized speech](#convert-text-to-speech) and [get a list of supported voices](#get-a-list-of-voices) for a region using a set of REST APIs. Each available endpoint is associated with a region. A subscription key for the endpoint/region you plan to use is required.
+The Speech service allows you to [convert text into synthesized speech](#convert-text-to-speech) and [get a list of supported voices](#get-a-list-of-voices) for a region using a set of REST APIs. Each available endpoint is associated with a region. A subscription key for the endpoint/region you plan to use is required.
 
 The text-to-speech REST API supports neural and standard text-to-speech voices, each of which supports a specific language and dialect, identified by locale.
 
@@ -162,7 +162,7 @@ This table lists required and optional headers for text-to-speech requests.
 
 ### Audio outputs
 
-This is a list of supported audio formats that are sent in each request as the `X-Microsoft-OutputFormat` header. Each incorporates a bitrate and encoding type. The Speech Services supports 24 kHz, 16 kHz, and 8 kHz audio outputs.
+This is a list of supported audio formats that are sent in each request as the `X-Microsoft-OutputFormat` header. Each incorporates a bitrate and encoding type. The Speech service supports 24 kHz, 16 kHz, and 8 kHz audio outputs.
 
 |||
 |-|-|

articles/cognitive-services/Speech-Service/scenario-availability.md

@@ -1,5 +1,5 @@
 ---
-title: Scenario Availability - Speech Service
+title: Scenario Availability - Speech service
 titleSuffix: Azure Cognitive Services
 description: The Speech SDK features many scenarios across a wide variety of programming languages and environments. Not all scenarios are available in all programming languages or all environments yet. Listed below is the availability of each scenario.
 services: cognitive-services

articles/cognitive-services/Speech-Service/ship-application.md

@@ -1,5 +1,5 @@
 ---
-title: Develop apps with the Speech SDK - Speech Service
+title: Develop apps with the Speech SDK - Speech service
 titleSuffix: Azure Cognitive Services
 description: Learn how to deploy an application that uses the Speech SDK on supported platforms.
 services: cognitive-services

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

@@ -1,7 +1,7 @@
 ---
 title: Configure Speech containers
 titleSuffix: Azure Cognitive Services
-description: Speech Services provides each container with a common configuration framework, so that you can easily configure and manage storage, logging and telemetry, and security settings for your containers.
+description: Speech service provides each container with a common configuration framework, so that you can easily configure and manage storage, logging and telemetry, and security settings for your containers.
 services: cognitive-services
 author: IEvangelist
 manager: nitinme
@@ -12,7 +12,7 @@ ms.date: 11/07/2019
 ms.author: dapine
 ---
 
-# Configure Speech Service containers
+# Configure Speech service containers
 
 Speech containers enable customers to build one speech application architecture that is optimized to take advantage of both robust cloud capabilities and edge locality. The four speech containers we support now are, **speech-to-text**, **custom-speech-to-text**, **text-to-speech**, and **custom-text-to-speech**.
 

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

@@ -1,5 +1,5 @@
 ---
-title: Use Speech Service container with Kubernetes and Helm
+title: Use Speech service containers with Kubernetes and Helm
 titleSuffix: Azure Cognitive Services
 description: Using Kubernetes and Helm to define the speech-to-text and text-to-speech container images, we'll create a Kubernetes package. This package will be deployed to a Kubernetes cluster on-premises.
 services: cognitive-services
@@ -12,9 +12,9 @@ ms.date: 11/04/2019
 ms.author: dapine
 ---
 
-# Use Speech Service container with Kubernetes and Helm
+# Use Speech service containers with Kubernetes and Helm
 
-One option to manage your Speech containers on-premises is to use Kubernetes and Helm. Using Kubernetes and Helm to define the speech-to-text and text-to-speech container images, we'll create a Kubernetes package. This package will be deployed to a Kubernetes cluster on-premises. Finally, we'll explore how to test the deployed services and various configuration options. For more information about running Docker containers without Kubernetes orchestration, see [install and run Speech Service containers](speech-container-howto.md).
+One option to manage your Speech containers on-premises is to use Kubernetes and Helm. Using Kubernetes and Helm to define the speech-to-text and text-to-speech container images, we'll create a Kubernetes package. This package will be deployed to a Kubernetes cluster on-premises. Finally, we'll explore how to test the deployed services and various configuration options. For more information about running Docker containers without Kubernetes orchestration, see [install and run Speech service containers](speech-container-howto.md).
 
 ## Prerequisites
 
@@ -30,7 +30,7 @@ The following prerequisites before using Speech containers on-premises:
 
 ## The recommended host computer configuration
 
-Refer to the [Speech Service container host computer][speech-container-host-computer] details as a reference. This *helm chart* automatically calculates CPU and memory requirements based on how many decodes (concurrent requests) that the user specifies. Additionally, it will adjust based on whether optimizations for audio/text input are configured as `enabled`. The helm chart defaults to, two concurrent requests and disabling optimization.
+Refer to the [Speech service container host computer][speech-container-host-computer] details as a reference. This *helm chart* automatically calculates CPU and memory requirements based on how many decodes (concurrent requests) that the user specifies. Additionally, it will adjust based on whether optimizations for audio/text input are configured as `enabled`. The helm chart defaults to, two concurrent requests and disabling optimization.
 
 | Service | CPU / Container | Memory / Container |
 |--|--|--|
@@ -137,7 +137,7 @@ The *Helm chart* contains the configuration of which docker image(s) to pull fro
 
 > A [Helm chart][helm-charts] is a collection of files that describe a related set of Kubernetes resources. A single chart might be used to deploy something simple, like a memcached pod, or something complex, like a full web app stack with HTTP servers, databases, caches, and so on.
 
-The provided *Helm charts* pull the docker images of the Speech Service, both text-to-speech and the speech-to-text services from the `mcr.microsoft.com` container registry.
+The provided *Helm charts* pull the docker images of the Speech service, both text-to-speech and the speech-to-text services from the `mcr.microsoft.com` container registry.
 
 ## Install the Helm chart on the Kubernetes cluster
 

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

@@ -1,5 +1,5 @@
 ---
-title: Install Speech containers - Speech Service
+title: Install Speech containers - Speech service
 titleSuffix: Azure Cognitive Services
 description: Install and run speech containers. Speech-to-text transcribes audio streams to text in real time that your applications, tools, or devices can consume or display. Text-to-speech converts input text into human-like synthesized speech.
 services: cognitive-services
@@ -12,9 +12,9 @@ ms.date: 12/04/2019
 ms.author: dapine
 ---
 
-# Install and run Speech Service containers (Preview)
+# Install and run Speech service containers (Preview)
 
-Containers enable you to run some of the Speech Service APIs in your own environment. Containers are great for specific security and data governance requirements. In this article you'll learn how to download, install, and run a Speech container.
+Containers enable you to run some of the Speech service APIs in your own environment. Containers are great for specific security and data governance requirements. In this article you'll learn how to download, install, and run a Speech container.
 
 Speech containers enable customers to build a speech application architecture that is optimized for both robust cloud capabilities and edge locality. There are four different containers available. The two standard containers are **Speech-to-text** and **Text-to-speech**. The two custom containers are **Custom Speech-to-text** and **Custom Text-to-speech**.
 
@@ -429,5 +429,5 @@ In this article, you learned concepts and workflow for downloading, installing,
 ## Next steps
 
 * Review [configure containers](speech-container-configuration.md) for configuration settings
-* Learn how to [use Speech Service containers with Kubernetes and Helm](speech-container-howto-on-premises.md)
+* Learn how to [use Speech service containers with Kubernetes and Helm](speech-container-howto-on-premises.md)
 * Use more [Cognitive Services containers](../cognitive-services-container-support.md)