correct Acrolinx flags

Author: Kat-Campise

articles/synapse-analytics/quickstart-connect-synapse-link-cosmos-db.md

@@ -1,6 +1,6 @@
 ---
 title: Connect to Synapse Link for Azure Cosmos DB
-description: How to connect a Azure Cosmos DB to a Synapse workspace with Synapse Link
+description: How to connect an Azure Cosmos DB to a Synapse workspace with Synapse Link
 services: synapse-analytics 
 author: ArnoMicrosoft
 ms.service: synapse-analytics 
@@ -24,11 +24,11 @@ Before you connect an Azure Cosmos DB account to your workspace, there are a few
 
 ## Enable Azure Cosmos DB analytical store
 
-To run large-scale analytics into Azure Cosmos DB without impacting your operational performance, we recommend enabling  Synapse Link for Azure Cosmos DB which bring HTAP capability to a container and built-in support in Azure Synapse. Follow this quickstart to enable Synapse Link for Cosmos DB containers.
+To run large-scale analytics into Azure Cosmos DB without impacting your operational performance, we recommend enabling Synapse Link for Azure Cosmos DB. This function brings HTAP capability to a container and built-in support in Azure Synapse. Follow this quickstart to enable Synapse Link for Cosmos DB containers.
 
 ## Navigate to Synapse Studio 
 
-From your Synapse workspace, select **Launch Synapse Studio**. On the Synapse Studio home page, select **Data** which will take you to the **Data Object Explorer**.
+From your Synapse workspace, select **Launch Synapse Studio**. On the Synapse Studio home page, select **Data, which will take you to the **Data Object Explorer**.
 
 ## Connect an Azure Cosmos DB database to a Synapse workspace 
 
@@ -41,10 +41,10 @@ From the Data Object Explorer, you can directly connect an Azure Cosmos DB datab
 4. Select ***Continue***
 5. Name the linked service. The name will be displayed in the Object Explorer and used by Synapse run-times to connect to the database and containers. We recommend using a friendly name.
 6. Select the **Cosmos DB account name** and **database name**
-7. (Optional) If no region is specified, Synapse run-time operations will be routed toward the nearest region where the analytical store is enabled. However, you can set manually which region you want your users to access Cosmos DB analytical store. Select **Additional connection properties** and then **New**. Under **Property Name**, write ***PreferredRegions*** and set the **Value** to the region you want (example: WestUS2, there is no space between words and number)
+7. (Optional) If no region is specified, Synapse run-time operations will be routed toward the nearest region where the analytical store is enabled. However, you can set manually which region you want your users to access Cosmos DB analytical store. Select **Additional connection properties** and then **New**. Under **Property Name**, write ***PreferredRegions*** and set the **Value** to the region you want (example: WestUS2, there is no space between words and numbers)
 8. Select ***Create***
 
-Azure Cosmos DB database are visible under the tab **Linked** in the Azure Cosmos DB section. You can differentiate an HTAP enabled Azure Cosmos DB container from an OLTP only container with the following icons:
+Azure Cosmos DB databases are visible under the tab **Linked** in the Azure Cosmos DB section. You can differentiate an HTAP enabled Azure Cosmos DB container from an OLTP only container with the following icons:
 
 **Synapse container**:
 
@@ -56,7 +56,7 @@ Azure Cosmos DB database are visible under the tab **Linked** in the Azure Cosmo
 
 ## Quickly interact with code-generated actions
 
-By right-clicking into a container, you have list of gestures that will trigger a Spark or SQL run-time. Writing into a container will happen through the Transactional Store of Azure Cosmos DB and will consume Request Units.  
+When you right-click into a container, you'll have a list of gestures that will trigger a Spark or SQL run-time. Writing into a container will happen through the Transactional Store of Azure Cosmos DB and will consume Request Units.  
 
 ## Next steps
 

articles/synapse-analytics/synapse-link/how-to-connect-synapse-link-cosmos-db.md

@@ -28,7 +28,7 @@ To run large-scale analytics into Azure Cosmos DB without impacting your operati
 
 ## Navigate to Synapse Studio 
 
-From your Synapse workspace, select **Launch Synapse Studio**. On the Synapse Studio home page, select **Data** which will take you to the **Data Object Explorer**. 
+From your Synapse workspace, select **Launch Synapse Studio**. On the Synapse Studio home page, select **Data, which will take you to the **Data Object Explorer**. 
 
 ## Connect an Azure Cosmos DB database to a Synapse workspace 
 
@@ -44,7 +44,7 @@ From the Data Object Explorer, you can directly connect to an Azure Cosmos DB da
 7. (Optional) If no region is specified, Synapse run-time operations will be routed toward the nearest region where the analytical store is enabled. However, you can set manually which region you want your users to access Cosmos DB analytical store. Select **Additional connection properties** and then **New**. Under **Property Name**, write ***PreferredRegions*** and set the **Value** to the region you want (example: WestUS2, there is no space between words and number)
 8. Select ***Create***
 
-Azure Cosmos DB database are visible under the tab **Linked** in the Azure Cosmos DB section. With Azure Cosmos DB, you can differentiate an HTAP enabled container from an OLTP only container through the following icons:
+Azure Cosmos DB databases are visible under the tab **Linked** in the Azure Cosmos DB section. With Azure Cosmos DB, you can differentiate an HTAP enabled container from an OLTP only container through the following icons:
 
 **OLTP only container**:
 

articles/synapse-analytics/synapse-link/how-to-query-analytical-store-spark.md

@@ -13,13 +13,13 @@ ms.reviewer: jrasnick
 
 # Query Azure Cosmos DB analytical store with Synapse Spark
 
-This article gives some examples on how you can interact with the analytical store from Synapse gestures. Gestures are visible when you right-click on a container. With gestures, you can quickly generate code and tailor it to your needs. They are also perfect for discovering data with a single click.
+This article gives some examples on how you can interact with the analytical store from Synapse gestures. Gestures are visible when you right-click on a container. With gestures, you can quickly generate code and tailor it to your needs. Gestures are also perfect for discovering data with a single click.
 
 ## Load to DataFrame
 
-In this step, you will read data from Azure Cosmos DB analytical store in a Spark DataFrame. It will display 10 rows from the DataFrame called ***df***. Once your data is into dataframe, you can perform additional analysis. 
+In this step, you'll read data from Azure Cosmos DB analytical store in a Spark DataFrame. It will display 10 rows from the DataFrame called ***df***. Once your data is into dataframe, you can perform additional analysis. 
 
-This operation does not impact the transactional store.
+This operation doesn't impact the transactional store.
 
 ```python
 # To select a preferred list of regions in a multi-region Cosmos DB account, add .option("spark.cosmos.preferredRegions", "<Region1>,<Region2>")
@@ -44,7 +44,7 @@ val df_olap = spark.read.format("cosmos.olap").
 
 ## Create Spark table
 
-In this gesture, you will create a Spark table pointing to the container you selected. That operation does not incur any data movement. If you decide to delete that table, the underlying container (and corresponding analytical store) won't be impacted. 
+In this gesture, you'll create a Spark table pointing to the container you selected. That operation doesn't incur any data movement. If you decide to delete that table, the underlying container (and corresponding analytical store) won't be impacted. 
 
 This scenario is convenient to reuse tables through third-party tools and provide accessibility to the data for the run-time.
 
@@ -59,7 +59,7 @@ create table call_center using cosmos.olap options (
 ```
 
 ## Write DataFrame to container
-In this gesture, you will write a dataframe into a container. This operation will impact the transactional performance and consume Request Units. Using Azure Cosmos DB transactional performance is ideal for write transactions. 
+In this gesture, you'll write a dataframe into a container. This operation will impact the transactional performance and consume Request Units. Using Azure Cosmos DB transactional performance is ideal for write transactions. 
 
 Make sure that you replace **YOURDATAFRAME** by the dataframe that you want to write back.
 
@@ -91,9 +91,9 @@ df.write.format("cosmos.oltp").
 ```
 
 ## Load streaming DataFrame from container
-In this gesture, you will use Spark Streaming capability to load data from a container into a dataframe. The data will be stored into the primary data lake account (and file system) that you connected to the workspace. 
+In this gesture, you'll use Spark Streaming capability to load data from a container into a dataframe. The data will be stored into the primary data lake account (and file system) that you connected to the workspace. 
 
-If the folder */localReadCheckpointFolder* is not created, it will be automatically created. This operation will impact the transactional performance of Cosmos DB.
+If the folder */localReadCheckpointFolder* isn't created, it will be automatically created. This operation will impact the transactional performance of Cosmos DB.
 
 ```python
 # To select a preferred list of regions in a multi-region Cosmos DB account, add .option("spark.cosmos.preferredRegions", "<Region1>,<Region2>")
@@ -125,7 +125,7 @@ val dfStream = spark.readStream.
 ```
 
 ## Write streaming DataFrame to container
-In this gesture, you will write a streaming dataframe into the Cosmos DB container you selected. If the folder */localReadCheckpointFolder* is not created, it will be automatically created. This operation will impact the transactional performance of Cosmos DB.
+In this gesture, you'll write a streaming dataframe into the Cosmos DB container you selected. If the folder */localReadCheckpointFolder* isn't created, it will be automatically created. This operation will impact the transactional performance of Cosmos DB.
 
 ```python
 # To select a preferred list of regions in a multi-region Cosmos DB account, add .option("spark.cosmos.preferredRegions", "<Region1>,<Region2>")