Update analytical-store-introduction.md

Author: Rodrigossz

articles/cosmos-db/analytical-store-introduction.md

@@ -331,7 +331,7 @@ Here's a map of all the property data types and their suffix representations in
 
 ##### Working with the MongoDB `_id` field
 
-the MongoDB `_id` field is fundamental to every collection in MongoDB and originally has a hexadecimal representation. As you can see in the table above, `Full Fidelity Schema` will preserve its characteristics, creating a challenge for its vizualiation in Azure Synapse Analytics. For correct visualization, you must convert the `_id` datatype as below:
+the MongoDB `_id` field is fundamental to every collection in MongoDB and originally has a hexadecimal representation. As you can see in the table above, `Full Fidelity Schema` will preserve its characteristics, creating a challenge for its visualization in Azure Synapse Analytics. For correct visualization, you must convert the `_id` datatype as below:
 
 ###### Spark
 
@@ -453,7 +453,7 @@ Synapse Link, and analytical store by consequence, has different compatibility l
 
 ### Backup Polices
 
-There two possible backup polices and to understand how to use them, two details about Cosmos DB backups are very important:
+There are two possible backup polices and to understand how to use them, the following details about Cosmos DB backups are very important:
 
  * The original container is restored without analytical store in both backup modes.
  * Cosmos DB doesn't support containers overwrite from a restore.
@@ -468,7 +468,7 @@ Now let's see how to use backup and restores from the analytical store perspecti
 
  #### Restoring a container with TTTL < ATTL
 
-When `transactional TTL` is smaller than `analytical TTL`, some data only exists in analytical store and won't be in the restored container. Again your have two possible situations:
+When `transactional TTL` is smaller than `analytical TTL`, some data only exists in analytical store and won't be in the restored container. Again, you have two possible situations:
  * To use the restored container as a replacement for the original container. In this case, when you enable Synapse Link at container level, only the data that was in transactional store will be included in the new analytical store. But please note that the analytical store of the original container remains available for queries as long as the original container exists. You may want to change your application to query both.
  * To use the restored container as a data source to backfill or update the data in the original container:
   * Analytical store will automatically reflect the data operations for the data that is in transactional store.