Updated how-to-run-a-reindex.md

Author: v-pbartley

articles/healthcare-apis/fhir/how-to-run-a-reindex.md

@@ -13,7 +13,7 @@ ms.author: mikaelw
 There are scenarios where you may have search parameters in the FHIR service in Azure Health Data Services that haven't yet been indexed. This is the case when you define your own custom search parameters. Until the search parameter is indexed, it can't be used in live production. This article covers how to run a reindex job to index any custom search parameters that haven't yet been indexed in your FHIR service database.
 
 > [!Warning]
-> It's important that you read this entire article before getting started. A reindex job can be very performance intensive. This article discusses options for how to throttle and control the reindex job.
+> It's important that you read this entire article before getting started. A reindex job can be very performance intensive. This article discusses options for how to throttle and control a reindex job.
 
 ## How to run a reindex job 
 
@@ -31,7 +31,7 @@ POST {{FHIR_URL}}/$reindex
 }
  ```
 
-Leave the `"parameter": []` field blank (as shown) if you don't need to tweak the compute resources allocated to the reindex job. If the request is successful, you will receive a **201 Created** status code. The FHIR service will also return a `Parameters` resource in response:
+Leave the `"parameter": []` field blank (as shown) if you don't need to tweak the compute resources allocated to the reindex job. If the request is successful, you will receive a **201 Created** status code in addition to a `Parameters` resource in response:
 
 ```json
 HTTP/1.1 201 Created 
@@ -93,7 +93,7 @@ Once you’ve started a reindex job, you can check the status of the job using t
 
 `GET {{FHIR_URL}}/_operations/reindex/{{reindexJobId}}`
 
-The status of the reindex job result is shown below:
+An example response is shown below:
 
 ```json
 {
@@ -150,17 +150,17 @@ The status of the reindex job result is shown below:
 
       "name": "resources",
       "valueString": 
-      "{LIST OF IMPACTED RESOURCES}"
+      "{{LIST_OF_IMPACTED_RESOURCES}}"
     }
   ]
 }
 ```
 
-The following information is shown in the reindex job result:
+The following information is shown in the above response:
 
 * `totalResourcesToReindex`: Includes the total number of resources that are being reindexed in this job.
 
-* `resourcesSuccessfullyReindexed`: The total that have already been successfully reindexed.
+* `resourcesSuccessfullyReindexed`: The total number of resources that have already been reindexed in this job.
 
 * `progress`: Reindex job percent complete. Equals `resourcesSuccessfullyReindexed`/`totalResourcesToReindex` x 100.
 
@@ -185,11 +185,11 @@ Below is a table outlining the available parameters, defaults, and recommended r
 
 | **Parameter**                     | **Description**              | **Default**        | **Available Range**            |
 | --------------------------------- | ---------------------------- | ------------------ | ------------------------------- |
-| `QueryDelayIntervalInMilliseconds`  | The delay between each batch of resources being kicked off during the reindex job. A smaller number will speed up the job while a bigger number will slow it down. | 500 MS (.5 seconds) | 50 to 500000 |
+| `QueryDelayIntervalInMilliseconds`  | The delay between each batch of resources being kicked off during the reindex job. A smaller number will speed up the job while a larger number will slow it down. | 500 MS (.5 seconds) | 50 to 500000 |
 | `MaximumResourcesPerQuery`  | The maximum number of resources included in the batch of resources to be reindexed.  | 100 | 1-5000 |
 | `MaximumConcurrency`  | The number of batches done at a time.  | 1 | 1-10 |
 
-If you want to use any of the parameters above, you can pass them into the `Parameters` resource when you send a `POST` request to start a reindex job.
+If you want to use any of the parameters above, you can pass them into the `Parameters` resource when you send the initial `POST` request to start a reindex job.
 
 ```json