Merge pull request #5037 from laujan/remove-v4-references-from-custom-branch

remove v4 references

Author: Stacyrch140

articles/ai-services/translator/custom-translator/azure-ai-foundry/beginners-guide.md

@@ -12,9 +12,9 @@ ms.topic: overview
 
 # Azure AI Translator custom translation for beginners
 
- [Custom translation](overview.md) enables you to a build translation system that reflects your business, industry, and domain-specific terminology and style. Training and deploying a custom system is easy and doesn't require any programming skills. The customized translation system seamlessly integrates into your existing applications, workflows, and websites and is available on Azure through the same cloud-based [Microsoft Text Translation API](../../text-translation/reference/v4/translate-api.md) service that powers billions of translations every day.
+ [Custom translation](overview.md) enables you to a build translation system that reflects your business, industry, and domain-specific terminology and style. Training and deploying a custom system is easy and doesn't require any programming skills. The customized translation system seamlessly integrates into your existing applications, workflows, and websites and is available on Azure through the same cloud-based [Microsoft Text Translation API](../../text-translation/reference/v3/translate.md) service that powers billions of translations every day.
 
-[Custom translation](overview.md) empowers you to build a translation system that truly captures your business's unique language, industry terminology, and domain-specific style. With an intuitive interface, training, testing, and deploying your custom model is simple and requires no programming expertise. Seamlessly integrate your tailored translation system into your existing applications, workflows, and websites—all backed by the cloud-based [Azure AI Translator Text Translation API](../../text-translation/reference/v4/translate-api.md?tabs=curl) service that powers billions of translations each day.
+[Custom translation](overview.md) empowers you to build a translation system that truly captures your business's unique language, industry terminology, and domain-specific style. With an intuitive interface, training, testing, and deploying your custom model is simple and requires no programming expertise. Seamlessly integrate your tailored translation system into your existing applications, workflows, and websites—all backed by the cloud-based [Azure AI Translator Text Translation API](../../text-translation/reference/v3/translate.md?tabs=curl) service that powers billions of translations each day.
 
 The platform enables users to build and publish custom translation systems to and from English. The Custom Translator supports more than 100 languages that map directly to the languages available for Neural machine translation (NMT). For a complete list, *see* [Translator language support](../../../language-support.md).
 

articles/ai-services/translator/custom-translator/azure-ai-foundry/concepts/workspace-and-project.md

@@ -22,7 +22,7 @@ A project is private to you and the people you invite into your project. Uninvit
 
 A language pair is a wrapper for a model, documents, and tests. Each language pair automatically includes all documents that are uploaded into that project that
 have the correct language pair. For example, if you have both an English-to-Spanish language pair and a Spanish-to-English language pair, the same documents are
-included in both language pairs. Each project has a Category ID associated with it that is used when querying the [V3 API](../../../text-translation/reference/v4/translate-api.md) for translations. Category ID is parameter used to get translations from a customized system built with custom translation.
+included in both language pairs. Each project has a Category ID associated with it that is used when querying the [V3 API](../../../text-translation/reference/v3/translate.md) for translations. Category ID is parameter used to get translations from a customized system built with custom translation.
 
 ## Language pair categories
 

articles/ai-services/translator/custom-translator/azure-ai-foundry/faq.md

@@ -35,7 +35,7 @@ The deployment generally takes less than an hour.
 
 ## How do you access a deployed system?
 
-Deployed systems can be accessed via the Azure AI Translator Text API V3 by specifying the Category ID. More information about the Translator Text API can be found in the [API Reference](../../text-translation/reference/v4/translate-api.md) webpage.
+Deployed systems can be accessed via the Azure AI Translator Text API V3 by specifying the Category ID. More information about the Translator Text API can be found in the [API Reference](../../text-translation/reference/v3/translate.md) webpage.
 
 ## How do I skip alignment and sentence breaking if my data is already sentence aligned?
 

articles/ai-services/translator/custom-translator/azure-ai-foundry/how-to/translate-with-model.md

@@ -16,7 +16,7 @@ After you deploy your custom translation model, you can access it with the Azure
 
 ## How to translate
 
-1. Use the **Category ID** when making a custom translation request via Microsoft Translator [Text API V3](../../../text-translation/reference/v4/translate-api.md?tabs=curl). 
+1. Use the **Category ID** when making a custom translation request via Microsoft Translator [Text API V3](../../../text-translation/reference/v3/translate.md?tabs=curl). 
 
 1. To find the model **Category ID**, select **Train model** from the left menu then select the model name.
 
@@ -33,7 +33,7 @@ After you deploy your custom translation model, you can access it with the Azure
 
    ```
 
-   More information about the Translator Text API can be found on the [Translator API Reference](../../../text-translation/reference/v4/translate-api.md) page.
+   More information about the Translator Text API can be found on the [Translator API Reference](../../../text-translation/reference/v3/translate.md) page.
 
 1. You can also use **Azure AI Foundry** > **AI Services** > **Language + Translator** > **Translation** > **Text translation**
 

articles/ai-services/translator/custom-translator/azure-ai-foundry/overview.md

@@ -63,7 +63,7 @@ The steps for creating a custom model are as follows:
 
 1. [**Deploy a model**](how-to/deploy-model.md). Your custom model is made available for runtime translation requests in the regions you select.
 
-1. [**Translate text**](../../text-translation/reference/v4/translate-api.md). Use the cloud-based, secure, high performance, highly scalable Azure AI Translator [Text API](../../text-translation/reference/v4/translate-api.md) to make translation requests.
+1. [**Translate text**](../../text-translation/reference/v3/translate.md). Use the cloud-based, secure, high performance, highly scalable Azure AI Translator [Text API](../../text-translation/reference/v3/translate.md) to make translation requests.
 
 ## Next steps
 

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: 05/19/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

@@ -6,7 +6,7 @@ author: laujan
 manager: nitinme
 ms.service: azure-ai-translator
 ms.topic: how-to
-ms.date: 01/28/2025
+ms.date: 05/19/2025
 ms.author: lajanuar
 ---
 

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

@@ -6,7 +6,7 @@ author: laujan
 manager: nitinme
 ms.service: azure-ai-translator
 ms.topic: how-to
-ms.date: 02/11/2025
+ms.date: 05/19/2025
 ms.author: lajanuar
 ---