update disconnected

Author: laujan

articles/applied-ai-services/form-recognizer/containers/form-recognizer-disconnected-containers.md

@@ -27,7 +27,7 @@ Azure Cognitive Services Form Recognizer containers allow you to use Form Recogn
 Before attempting to run a Docker container in an offline environment, make sure you're familiar with the following requirements to successfully download and use the container:
 
 * Host computer requirements and recommendations.
-* The Docker `pull` command you'll use to download the container.
+* The Docker `pull` command to download the container.
 * How to validate that a container is running.
 * How to send queries to the container's endpoint, once it's running.
 
@@ -93,19 +93,19 @@ docker pull mcr.microsoft.com/azure-cognitive-services/form-recognizer/invoice:l
 
 ## Configure the container to be run in a disconnected environment
 
-Now that you've downloaded your container, you'll need to execute the `docker run` command with the following parameter:
+Now that you've downloaded your container, you need to execute the `docker run` command with the following parameter:
 
-* **`DownloadLicense=True`**. This parameter will download a license file that will enable your Docker container to run when it isn't connected to the internet. It also contains an expiration date, after which the license file will be invalid to run the container. You can only use the license file in corresponding approved container.
+* **`DownloadLicense=True`**. This parameter downloads a license file that enables your Docker container to run when it isn't connected to the internet. It also contains an expiration date, after which the license file is invalid to run the container. You can only use the license file in corresponding approved container.
 
 > [!IMPORTANT]
 >The `docker run` command will generate a template that you can use to run the container. The template contains parameters you'll need for the downloaded models and configuration file. Make sure you save this template.
 
-The following example shows the formatting for the `docker run` command you'll use, with placeholder values. Replace these placeholder values with your own values.
+The following example shows the formatting for the `docker run` command to use with placeholder values. Replace these placeholder values with your own values.
 
 | Placeholder | Value | Format or example |
 |-------------|-------|---|
 | `{IMAGE}` | The container image you want to use. | `mcr.microsoft.com/azure-cognitive-services/form-recognizer/invoice` |
-| `{LICENSE_MOUNT}` | The path where the license will be downloaded, and mounted.  | `/host/license:/path/to/license/directory` |
+| `{LICENSE_MOUNT}` | The path where the license is downloaded, and mounted.  | `/host/license:/path/to/license/directory` |
 | `{ENDPOINT_URI}` | The endpoint for authenticating your service request. You can find it on your resource's **Key and endpoint** page, on the Azure portal. | `https://<your-custom-subdomain>.cognitiveservices.azure.com` |
 | `{API_KEY}` | The key for your Text Analytics resource. You can find it on your resource's **Key and endpoint** page, on the Azure portal. |`{string}`|
 | `{CONTAINER_LICENSE_DIRECTORY}` | Location of the license folder on the container's local filesystem.  | `/path/to/license/directory` |
@@ -156,7 +156,7 @@ Placeholder | Value | Format or example |
 | `{IMAGE}` | The container image you want to use. | `mcr.microsoft.com/azure-cognitive-services/form-recognizer/invoice` |
  `{MEMORY_SIZE}` | The appropriate size of memory to allocate for your container. | `4g` |
 | `{NUMBER_CPUS}` | The appropriate number of CPUs to allocate for your container. | `4` |
-| `{LICENSE_MOUNT}` | The path where the license will be located and mounted.  | `/host/license:/path/to/license/directory` |
+| `{LICENSE_MOUNT}` | The path where the license is located and mounted.  | `/host/license:/path/to/license/directory` |
 | `{OUTPUT_PATH}` | The output path for logging [usage records](#usage-records). | `/host/output:/path/to/output/directory` |
 | `{CONTAINER_LICENSE_DIRECTORY}` | Location of the license folder on the container's local filesystem.  | `/path/to/license/directory` |
 | `{CONTAINER_OUTPUT_DIRECTORY}` | Location of the output folder on the container's local filesystem.  | `/path/to/output/directory` |
@@ -189,7 +189,7 @@ When operating Docker containers in a disconnected environment, the container wi
 
 #### Arguments for storing logs
 
-When run in a disconnected environment, an output mount must be available to the container to store usage logs. For example, you would include `-v /host/output:{OUTPUT_PATH}` and `Mounts:Output={OUTPUT_PATH}` in the following example, replacing `{OUTPUT_PATH}` with the path where the logs will be stored:
+When run in a disconnected environment, an output mount must be available to the container to store usage logs. For example, you would include `-v /host/output:{OUTPUT_PATH}` and `Mounts:Output={OUTPUT_PATH}` in the following example, replacing `{OUTPUT_PATH}` with the path where the logs are stored:
 
 ```Docker
 docker run -v /host/output:{OUTPUT_PATH} ... <image> ... Mounts:Output={OUTPUT_PATH}
@@ -201,7 +201,7 @@ The container provides two endpoints for returning records about its usage.
 
 #### Get all records
 
-The following endpoint will provide a report summarizing all of the usage collected in the mounted billing record directory.
+The following endpoint provides a report summarizing all of the usage collected in the mounted billing record directory.
 
 ```http
 https://<service>/records/usage-logs/
@@ -211,7 +211,7 @@ https://<service>/records/usage-logs/
 
   `http://localhost:5000/records/usage-logs`
 
-The usage-log endpoint will return a JSON response similar to the following example:
+The usage-log endpoint returns a JSON response similar to the following example:
 
 ```json
 {
@@ -228,13 +228,13 @@ The usage-log endpoint will return a JSON response similar to the following exam
 
 #### Get records for a specific month
 
-The following endpoint will provide a report summarizing usage over a specific month and year.
+The following endpoint provides a report summarizing usage over a specific month and year.
 
 ```HTTP
 https://<service>/records/usage-logs/{MONTH}/{YEAR}
 ```
 
-This usage-logs endpoint will return a JSON response similar to the following example:
+This usage-logs endpoint returns a JSON response similar to the following example:
 
 ```json
 {
@@ -251,17 +251,17 @@ This usage-logs endpoint will return a JSON response similar to the following ex
 
 ### Purchase a different commitment plan for disconnected containers
 
-Commitment plans for disconnected containers have a calendar year commitment period. When you purchase a plan, you'll be charged the full price immediately. During the commitment period, you can't change your commitment plan, however you can purchase more unit(s) at a pro-rated price for the remaining days in the year. You have until midnight (UTC) on the last day of your commitment, to end a commitment plan.
+Commitment plans for disconnected containers have a calendar year commitment period. When you purchase a plan, you're charged the full price immediately. During the commitment period, you can't change your commitment plan, however you can purchase more unit(s) at a pro-rated price for the remaining days in the year. You have until midnight (UTC) on the last day of your commitment, to end a commitment plan.
 
 You can choose a different commitment plan in the **Commitment tier pricing** settings of your resource under the **Resource Management** section.
 
 ### End a commitment plan
 
-If you decide that you don't want to continue purchasing a commitment plan, you can set your resource's auto-renewal to **Do not auto-renew**. Your commitment plan will expire on the displayed commitment end date. After this date, you won't be charged for the commitment plan. You'll be able to continue using the Azure resource to make API calls, charged at pay-as-you-go pricing. You have until midnight (UTC) on the last day of the year to end a commitment plan for disconnected containers. If you cancel at or before that time, you won't be charged for the following year.
+If you decide that you don't want to continue purchasing a commitment plan, you can set your resource's auto-renewal to **Do not auto-renew**. Your commitment plan expires on the displayed commitment end date. After this date, you won't be charged for the commitment plan. You can continue using the Azure resource to make API calls, charged at pay-as-you-go pricing. You have until midnight (UTC) on the last day of the year to end a commitment plan for disconnected containers. If you cancel at or before that time, there are no charges for the next year.
 
 ## Troubleshooting
 
-Run the container with an output mount and logging enabled. These settings will enable the container generates log files that are helpful for troubleshooting issues that occur while starting or running the container.
+Run the container with an output mount and logging enabled. These settings enable the container generates log files that are helpful for troubleshooting issues that occur while starting or running the container.
 
 > [!TIP]
 > For more troubleshooting information and guidance, see [Disconnected containers Frequently asked questions (FAQ)](../../../cognitive-services/containers/disconnected-container-faq.yml).