update language support, receipt, invoice

Author: laujan

articles/applied-ai-services/form-recognizer/concept-invoice.md

@@ -92,7 +92,7 @@ The following tools are supported by Form Recognizer v2.1:
 
 ## Try invoice data extraction
 
-See how data, including customer information, vendor details, and line items, is extracted from invoices. You'll need the following resources:
+See how data, including customer information, vendor details, and line items, is extracted from invoices. You need the following resources:
 
 * An Azure subscription—you can [create one for free](https://azure.microsoft.com/free/cognitive-services/)
 
@@ -146,7 +146,7 @@ See how data, including customer information, vendor details, and line items, is
 
     :::image type="content" source="media/fott-select-form-type.png" alt-text="Screenshot showing the select-form-type dropdown menu.":::
 
-1. Select **Run analysis**. The Form Recognizer Sample Labeling tool will call the Analyze Prebuilt API and analyze the document.
+1. Select **Run analysis**. The Form Recognizer Sample Labeling tool calls the Analyze Prebuilt API and analyze the document.
 
 1. View the results - see the key-value pairs extracted, line items, highlighted text extracted and tables detected.
 
@@ -166,13 +166,13 @@ See how data, including customer information, vendor details, and line items, is
 
 | Supported languages | Details |
 |:----------------------|:---------|
-| • English | United States (us), Australia (-au), Canada (-ca), Great Britain (-gb), India (-in)|
-| • Spanish |Spain (es)|
-| • German | Germany (de)|
-| • French | France (fr) |
-| • Italian | Italy (it)|
-| • Portuguese | Portugal (-pt), Brazil (-br)|
-| • Dutch | Netherlands (de)|
+| • English (en) | United States (us), Australia (-au), Canada (-ca), Great Britain (-gb), India (-in)|
+| • Spanish (es) |Spain (es)|
+| • German (de) | Germany (de)|
+| • French (fr) | France (fr) |
+| • Italian (it) | Italy (it)|
+| • Portuguese (pt) | Portugal (pt), Brazil (br)|
+| • Dutch (de) | Netherlands (de)|
 
 ## Field extraction
 
@@ -196,7 +196,7 @@ See how data, including customer information, vendor details, and line items, is
 | ShippingAddress | String | Explicit shipping address for the customer | |
 | ShippingAddressRecipient | String | Name associated with the ShippingAddress |  |
 | PaymentTerm | String | The terms of payment for the invoice | |
-| SubTotal | Number | Subtotal field identified on this invoice | Integer |
+ |Sub​Total| Number | Subtotal field identified on this invoice | Integer |
 | TotalTax | Number | Total tax field identified on this invoice | Integer |
 | InvoiceTotal | Number (USD) | Total new charges associated with this invoice | Integer |
 | AmountDue |  Number (USD) | Total Amount Due to the vendor | Integer |
@@ -234,7 +234,7 @@ The invoice key-value pairs and line items extracted are in the `documentResults
 
 The prebuilt invoice **2022-06-30** and later releases support returns key-value pairs at no extra cost. Key-value pairs are specific spans within the invoice that identify a label or key and its associated response or value. In an invoice, these pairs could be the label and the value the user entered for that field or telephone number. The AI model is trained to extract identifiable keys and values based on a wide variety of document types, formats, and structures.
 
-Keys can also exist in isolation when the model detects that a key exists, with no associated value or when processing optional fields. For example, a middle name field may be left blank on a form in some instances. key-value pairs are always spans of text contained in the document. For documents where the same value is described in different ways, for example, customer/user, the associated key will be either customer or user (based on context).
+Keys can also exist in isolation when the model detects that a key exists, with no associated value or when processing optional fields. For example, a middle name field may be left blank on a form in some instances. key-value pairs are always spans of text contained in the document. For documents where the same value is described in different ways, for example, customer/user, the associated key is either customer or user (based on context).
 
 ::: moniker-end
 
@@ -246,7 +246,7 @@ Keys can also exist in isolation when the model detects that a key exists, with
 
 ## Fields extracted
 
-The Invoice service will extract the text, tables, and 26 invoice fields. Following are the fields extracted from an invoice in the JSON output response (the following output uses this [sample invoice](media/sample-invoice.jpg)).
+The Invoice service extracts the text, tables, and 26 invoice fields. Following are the fields extracted from an invoice in the JSON output response (the following output uses this [sample invoice](media/sample-invoice.jpg)).
 
 |Name| Type | Description | Text | Value (standardized output) |
 |:-----|:----|:----|:----| :----|
@@ -265,7 +265,7 @@ The Invoice service will extract the text, tables, and 26 invoice fields. Follow
 | BillingAddressRecipient | string | Name associated with the BillingAddress | Microsoft Services | |
 | ShippingAddress | string | Explicit shipping address for the customer | 123 Ship Street, Redmond WA, 98052 | |
 | ShippingAddressRecipient | string | Name associated with the ShippingAddress | Microsoft Delivery | |
-| SubTotal | number | Subtotal field identified on this invoice | $100.00 | 100 |
+| Sub​Total | number | Subtotal field identified on this invoice | $100.00 | 100 |
 | TotalTax | number | Total tax field identified on this invoice | $10.00 | 10 |
 | InvoiceTotal | number | Total new charges associated with this invoice | $110.00 | 110 |
 | AmountDue |  number | Total Amount Due to the vendor | $610.00 | 610 |
@@ -297,7 +297,7 @@ The JSON output has three parts:
 
 * `"readResults"` node contains all of the recognized text and selection marks. Text is organized by page, then by line, then by individual words.
 * `"pageResults"` node contains the tables and cells extracted with their bounding boxes, confidence, and a reference to the lines and words in "readResults".
-* `"documentResults"` node contains the invoice-specific values and line items that the model discovered. It's where you'll find all the fields from the invoice such as invoice ID, ship to, bill to, customer, total, line items and lots more.
+* `"documentResults"` node contains the invoice-specific values and line items that the model discovered. It's where to find all the fields from the invoice such as invoice ID, ship to, bill to, customer, total, line items and lots more.
 
 ## Migration guide
 

articles/applied-ai-services/form-recognizer/concept-receipt.md

@@ -84,7 +84,7 @@ The following tools are supported by Form Recognizer v2.1:
 
 ### Try receipt data extraction
 
-See how data, including time and date of transactions, merchant information, and amount totals, is extracted from receipts. You'll need the following resources:
+See how data, including time and date of transactions, merchant information, and amount totals, is extracted from receipts. You need the following resources:
 
 * An Azure subscription—you can [create one for free](https://azure.microsoft.com/free/cognitive-services/)
 
@@ -141,7 +141,7 @@ See how data, including time and date of transactions, merchant information, and
 
     :::image type="content" source="media/fott-select-form-type.png" alt-text="Screenshot of the select-form-type dropdown menu.":::
 
-1. Select **Run analysis**. The Form Recognizer Sample Labeling tool will call the Analyze Prebuilt API and analyze the document.
+1. Select **Run analysis**. The Form Recognizer Sample Labeling tool calls the Analyze Prebuilt API and analyze the document.
 
 1. View the results - see the key-value pairs extracted, line items, highlighted text extracted and tables detected.
 
@@ -164,13 +164,13 @@ The receipt model supports all English receipts and the following locales:
 |Supported Languages| Details |
 |:-----|:----:|
 |• English| United States (-us), Australia (-au), Great Britain (-gb), India (-in), United Arab Emirates (-ae)|
-|• Dutch| Netherlands (nl)|
-|• French | France (fr), Canada (fr-ca) |
-|• German | Germany (de) |
-|• Italian | Italy (it) |
-|• Japanese | Japan (ja)|
-|• Portuguese| Portugal (-pt), Brazil (-br)|
-|• Spanish | Spain (es) |
+|• Dutch| Netherlands (nl-nl)|
+|• French | France (fr-fr), Canada (fr-ca) |
+|• German | Germany (de-de) |
+|• Italian | Italy (it-it) |
+|• Japanese | Japan (ja-ja)|
+|• Portuguese| Portugal (pt-pt), Brazil (pt-br)|
+|• Spanish | Spain (es-es) |
 ::: moniker-end
 
 ::: moniker range="form-recog-2.1.0"

articles/applied-ai-services/form-recognizer/language-support.md

@@ -228,13 +228,13 @@ Language| Locale code |
 |English (Australia)|`en-au`|
 |English (Canada)|`en-ca`|
 |English (United Kingdom)|`en-gb`|
-|English (India|`en-in`|
+|English (India)|`en-in`|
 |English (United States)| `en-us`|
-|French | `fr` |
+|French (France) | `fr` |
 |French (Canada)| `fr-ca`|
 |German | `de`|
 |Italian| `it`|
-| Spanish | `es` |
+|Spanish | `es` |
 
 ## Business card model
 

articles/applied-ai-services/form-recognizer/whats-new.md

@@ -46,13 +46,13 @@ Form Recognizer service is updated on an ongoing basis. Bookmark this page to st
 
    The **prebuilt receipt model** now has added support for the following languages:
 
-  * English - United Arab Emirates (en-AE)
-  * Dutch - Netherlands (nl-NL)
-  * French - Canada (fr-CA)
+  * English - United Arab Emirates (en-ae)
+  * Dutch - Netherlands (nl-nl)
+  * French - Canada (fr-ca)
   * German - (de-de)
   * Italian - (it-it)
-  * Japanese - Japan (ja-JP)
-  * Portuguese - Brazil (pt-BR)
+  * Japanese - Japan (ja-jp)
+  * Portuguese - Brazil (pt-br)
 
 * **[Prebuilt invoice model](concept-invoice.md)—additional language support and field extractions**