edit for pub

Author: laujan

articles/applied-ai-services/form-recognizer/concept-custom-template.md

@@ -9,18 +9,27 @@ ms.subservice: forms-recognizer
 ms.topic: conceptual
 ms.date: 10/10/2022
 ms.author: lajanuar
-monikerRange: 'form-recog-3.0.0'
 recommendations: false
 ---
 
 # Custom template document model
 
-**This article applies to:** ![Form Recognizer v3.0 checkmark](media/yes-icon.png) **Form Recognizer v3.0**.
+::: moniker range="form-recog-3.0.0"
+[!INCLUDE [applies to v3.0](includes/applies-to-v3-0.md)]
+::: moniker-end
+
+::: moniker range="form-recog-2.1.0"
+[!INCLUDE [applies to v2.1](includes/applies-to-v2-1.md)]
+::: moniker-end
 
 Custom template (formerly custom form) is an easy-to-train document model that accurately extracts labeled key-value pairs, selection marks, tables, regions, and signatures from documents. Template models use layout cues to extract values from documents and are suitable to extract fields from highly structured documents with defined visual templates.
 
+::: moniker range="form-recog-3.0.0"
+
 Custom template models share the same labeling format and strategy as custom neural models, with support for more field types and languages.
 
+::: moniker-end
+
 ## Model capabilities
 
 Custom template models support key-value pairs, selection marks, tables, signature fields, and selected regions.
@@ -29,6 +38,8 @@ Custom template models support key-value pairs, selection marks, tables, signatu
 |:--:|:--:|:--:|:--:|:--:|
 | Supported| Supported | Supported | Supported| Supported |
 
+::: moniker range="form-recog-3.0.0"
+
 ## Tabular fields
 
 With the release of API versions **2022-06-30-preview** and  later, custom template models will add support for **cross page** tabular fields (tables):  
@@ -38,20 +49,23 @@ With the release of API versions **2022-06-30-preview** and  later, custom templ
 
 Tabular fields are also useful when extracting repeating information within a document that isn't recognized as a table. For example, a repeating section of work experiences in a resume can be labeled and extracted as a tabular field.
 
+::: moniker-end
+
 ## Dealing with variations
 
 Template models rely on a defined visual template, changes to the template will result in lower accuracy. In those instances, split your training dataset to include at least five samples of each template and train a model for each of the variations. You can then [compose](concept-composed-models.md) the models into a single endpoint. For subtle variations, like digital PDF documents and images, it's best to include at least five examples of each type in the same training dataset.
 
 ## Training a model
 
-Template models are available generally [v3.0 API](https://westus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-2022-08-31/operations/BuildDocumentModel) and  [v2.1 API](https://westus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-v2-1/operations/AnalyzeWithCustomForm). If you're starting with a new project or have an existing labeled dataset, work with the v3 API and Form Recognizer Studio to train a custom template model.
+::: moniker range="form-recog-3.0.0"
+
+Custom template models are generally available with the [v3.0 API](https://westus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-2022-08-31/operations/BuildDocumentModel). If you're starting with a new project or have an existing labeled dataset, use the v3 API and Form Recognizer Studio to train a custom template model.
 
 | Model | REST API | SDK | Label and Test Models|
 |--|--|--|--|
 | Custom template  | [Form Recognizer 3.0 ](https://westus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-2022-08-31/operations/AnalyzeDocument)| [Form Recognizer SDK](quickstarts/get-started-sdks-rest-api.md?view=form-recog-3.0.0&preserve-view=true)| [Form Recognizer Studio](https://formrecognizer.appliedai.azure.com/studio)|
-| Custom template | [Form Recognizer 2.1 ](https://westus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-v2-1/operations/AnalyzeWithCustomForm)| [Form Recognizer SDK](quickstarts/get-started-v2-1-sdk-rest-api.md?pivots=programming-language-python)| [Form Recognizer Sample labeling tool](https://fott-2-1.azurewebsites.net/)|
 
-On the v3 API, the build operation to train model supports a new ```buildMode``` property, to train a custom template model, set the ```buildMode``` to ```template```.
+With the v3.0 API, the build operation to train model supports a new ```buildMode``` property, to train a custom template model, set the ```buildMode``` to ```template```.
 
 ```REST
 https://{endpoint}/formrecognizer/documentModels:build?api-version=2022-08-31
@@ -68,10 +82,34 @@ https://{endpoint}/formrecognizer/documentModels:build?api-version=2022-08-31
 }
 ```
 
+::: moniker-end
+
+::: moniker range="form-recog-2.1.0"
+
+Custom (template) models  are generally available with the [v2.1 API](https://westus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-v2-1/operations/AnalyzeWithCustomForm).
+
+| Model | REST API | SDK | Label and Test Models|
+|--|--|--|--|
+| Custom model (template) | [Form Recognizer 2.1 ](https://westus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-v2-1/operations/AnalyzeWithCustomForm)| [Form Recognizer SDK](quickstarts/get-started-v2-1-sdk-rest-api.md?pivots=programming-language-python)| [Form Recognizer Sample labeling tool](https://fott-2-1.azurewebsites.net/)|
+
+::: moniker-end
+
 ## Next steps
 
 Learn to create and compose custom models:
 
+::: moniker range="form-recog-3.0.0"
+
 > [!div class="nextstepaction"]
 > [**Build a custom model**](how-to-guides/build-a-custom-model.md)
 > [**Compose custom models**](how-to-guides/compose-custom-models.md)
+
+::: moniker-end
+
+::: moniker range="form-recog-2.1.0"
+
+> [!div class="nextstepaction"]
+> [**Build a custom model**](concept-custom.md?view=form-recog-2.1.0#build-a-custom-model)
+> [**Compose custom models**](concept-composed-models.md?view=form-recog-2.1.0#development-options)
+
+::: moniker-end

articles/applied-ai-services/form-recognizer/service-limits.md

@@ -25,9 +25,9 @@ recommendations: false
 [!INCLUDE [applies to v2.1](includes/applies-to-v2-1.md)]
 ::: moniker-end
 
-* This article contains a quick reference and the **detailed description** of Azure Form Recognizer service Quotas and Limits for all [pricing tiers](https://azure.microsoft.com/pricing/details/form-recognizer/). It also contains some best practices to avoid request throttling.
+This article contains both a quick reference and detailed description of Azure Form Recognizer service Quotas and Limits for all [pricing tiers](https://azure.microsoft.com/pricing/details/form-recognizer/). It also contains some best practices to avoid request throttling.
 
-## Model usuage
+## Model usage
 
 > [!div class="checklist"]
 >
@@ -55,19 +55,25 @@ recommendations: false
 
 ::: moniker range="form-recog-3.0.0"
 
-## Custom model usuage
+## Custom model usage
+
+> [!div class="checklist"]
+>
+> * [**Custom template model**](concept-custom-template.md)
+> * [**Custom neural model**](concept-custom-neural.md)
+> * [**Composed custom models**](concept-composed-models.md)
 
 |Quota|Free (F0) <sup>1</sup>|Standard (S0)|
 |--|--|--|
 | **Compose Model limit** | 5 | 200 (default value) |
 | Adjustable | No | No |
-| **Training dataset size - Neural** | 1 GB <sup>3</sup> | 1 GB (default value) |
+| **Training dataset size * Neural** | 1 GB <sup>3</sup> | 1 GB (default value) |
 | Adjustable | No | No |
-| **Training dataset size - Template** | 50 MB <sup>4</sup> | 50 MB (default value) |
+| **Training dataset size * Template** | 50 MB <sup>4</sup> | 50 MB (default value) |
 | Adjustable | No | No |
-| **Max number of pages (Training) - Template** | 500 | 500 (default value) |
+| **Max number of pages (Training) * Template** | 500 | 500 (default value) |
 | Adjustable | No | No |
-| **Max number of pages (Training) - Neural** | 50,000 | 50,000 (default value) |
+| **Max number of pages (Training) * Neural** | 50,000 | 50,000 (default value) |
 | Adjustable | No | No |
 | **Custom neural model train** | 10 per month | 10 per month |
 | Adjustable | No |Yes <sup>3</sup>|
@@ -78,6 +84,11 @@ recommendations: false
 
 ## Custom model limits v2.1
 
+> [!div class="checklist"]
+>
+> * [**Custom template model**](concept-custom-template.md)
+> * [**Composed custom models**](concept-composed-models.md)
+
 | Quota | Free (F0) <sup>1</sup> | Standard (S0) |
 |--|--|--|
 | **Compose Model limit** | 5 | 100 (default value) |
@@ -109,8 +120,8 @@ If your application returns Response Code 429 (*Too many requests*) and your wor
 
 To minimize issues related to throttling (Response Code 429), we recommend using the following techniques:
 
-- Implement retry logic in your application
-- Avoid sharp changes in the workload. Increase the workload gradually <br/>
+* Implement retry logic in your application
+* Avoid sharp changes in the workload. Increase the workload gradually <br/>
 *Example.* Your application is using Form Recognizer and your current workload is 10 TPS (transactions per second). The next second you increase the load to 40 TPS (that is four times more). The Service immediately starts scaling up to fulfill the new load, but likely it will not be able to do it within a second, so some of the requests will get Response Code 429.
 
 The next sections describe specific cases of adjusting quotas.
@@ -124,7 +135,7 @@ Increasing the Concurrent Request limit does **not** directly affect your costs.
 
 Existing value of Concurrent Request limit parameter is **not** visible via Azure portal, Command-Line tools, or API requests. To verify the existing value, create an Azure Support Request.
 
-If you would like to increase your transactions per second, you can enable auto scaling on your resource. Follow this document to enable auto scaling on your resource - [enable auto scaling](../../cognitive-services/autoscale.md). You can also submit an increase TPS support request.
+If you would like to increase your transactions per second, you can enable auto scaling on your resource. Follow this document to enable auto scaling on your resource * [enable auto scaling](../../cognitive-services/autoscale.md). You can also submit an increase TPS support request.
 
 #### Have the required information ready
 
@@ -143,21 +154,21 @@ If you would like to increase your transactions per second, you can enable auto
 
 Initiate the increase of transactions per second(TPS) limit for your resource by submitting the Support Request:
 
-- Ensure you have the [required information](#have-the-required-information-ready)
-- Go to [Azure portal](https://portal.azure.com/)
-- Select the Form Recognizer Resource for which you would like to increase the TPS limit
-- Select *New support request* (*Support + troubleshooting* group)
-- A new window will appear with auto-populated information about your Azure Subscription and Azure Resource
-- Enter *Summary* (like "Increase Form Recognizer TPS limit")
-- In Problem type,* select "Quota or usage validation"
-- Select *Next: Solutions*
-- Proceed further with the request creation
-- Under the *Details* tab enters the following in the *Description* field:
-  - a note, that the request is about **Form Recognizer** quota.
-  - Provide a TPS expectation you would like to scale to  meet.
-  - Azure resource information you [collected](#have-the-required-information-ready).
-  - Complete entering the required information and select *Create* button in *Review + create* tab
-  - Note the support request number in Azure portal notifications. You'll be contacted shortly for further processing
+* Ensure you have the [required information](#have-the-required-information-ready)
+* Go to [Azure portal](https://portal.azure.com/)
+* Select the Form Recognizer Resource for which you would like to increase the TPS limit
+* Select *New support request* (*Support + troubleshooting* group)
+* A new window will appear with auto-populated information about your Azure Subscription and Azure Resource
+* Enter *Summary* (like "Increase Form Recognizer TPS limit")
+* In Problem type,* select "Quota or usage validation"
+* Select *Next: Solutions*
+* Proceed further with the request creation
+* Under the *Details* tab enters the following in the *Description* field:
+  * a note, that the request is about **Form Recognizer** quota.
+  * Provide a TPS expectation you would like to scale to  meet.
+  * Azure resource information you [collected](#have-the-required-information-ready).
+  * Complete entering the required information and select *Create* button in *Review + create* tab
+  * Note the support request number in Azure portal notifications. You'll be contacted shortly for further processing
 
 ## Example of a workload pattern best practice