remove v4 references

Author: laujan

articles/ai-services/translator/text-translation/how-to/migrate-to-v3.md

@@ -1,27 +1,27 @@
 ---
-title: Migrate to v3 - Azure AI Translator
+title: Migrate to V3 - Azure AI Translator
 titleSuffix: Azure AI services
-description: This article provides the steps to help you migrate from V2 to v3 of the Azure AI Translator.
+description: This article provides the steps to help you migrate from V2 to V3 of the Azure AI Translator.
 author: laujan
 manager: nitinme
 ms.service: azure-ai-translator
 ms.topic: conceptual
-ms.date: 04/15/2025
+ms.date: 04/14/2025
 ms.author: lajanuar
 ---
 
-# Azure AI Translator v3 migration
+# Azure AI Translator V3 Migration
 
 > [!NOTE]
-> Microsoft Translator V2 was deprecated on April 30, 2018. Migrate your applications to v3 and experience new functionality available exclusively in v3. Translator v2 was retired on May 24, 2021.
+> Microsoft Translator V2 was deprecated on April 30, 2018. Migrate your applications to V3 and experience new functionality available exclusively in V3. V2 was retired on May 24, 2021.
 
-Azure AI Translator Version 3 (v3) is generally available. The release includes new features, deprecated methods and a new format for sending to, and receiving data from the Microsoft Translator Service. This document provides information for changing applications to use v3.
+Azure AI Translator Version 3 (V3) is generally available. The release includes new features, deprecated methods and a new format for sending to, and receiving data from the Microsoft Translator Service. This document provides information for changing applications to use V3.
 
 The end of this document contains helpful links for you to learn more.
 
 ## Summary of features
 
-* No Trace - In v3 No-Trace applies to all pricing tiers in the Azure portal. This feature means that the service doesn't save text submitted to the v3 API.
+* No Trace - In V3 No-Trace applies to all pricing tiers in the Azure portal. This feature means that the service doesn't save text submitted to the V3 API.
 * JSON - XML replaces JSON. All data sent to the service and received from the service is in JSON format.
 * Multiple target languages in a single request - The Translate method accepts multiple `to` languages for translation in a single request. For example, a single request can be `from` English and `to` German, Spanish and Japanese, or any other group of languages.
 * Bilingual dictionary - A bilingual dictionary method is added to the API. This method includes `lookup` and `examples`.
@@ -30,9 +30,9 @@ The end of this document contains helpful links for you to learn more.
 * New to Translate - New capabilities are added to the `translate` method to support some of the features that were in the V2 API as separate methods. An example is TranslateArray.
 * Speech method - Text to speech functionality is no longer supported in the Microsoft Translator. Text to speech functionality is available in [Microsoft Speech Service](../../../speech-service/text-to-speech.md).
 
-The following list of V2 and v3 methods identifies the v3 methods and APIs that provide the functionality that came with V2.
+The following list of V2 and V3 methods identifies the V3 methods and APIs that provide the functionality that came with V2.
 
-| V2 API Method   | v3 API Compatibility |
+| V2 API Method   | V3 API Compatibility |
 |:----------- |:-------------|
 | `Translate`     | [Translate](../reference/v3/translate.md)          |
 | `TranslateArray`      | [Translate](../reference/v3/translate.md)        |
@@ -50,23 +50,23 @@ The following list of V2 and v3 methods identifies the v3 methods and APIs that
 
 ## Move to JSON format
 
-Microsoft Translator Translation V2 accepted and returned data in XML format. In v3, all data sent and received using the API is in JSON format. XML is no longer accepted or returned in v3.
+Microsoft Translator Translation V2 accepted and returned data in XML format. In V3, all data sent and received using the API is in JSON format. XML is no longer accepted or returned in V3.
 
 This change affects several aspects of an application written for the V2 Text translation API. As an example: The Languages API returns language information for text translation, transliteration, and the two dictionary methods. You can request all language information for all methods in one call or request them individually.
 
-The languages method doesn't require authentication; by selecting the following link you can see all the language information for v3 in JSON:
+The languages method doesn't require authentication; by selecting the following link you can see all the language information for V3 in JSON:
 
 [https://api.cognitive.microsofttranslator.com/languages?api-version=3.0&scope=translation,dictionary,transliteration](https://api.cognitive.microsofttranslator.com/languages?api-version=3.0&scope=translation,dictionary,transliteration)
 
 ## Authentication Key
 
-The authentication key used for V2 is accepted for v3. You don't need to get a new subscription. You can mix V2 and v3 in your apps during the yearlong migration period, making it easier for you to release new versions while you migrate from V2-XML to v3-JSON.
+The authentication key used for V2 is accepted for V3. You don't need to get a new subscription. You can mix V2 and V3 in your apps during the yearlong migration period, making it easier for you to release new versions while you migrate from V2-XML to V3-JSON.
 
 ## Pricing Model
 
-Microsoft Translator v3 is priced in the same way V2 was priced; per character, including spaces. The new features in v3 make some changes in what characters are counted for billing.
+Microsoft Translator V3 is priced in the same way V2 was priced; per character, including spaces. The new features in V3 make some changes in what characters are counted for billing.
 
-| v3 Method   | Characters Counted for Billing |
+| V3 Method   | Characters Counted for Billing |
 |:----------- |:-------------|
 | `Languages`     | No characters submitted, none counted, no charge.          |
  | `Translate`     | Count is based on how many characters are submitted for translation, and how many languages the characters are translated into. 50 characters submitted, and 5 counted as 50x5.           |
@@ -75,13 +75,13 @@ Microsoft Translator v3 is priced in the same way V2 was priced; per character,
 | `BreakSentence`     | No Charge.       |
 | `Detect`     | No Charge.      |
 
-## v3 End Points
+## V3 End Points
 
 Global
 
 * api.cognitive.microsofttranslator.com
 
-## v3 API text translations methods
+## V3 API text translations methods
 
 [`Languages`](../reference/v3/languages.md)
 
@@ -103,11 +103,11 @@ Global
 >
 > The Microsoft Translator Hub will be retired on May 17, 2019. [View important migration information and dates](https://www.microsoft.com/translator/business/hub/).
 
-Azure AI Translator v3 uses neural machine translation by default. As such, it can't be used with the Microsoft Translator Hub. The Translator Hub only supports legacy statistical machine translation. Customization for neural translation is now available using the Azure AI Custom Translator. [Learn more about customizing neural machine translation](../../custom-translator/overview.md)
+Azure AI Translator V3 uses neural machine translation by default. As such, it can't be used with the Microsoft Translator Hub. The Translator Hub only supports legacy statistical machine translation. Customization for neural translation is now available using the Azure AI Custom Translator. [Learn more about customizing neural machine translation](../../custom-translator/overview.md)
 
-Neural translation with the v3 text API doesn't support the use of standard categories (`SMT`, `speech`, `tech`, `generalnn`).
+Neural translation with the V3 text API doesn't support the use of standard categories (`SMT`, `speech`, `tech`, `generalnn`).
 
-| Version | Endpoint | GDPR Processor Compliance | Use Translator Hub | Use Custom Translator (preview) |
+| Version | Endpoint | GDPR Processor Compliance | Use Translator Hub | Use Custom Translator (Preview) |
 | :------ | :------- | :------------------------ | :----------------- | :------------------------------ |
 |Translator Version 2|    api.microsofttranslator.com|    No    |Yes    |No|
 |Translator Version 3|    api.cognitive.microsofttranslator.com|    Yes|    No|    Yes|
@@ -116,7 +116,7 @@ Neural translation with the v3 text API doesn't support the use of standard cate
 
 * It's generally available and fully supported.
 * It's GDPR-compliant as a processor and satisfies all ISO 20001 and 20018 as well as SOC 3 certification requirements.
-* It allows you to invoke the neural network translation systems you customized with Custom Translator (preview), the new Translator neural machine translation (NMT) customization feature.
+* It allows you to invoke the neural network translation systems you customized with Custom Translator (Preview), the new Translator neural machine translation (NMT) customization feature.
 * It doesn't provide access to custom translation systems created using the Microsoft Translator Hub.
 
 You're using Version 3 of the Translator if you're using the api.cognitive.microsofttranslator.com endpoint.
@@ -139,4 +139,4 @@ No version of the Azure AI Translator creates a record of your translations. You
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [View Azure AI Translator v3.0 Documentation](../reference/v3/reference.md)
+> [View Azure AI Translator V3.0 Documentation](../reference/v3/reference.md)

articles/ai-services/translator/text-translation/how-to/migrate-to-v4.md

@@ -53,7 +53,7 @@ To call the Translator service via the [REST API](../reference/rest-api-guide.md
 |**Ocp-Apim-Subscription-Region**|The region where your resource was created. |<ul><li>***Required*** when using an Azure AI multi-service or regional (geographic) resource like **West US**.</li><li> ***Optional*** when using a single-service Translator Resource.</li></ul>|
 |**Content-Type**|The content type of the payload. The accepted value is **application/json** or **charset=UTF-8**.|<ul><li>***Required***</li></ul>|
 |**Content-Length**|The **length of the request** body.|<ul><li>***Optional***</li></ul> |
-|**X-ClientTraceId**|A client-generated GUID to uniquely identify the request. You can omit this optional header if you include the trace ID in the query string using a query parameter named ClientTraceId.|<ul><li>***Optional***</li></ul>
+|**X-ClientTraceId**|A client-generated GUID to uniquely identify the request. You can omit this header if you include the trace ID in the query string using a query parameter named ClientTraceId.|<ul><li>***Optional***</li></ul>
 
 ## Set up your application
 
@@ -3123,7 +3123,7 @@ After a successful call, you should see the following response. For more informa
 |------------------|-------------|-----------------|
 | 200 | OK | The request was successful. |
 | 400 | Bad Request | A required parameter is missing, empty, or null. Or, the value passed to either a required or optional parameter is invalid. A common issue is a header that is too long. |
-| 401 | Unauthorized | The request isn't authorized. Check to make sure your key or token is valid and in the correct region. *See also* [Authentication](../reference/authentication.md).|
+| 401 | Unauthorized | The request isn't authorized. Check to make sure your key or token is valid and in the correct region. *See also* [Authentication](../reference/v3/reference.md#authentication).|
 | 429 | Too Many Requests | You exceeded the quota or rate of requests allowed for your subscription. |
 | 502 | Bad Gateway    | Network or server-side issue. May also indicate invalid headers. |
 

articles/ai-services/translator/text-translation/how-to/use-rest-api.md

@@ -26,7 +26,7 @@ Text translation documentation contains the following article types:
 
 * [**Languages**](reference/v3/languages.md). Returns a list of languages supported by **Translate**, **Transliterate**, and **Dictionary Lookup** operations. This request doesn't require authentication; just copy and paste the following GET request into your favorite REST API tool or browser:
 
-    ```bash
+    ```http
     https://api.cognitive.microsofttranslator.com/languages?api-version=3.0
     ```
 
@@ -79,7 +79,7 @@ Customers with a resource located in Switzerland North or Switzerland West can e
 
 For example: If you create a Translator resource in Azure portal with `Resource region` as `Switzerland North` and your resource name is `my-swiss-n`, then your custom endpoint is `https​://my-swiss-n.cognitiveservices.azure.com`. And a sample request to translate is:
 
- ```bash
+```curl
 // Pass secret key and region using headers to a custom endpoint
 curl -X POST "https://my-swiss-n.cognitiveservices.azure.com/translator/text/v3.0/translate?to=fr" \
 -H "Ocp-Apim-Subscription-Key: xxx" \

articles/ai-services/translator/text-translation/overview.md

@@ -63,4 +63,4 @@ That's it, congratulations! In this quickstart, you used a Text translation SDK
 Learn more about Text translation development options:
 
 > [!div class="nextstepaction"]
->[Text translation SDK overview](../../text-sdk-overview.md) </br></br>[Text translation v3 reference](../reference/v3/reference.md)
+>[Text translation SDK overview](../../text-sdk-overview.md) </br></br>[Text translation V3 reference](../reference/v3/reference.md)

articles/ai-services/translator/text-translation/quickstart/client-library-sdk.md

@@ -45,7 +45,7 @@ You need an active Azure subscription. If you don't have an Azure subscription,
 
 To call the Translator service via the [REST API](../reference/rest-api-guide.md), you need to include the following headers with each request. Don't worry, we include the headers for you in the sample code for each programming language.
 
-For more information on Translator authentication options, _see_ the [Translator v3 reference](..//reference/authentication.md) guide.
+For more information on Translator authentication options, _see_ the [Translator v3 reference](..//reference/v3/reference.md#authentication) guide.
 
 Header|Value| Condition  |
 |--- |:--- |:---|