Update configure-synapse-link.md

Author: Rodrigossz

articles/cosmos-db/configure-synapse-link.md

@@ -56,7 +56,7 @@ You can also checkout the learn module on how to [configure Azure Synapse Link f
 > [!NOTE]
 > Turning on Synapse Link does not turn on the analytical store automatically. Once you enable Synapse Link on the Cosmos DB account, enable analytical store on containers to start using Synapse Link. 
 
-### Command Line Tools
+### Command-Line Tools
 
 Enable Synapse Link in your Cosmos DB SQL API or MongoDB API account using Azure CLI or PowerShell.
 
@@ -170,7 +170,7 @@ try:
 except exceptions.CosmosResourceExistsError:
     print('A container with already exists')
 ```
-### Command Line Tools
+### Command-Line Tools
 
 Set the `analytical TTL` property to the required value to create an analytical store enabled container. For the list of allowed values, see the [analytical TTL supported values](analytical-store-introduction.md#analytical-ttl) article.
 
@@ -191,7 +191,7 @@ The following options create a container with analytical store by using PowerShe
 
 ## <a id="update-analytical-ttl"></a> Enable analytical store on an existing container
 
-Due to short-term capacity constraints, you need to register to enable Synapse Link on your existing containers. Depending on the pending requests, approving this request may take anywhere from a day to a week. Instructions to check the reuqest status are provided below. If you have any issues or questions, please reach out to [[email protected]](mailto:[email protected]). This step is required once per subscription, and all new database accounts will also have this capability enabled.
+Due to short-term capacity constraints, you need to register to enable Synapse Link on your existing containers. Depending on the pending requests, approving this request may take anywhere from a day to a week. Instructions to check the request status are provided below. If you have any issues or questions, please reach out to [[email protected]](mailto:[email protected]). This step is required once per subscription, and all new database accounts will also have this capability enabled.
 
 You can turn on analytical store on existing Azure Cosmos DB SQL API containers. This capability is general available and can be used for production workloads. Please note the following details about the initial sync process:
 
@@ -201,7 +201,7 @@ You can turn on analytical store on existing Azure Cosmos DB SQL API containers.
 
 * The throughput of your container, or database account, also influences the total initial sync time. Although RU/s are not used in this migration, the total RU/s available influences the performance of the process. You can temporarily increase your environment's throughput to speed up the process.
 
-* You won't be able to query analytical store of an existing container until the end of the initial sync process. Your OLTP workload isn't impacted and you can keep on reading data normally. Data ingested after the start of the initial sync will me merged into analytical store by the regular auto-sync process after completition of the initial process.
+* You won't be able to query analytical store of an existing container until the end of the initial sync process. Your OLTP workload isn't impacted and you can keep on reading data normally. Data ingested after the start of the initial sync will be merged into analytical store by the regular auto-sync process after completition of the initial process.
 
 * Currently existing MongoDB API collections are not supported. The alternative is to migrate the data into a new collection, created with analytical store turned on.
 
@@ -217,7 +217,7 @@ You can turn on analytical store on existing Azure Cosmos DB SQL API containers.
 5. Optionally, you can go to the  **Power BI** tab, in the **Integrations** section, to create Power BI dashboards on your Synapse Link enabled containers.
 
 
-### Command Line Tools
+### Command-Line Tools
 
 Set the `analytical TTL` property to the required value to create an analytical store enabled container. For the list of allowed values, see the [analytical TTL supported values](analytical-store-introduction.md#analytical-ttl) article.