update concepts

laujan · laujan · commit 885eb3de7789 · 2021-10-23T19:08:56.000-07:00
diff --git a/articles/applied-ai-services/form-recognizer/concept-business-card.md b/articles/applied-ai-services/form-recognizer/concept-business-card.md
@@ -108,7 +108,7 @@ You will need a business card document. You can use our [sample business card do
 
  The Form Recognizer preview introduces several new features and capabilities.
 
-* Following our [**Form Recognizer v3.0 migration guide**](v3-migration-guide.md) to learn how to use the preview version in your applications and workflows.
+* Follow our [**Form Recognizer v3.0 migration guide**](v3-migration-guide.md) to learn how to use the preview version in your applications and workflows.
 
 * Explore our [**REST API (preview)**](https://westus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-v3-0-preview-1/operations/AnalyzeDocument) to learn more about the preview version and new capabilities.
 
diff --git a/articles/applied-ai-services/form-recognizer/concept-custom.md b/articles/applied-ai-services/form-recognizer/concept-custom.md
@@ -76,7 +76,7 @@ In the Form Recognizer UI:
 
     :::image type="content" source="media/label-tool/fott-new-project.png" alt-text="Screenshot: FOTTtools select new project.":::
 
-    For more detailed instructions, *see* our [Sample Labeling tool] quickstart.
+    For more detailed instructions, *see* our [Sample Labeling tool](quickstarts/try-sample-label-tool.md) quickstart.
 
     > [!div class="nextstepaction"]
     > [Try Sample Labeling tool](https://fott-2-1.azurewebsites.net/projects/create)
@@ -116,7 +116,7 @@ In the Form Recognizer UI:
 
 * **Custom model API (v3.0)** supports signature detection for custom forms. When training custom models, you can specify certain fields as signatures.  When a document is analyzed with your custom model, it will indicate whether a signature has been detected or not.
 
-* Following our [**Form Recognizer v3.0 migration guide**](v3-migration-guide.md) to learn how to use the preview version in your applications and workflows.
+* Follow our [**Form Recognizer v3.0 migration guide**](v3-migration-guide.md) to learn how to use the preview version in your applications and workflows.
 
 * Explore our [**REST API (preview)**](https://westus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-v3-0-preview-1/operations/AnalyzeDocument) to learn more about the preview version and new capabilities.
 
diff --git a/articles/applied-ai-services/form-recognizer/concept-form-recognizer-studio.md b/articles/applied-ai-services/form-recognizer/concept-form-recognizer-studio.md
@@ -11,7 +11,7 @@ ms.date: 10/11/2021
 ms.author: sajagtap
 ---
 
-# Form Recognizer Studio | Preview
+# Form Recognizer Studio (preview)
 
 >[!NOTE]
 > Form Recognizer Studio is currently in public preview. Some features may not be supported or have limited capabilities.
diff --git a/articles/applied-ai-services/form-recognizer/concept-general-document.md b/articles/applied-ai-services/form-recognizer/concept-general-document.md
@@ -13,7 +13,7 @@ recommendations: false
 ---
 <!-- markdownlint-disable MD033 -->
 
-# Form Recognizer general document model | Preview
+  # Form Recognizer general document model (preview))
 
 The General document preview model combines powerful Optical Character Recognition (OCR) capabilities with deep learning models to extract key-value pairs and entities from documents. General document is only available with the preview (v3.0) API.  For more information on using the preview (v3.0) API, see our [migration guide](v3-migration-guide.md).
 
@@ -129,7 +129,7 @@ Email | String | Email address. |
 
 ## Next steps
 
-* Following our [**Form Recognizer v3.0 migration guide**](v3-migration-guide.md) to learn how to use the preview version in your applications and workflows.
+* Follow our [**Form Recognizer v3.0 migration guide**](v3-migration-guide.md) to learn how to use the preview version in your applications and workflows.
 
 * Explore our [**REST API (preview)**](https://westus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-v3-0-preview-1/operations/AnalyzeDocument) to learn more about the preview version and new capabilities.
 
diff --git a/articles/applied-ai-services/form-recognizer/concept-id-document.md b/articles/applied-ai-services/form-recognizer/concept-id-document.md
@@ -126,7 +126,9 @@ You will need an ID document. You can use our [sample ID document](https://raw.g
     |  Address | String | Extracted address (Driver's License only) ||
     |  Region | String | Extracted region, state, province, etc. (Driver's License only) |  |
 
-* Following our [**Form Recognizer v3.0 migration guide**](v3-migration-guide.md) to learn how to use the preview version in your applications and workflows.
+### Migration guide and REST API v3.0
+
+* Follow our [**Form Recognizer v3.0 migration guide**](v3-migration-guide.md) to learn how to use the preview version in your applications and workflows.
 
 * Explore our [**REST API (preview)**](https://westus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-v3-0-preview-1/operations/AnalyzeDocument) to learn more about the preview version and new capabilities.
 
diff --git a/articles/applied-ai-services/form-recognizer/concept-invoice.md b/articles/applied-ai-services/form-recognizer/concept-invoice.md
@@ -133,7 +133,7 @@ The invoice key-value pairs and line items extracted are in the `documentResults
 
  The Form Recognizer preview introduces several new features and capabilities.
 
-* Following our [**Form Recognizer v3.0 migration guide**](v3-migration-guide.md) to learn how to use the preview version in your applications and workflows.
+* Follow our [**Form Recognizer v3.0 migration guide**](v3-migration-guide.md) to learn how to use the preview version in your applications and workflows.
 
 * Explore our [**REST API (preview)**](https://westus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-v3-0-preview-1/operations/AnalyzeDocument) to learn more about the preview version and new capabilities.
 
diff --git a/articles/applied-ai-services/form-recognizer/concept-layout.md b/articles/applied-ai-services/form-recognizer/concept-layout.md
@@ -134,7 +134,7 @@ For large multi-page documents, use the `pages` query parameter to indicate spec
 
  The Form Recognizer preview introduces several new features and capabilities.
 
-* Following our [**Form Recognizer v3.0 migration guide**](v3-migration-guide.md) to learn how to use the preview version in your applications and workflows.
+* Follow our [**Form Recognizer v3.0 migration guide**](v3-migration-guide.md) to learn how to use the preview version in your applications and workflows.
 
 * Explore our [**REST API (preview)**](https://westus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-v3-0-preview-1/operations/AnalyzeDocument) to learn more about the preview version and new capabilities.
 
diff --git a/articles/applied-ai-services/form-recognizer/concept-receipt.md b/articles/applied-ai-services/form-recognizer/concept-receipt.md
@@ -55,10 +55,10 @@ You will need a receipt document. You can use our [sample receipt document](http
 
 1. Select **Receipt** from the **Form Type** dropdown menu:
 
-  :::image type="content" source="media/try-receipt.png" alt-text="Screenshot: Sample Labeling tool dropdown prebuilt model selection menu.":::
+      :::image type="content" source="media/try-receipt.png" alt-text="Screenshot: Sample Labeling tool dropdown prebuilt model selection menu.":::
 
-  > [!div class="nextstepaction"]
-  > [Try Sample Labeling tool](https://fott-2-1.azurewebsites.net/prebuilts-analyze)
+      > [!div class="nextstepaction"]
+      > [Try Sample Labeling tool](https://fott-2-1.azurewebsites.net/prebuilts-analyze)
 
 ## Input requirements
 
@@ -105,38 +105,38 @@ You will need a receipt document. You can use our [sample receipt document](http
 
 ## Form Recognizer preview v3.0
 
- The Form Recognizer preview introduces several new features and capabilities:
-
-* **Receipt** model supports single-page hotel receipt processing.
-
-    ### Hotel receipt key-value pair extraction
-
-    |Name| Type | Description | Standardized output |
-    |:-----|:----|:----|:----|
-    | ArrivalDate | Date | Date of arrival | yyyy-mm-dd |
-    | Currency | Currency | Currency unit of receipt amounts. For example USD, EUR, or MIXED if multiple values are found ||
-    | DepartureDate | Date | Date of departure | yyyy-mm-dd |
-    | Items | Array | | |
-    | Items.*.Category | String | Item category, for example, Room, Tax, etc. |  |
-    | Items.*.Date | Date | Item date | yyyy-mm-dd |
-    | Items.*.Description | String | Item description | |
-    | Items.*.TotalPrice |  Number | Item total price | Integer |
-    | Locale | String | Locale of the receipt, for example, en-US. | ISO language-county code   |
-    | MerchantAddress | String | Listed address of merchant | |
-    | MerchantAliases | Array| | |
-    | MerchantAliases.* | String | Alternative name of merchant |  |
-    | MerchantName | String | Name of the merchant issuing the receipt | |
-    | MerchantPhoneNumber | phoneNumber | Listed phone number of merchant | +1 xxx xxx xxxx|
-    | ReceiptType | String | Type of receipt, for example, Hotel, Itemized | |
-    | Total | Number | Full transaction total of receipt | Two-decimal float |
-
-    ### Hotel receipt supported languages and locales
-
-    | Model | Language—Locale code | Default |
-    |--------|:----------------------|:---------|
-    |Receipt (hotel) | <ul><li>English (United States)—en-US</li></ul>| English (United States)—en-US|
-
-* Following our [**Form Recognizer v3.0 migration guide**](v3-migration-guide.md) to learn how to use the preview version in your applications and workflows.
+ The Form Recognizer preview introduces several new features and capabilities. The **Receipt** model supports single-page hotel receipt processing.
+
+### Hotel receipt field extraction
+
+|Name| Type | Description | Standardized output |
+|:-----|:----|:----|:----|
+| ArrivalDate | Date | Date of arrival | yyyy-mm-dd |
+| Currency | Currency | Currency unit of receipt amounts. For example USD, EUR, or MIXED if multiple values are found ||
+| DepartureDate | Date | Date of departure | yyyy-mm-dd |
+| Items | Array | | |
+| Items.*.Category | String | Item category, for example, Room, Tax, etc. |  |
+| Items.*.Date | Date | Item date | yyyy-mm-dd |
+| Items.*.Description | String | Item description | |
+| Items.*.TotalPrice |  Number | Item total price | Integer |
+| Locale | String | Locale of the receipt, for example, en-US. | ISO language-county code   |
+| MerchantAddress | String | Listed address of merchant | |
+| MerchantAliases | Array| | |
+| MerchantAliases.* | String | Alternative name of merchant |  |
+| MerchantName | String | Name of the merchant issuing the receipt | |
+| MerchantPhoneNumber | phoneNumber | Listed phone number of merchant | +1 xxx xxx xxxx|
+| ReceiptType | String | Type of receipt, for example, Hotel, Itemized | |
+| Total | Number | Full transaction total of receipt | Two-decimal float |
+
+### Hotel receipt supported languages and locales
+
+| Model | Language—Locale code | Default |
+|--------|:----------------------|:---------|
+|Receipt (hotel) | <ul><li>English (United States)—en-US</li></ul>| English (United States)—en-US|
+
+### Migration guide and REST API v3.0
+
+* Follow our [**Form Recognizer v3.0 migration guide**](v3-migration-guide.md) to learn how to use the preview version in your applications and workflows.
 
 * Explore our [**REST API (preview)**](https://westus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-v3-0-preview-1/operations/AnalyzeDocument) to learn more about the preview version and new capabilities.
 
