personal voice from local files

Author: eric-urban

articles/ai-services/speech-service/personal-voice-create-consent.md

@@ -16,7 +16,7 @@ ms.author: eur
 
 With the personal voice feature, it's required that every voice be created with explicit consent from the user. A recorded statement from the user is required acknowledging that the customer (Azure AI Speech resource owner) will create and use their voice.
 
-To add user consent to the personal voice project, you get the prerecorded consent audio file from a publicly accessible URL (`Consents_Create`) or upload the audio file (`Consents_Post`). In this article, you add consent from a URL. 
+To add user consent to the personal voice project, you provide the prerecorded consent audio file [from a publicly accessible URL](#add-consent-from-a-url) (`Consents_Create`) or [upload the audio file](#add-consent-from-a-file) (`Consents_Post`).  
 
 ## Consent statement
 
@@ -32,15 +32,15 @@ You can get the consent statement text for each locale from the text to speech G
 
 In this scenario, the audio files must be available locally. 
 
-To add consent to a personal voice project from the URL of an audio file, use the `Consents_Create` operation of the custom voice API. Construct the request body according to the following instructions:
+To add consent to a personal voice project from the URL of an audio file, use the `Consents_Post` operation of the custom voice API. Construct the request body according to the following instructions:
 
 - Set the required `projectId` property. See [create a project](./personal-voice-create-project.md).
 - Set the required `voiceTalentName` property. The voice talent name can't be changed later.
 - Set the required `companyName` property. The company name can't be changed later.
 - Set the required `audiodata` property with the consent audio file. 
 - Set the required `locale` property. This should be the locale of the consent. The locale can't be changed later. You can find the text to speech locale list [here](/azure/ai-services/speech-service/language-support?tabs=tts).
 
-Make an HTTP POST request using the URI as shown in the following `Consents_Create` example. 
+Make an HTTP POST request using the URI as shown in the following `Consents_Post` example. 
 - Replace `YourResourceKey` with your Speech resource key.
 - Replace `YourResourceRegion` with your Speech resource region.
 - Replace `JessicaConsentId` with a consent ID of your choice. The case sensitive ID will be used in the consent's URI and can't be changed later. 
@@ -65,7 +65,7 @@ You should receive a response body in the following format:
 }
 ```
 
-The response header contains the `Operation-Location` property. Use this URI to get details about the `Consents_Create` operation. Here's an example of the response header:
+The response header contains the `Operation-Location` property. Use this URI to get details about the `Consents_Post` operation. Here's an example of the response header:
 
 ```HTTP 201
 Operation-Location: https://eastus.api.cognitive.microsoft.com/customvoice/operations/070f7986-ef17-41d0-ba2b-907f0f28e314?api-version=2023-12-01-preview

articles/ai-services/speech-service/personal-voice-create-voice.md

@@ -21,19 +21,21 @@ You create a speaker profile ID based on the speaker's verbal consent statement
 > [!NOTE]
 > The personal voice ID and speaker profile ID aren't same. You can choose the personal voice ID, but the speaker profile ID is generated by the service. The personal voice ID is used to manage the personal voice. The speaker profile ID is used for text to speech.
 
+You provide the audio files [from a publicly accessible URL](#create-personal-voice-from-a-url) (`PersonalVoices_Create`) or [upload the audio files](#create-personal-voice-from-a-file) (`PersonalVoices_Post`).  
+
 ## Create personal voice from a file
 
 In this scenario, the audio files must be available locally. 
 
-To create a personal voice and get the speaker profile ID, use the `PersonalVoices_Create` operation of the custom voice API. 
+To create a personal voice and get the speaker profile ID, use the `PersonalVoices_Post` operation of the custom voice API. 
 
 Construct the request body according to the following instructions:
 
 - Set the required `projectId` property. See [create a project](./personal-voice-create-project.md).
 - Set the required `consentId` property. See [add user consent](./personal-voice-create-consent.md).
 - Set the required `audiodata` property. You can specify one or more audio files in the same request. 
 
-Make an HTTP POST request using the URI as shown in the following `PersonalVoices_Create` example. 
+Make an HTTP POST request using the URI as shown in the following `PersonalVoices_Post` example. 
 - Replace `YourResourceKey` with your Speech resource key.
 - Replace `YourResourceRegion` with your Speech resource region. 
 - Replace `JessicaPersonalVoiceId` with a personal voice ID of your choice. The case sensitive ID will be used in the personal voice's URI and can't be changed later. 
@@ -59,7 +61,7 @@ You should receive a response body in the following format:
 
 Use the `speakerProfileId` property to integrate personal voice in your text to speech application. For more information, see [use personal voice in your application](./personal-voice-how-to-use.md).
 
-The response header contains the `Operation-Location` property. Use this URI to get details about the `PersonalVoices_Create` operation. Here's an example of the response header:
+The response header contains the `Operation-Location` property. Use this URI to get details about the `PersonalVoices_Post` operation. Here's an example of the response header:
 
 ```HTTP 201
 Operation-Location: https://eastus.api.cognitive.microsoft.com/customvoice/operations/1321a2c0-9be4-471d-83bb-bc3be4f96a6f?api-version=2023-12-01-preview