Update analysis-services-async-refresh.md

Author: minghan

articles/analysis-services/analysis-services-async-refresh.md

@@ -14,7 +14,7 @@ ms.custom: references_regions
 
 By using any programming language that supports REST calls, you can perform asynchronous data-refresh operations on your Azure Analysis Services tabular models, including synchronization of read-only replicas for query scale-out.
 
-Data-refresh operations can take some time depending on many factors including data volume, level of optimization using partitions, etc. These operations have traditionally been invoked with existing methods such as using [TOM](/analysis-services/tom/introduction-to-the-tabular-object-model-tom-in-analysis-services-amo) (Tabular Object Model), [PowerShell](/analysis-services/powershell/analysis-services-powershell-reference) cmdlets, or [TMSL](/analysis-services/tmsl/tabular-model-scripting-language-tmsl-reference) (Tabular Model Scripting Language). However, these methods can require often unreliable, long-running HTTP connections.
+Data-refresh operations can take some time depending on many factors including data volume, level of optimization using partitions, etc. Traditionally, these operations been invoked with existing methods such as using [TOM](/analysis-services/tom/introduction-to-the-tabular-object-model-tom-in-analysis-services-amo) (Tabular Object Model), [PowerShell](/analysis-services/powershell/analysis-services-powershell-reference) cmdlets, or [TMSL](/analysis-services/tmsl/tabular-model-scripting-language-tmsl-reference) (Tabular Model Scripting Language). However, these methods can require often unreliable, long-running HTTP connections.
 
 The REST API for Azure Analysis Services enables data-refresh operations to be carried out asynchronously. By using the REST API, long-running HTTP connections from client applications aren't necessary. There are also other built-in features for reliability, such as auto retries and batched commits.
 
@@ -96,7 +96,7 @@ The default value is applied if the parameter isn't specified.
 | Name             | Type  | Description  |Default  |
 |------------------|-------|--------------|---------|
 | `Type`           | Enum  | The type of processing to perform. The types are aligned with the TMSL [refresh command](/analysis-services/tmsl/refresh-command-tmsl) types: `full`, `clearValues`, `calculate`, `dataOnly`, `automatic`, and `defragment`. `add` type isn't supported.      |   `automatic`      |
-| `CommitMode`     | Enum  | Determines if objects will be committed in batches or only when complete. Modes include: `default`, `transactional`, `partialBatch`.  |  `transactional`       |
+| `CommitMode`     | Enum  | Determines if objects are committed in batches or committed only when the entire operation completes. Modes include: `transactional`, `partialBatch`.  |  `transactional`       |
 | `MaxParallelism` | Int   | This value determines the maximum number of threads on which to run processing commands in parallel. This value aligned with the MaxParallelism property that can be set in the TMSL [Sequence command](/analysis-services/tmsl/sequence-command-tmsl) or using other methods.       | 10        |
 | `RetryCount`     | Int   | Indicates the number of times the operation retries before failing.      |     0    |
 | `Objects`        | Array | An array of objects to be processed. Each object includes: "table" when processing the entire table or "table" and "partition" when processing a partition. If no objects are specified, the whole model is refreshed. |   Process the entire model      |