Merge pull request #413 from eric-urban/eur/speech-refresh

speech docs refresh

Author: denrea

articles/ai-services/.openpublishing.redirection.ai-services.json

@@ -415,6 +415,11 @@
       "redirect_url": "/azure/ai-services/speech-service/intent-recognition",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/ai-services/speech-service/how-to-custom-speech-continuous-integration-continuous-deployment.md",
+      "redirect_url": "/azure/ai-services/speech-service/how-to-custom-speech-model-and-endpoint-lifecycle",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/ai-services/anomaly-detector/how-to/postman.md",
       "redirect_url": "/azure/ai-services/anomaly-detector/overview",

articles/ai-services/speech-service/how-to-custom-speech-continuous-integration-continuous-deployment.md

@@ -388,5 +388,5 @@ Logging data is available on Microsoft-owned storage for 30 days, and then it's
 
 ## Related content
 
-- [CI/CD for custom speech](how-to-custom-speech-continuous-integration-continuous-deployment.md)
+- [Custom speech overview](custom-speech-overview.md)
 - [Custom speech model lifecycle](how-to-custom-speech-model-and-endpoint-lifecycle.md)

articles/ai-services/speech-service/how-to-custom-speech-deploy-model.md

@@ -277,7 +277,7 @@ You should receive a response body in the following format:
 
 ::: zone-end
 
-## Next steps
+## Related content
 
 - [Train a model](how-to-custom-speech-train-model.md)
-- [CI/CD for custom speech](how-to-custom-speech-continuous-integration-continuous-deployment.md)
+- [Custom speech overview](custom-speech-overview.md)

articles/ai-services/speech-service/how-to-custom-speech-model-and-endpoint-lifecycle.md

@@ -0,0 +1,13 @@
+---
+title: include file
+description: include file
+author: eric-urban
+ms.author: eur
+ms.service: azure-ai-speech
+ms.topic: include
+ms.date: 9/20/2024
+ms.custom: include
+---
+
+> [!NOTE]
+> This feature is currently in public preview. This preview is provided without a service-level agreement, and is not recommended for production workloads. Certain features might not be supported or might have constrained capabilities. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).

articles/ai-services/speech-service/includes/previews/preview-generic.md

@@ -6,9 +6,10 @@ author: eric-urban
 manager: nitinme
 ms.service: azure-ai-speech
 ms.topic: overview
-ms.date: 9/9/2024
+ms.date: 9/20/2024
 ms.author: eur
 ms.custom: cogserv-non-critical-speech, references_regions
+#Customer intent: For developers who want to use the conversation transcription feature in the Speech service to transcribe meetings.
 ---
 
 # What is conversation transcription multichannel diarization? (preview)

articles/ai-services/speech-service/includes/previews/preview-personal-voice.md

@@ -2,22 +2,24 @@
 title: Migrate to Batch synthesis API - Speech service
 titleSuffix: Azure AI services
 description: This document helps developers migrate code from Long Audio REST API to Batch synthesis REST API.
-author: heikora
-manager: dongli
+author: eric-urban
+ms.author: eur
+manager: nitinme
 ms.service: azure-ai-speech
 ms.topic: reference
-ms.date: 1/21/2024
-ms.author: heikora
+ms.date: 9/20/2024
+ms.reviewer: heikora
 ms.devlang: csharp
 ms.custom: devx-track-csharp
+#Customer intent: As a developer, I want to migrate code from Long Audio REST API to Batch synthesis REST API in the Speech service.
 ---
 
 # Migrate code from Long Audio API to Batch synthesis API
 
 The [Batch synthesis API](batch-synthesis.md) provides asynchronous synthesis of long-form text to speech. This article describes the benefits of upgrading from Long Audio API to Batch synthesis API, and details about how to do so.
 
 > [!IMPORTANT]
-> [Batch synthesis API](batch-synthesis.md) is generally available. the Long Audio API will be retired on April 1st, 2027.
+> [Batch synthesis API](batch-synthesis.md) is generally available. the Long Audio API is retiring on April 1st, 2027.
 
 ## Base path and version
 

articles/ai-services/speech-service/meeting-transcription.md

@@ -6,16 +6,16 @@ author: eric-urban
 manager: nitinme
 ms.service: azure-ai-speech
 ms.topic: how-to
-ms.date: 1/21/2024
+ms.date: 9/20/2024
 ms.author: eur
+#Customer intent: As a developer, I want to migrate code from v3 text to speech REST API to custom voice REST API in the Speech service.
 ---
 
 # Migrate to custom voice REST API (Preview)
 
-The custom voice REST API is a new version of the text to speech REST API. You can deploy and use custom neural voice models with the API. 
+[!INCLUDE [Feature preview](./includes/previews/preview-generic.md)]
 
-> [!NOTE]
-> The custom voice REST API is currently in preview. 
+The custom voice REST API is a new version of the text to speech REST API. You can deploy and use custom neural voice models with the API. 
 
 In this article, you learn how to migrate code from the v3 text to speech REST API to the custom voice REST API.
 

articles/ai-services/speech-service/migrate-to-batch-synthesis.md

@@ -2,14 +2,16 @@
 title: Migrate from v3.0 to v3.1 REST API - Speech service
 titleSuffix: Azure AI services
 description: This document helps developers migrate code from v3.0 to v3.1 of the Speech to text REST API.
-author: heikora
-manager: dongli
+author: eric-urban
+ms.author: eur
+manager: nitinme
 ms.service: azure-ai-speech
 ms.topic: how-to
-ms.date: 9/15/2024
-ms.author: heikora
+ms.date: 9/20/2024
+ms.reviewer: heikora
 ms.devlang: csharp
 ms.custom: devx-track-csharp
+#Customer intent: As a developer, I want to migrate code from v3.0 to v3.1 of the Speech to text REST API.
 ---
 
 # Migrate code from v3.0 to v3.1 of the REST API