Update known-issues.md

Author: ttorble

articles/synapse-analytics/known-issues.md

@@ -14,15 +14,15 @@ ms.reviewer: wiassaf
 # Azure Synapse Analytics known issues
 
 This page lists the known issues in [Azure Synapse Analytics](overview-what-is.md), as well as their resolution date or possible workaround. 
-Before submitting a Support request, please review this list to see if the issue that you are experiencing is already known and being addressed.
+Before submitting a Support request, please review this list to see if the issue that you're experiencing is already known and being addressed.
 
 To learn more about Azure Synapse Analytics, see the [Overview](index.yml), and [What's new in Azure Synapse Analytics?](whats-new.md). 
 
 ## Active Known issues
 
 |Issue |Status  |Synapse Component|
 |---------|---------|---------|
-|[Queries using Azure AD authentication fails after 1 hour](#queries-using-aad-authentication-fails-after-1-hour)|Has Workaround|Azure Synapse Serverless SQL Pool|
+|[Queries using Azure AD authentication fails after 1 hour](#queries-using-azure-ad-authentication-fails-after-1-hour)|Has Workaround|Azure Synapse Serverless SQL Pool|
 |[Query failures from Serverless SQL to Cosmos DB analytical store](#query-failures-from-serverless-sql-pool-to-azure-cosmos-db-analytical-store)|Has Workaround|Azure Synapse Serverless SQL pool|
 |[Query failures while reading Cosmos Data using OPENROWSET](#query-failures-while-reading-cosmos-data-using-openrowset)|Has Workaround|Azure Synapse Serverless SQL Pool|
 |[Queries failing with Data Exfiltration Error](#queries-failing-with-data-exfiltration-error)|Has Workaround|Azure Synapse Dedicated SQL Pool|
@@ -33,12 +33,12 @@ To learn more about Azure Synapse Analytics, see the [Overview](index.yml), and
 
 ### Queries using Azure AD authentication fails after 1 hour
 
-SQL connections using Azure AD authentication that remain active for more than 1 hour will start to fail. This includes querying storage using Azure AD pass-through authentication and statements that interact with Azure AD, like CREATE EXTERNAL PROVIDER. This affects every tool that keeps connections active, like query editor in SSMS and ADS. Tools that open new connection to execute queries are not affected, like Synapse Studio.
+SQL connections using Azure AD authentication that remain active for more than 1 hour will start to fail. This includes querying storage using Azure AD pass-through authentication and statements that interact with Azure AD, like CREATE EXTERNAL PROVIDER. This affects every tool that keeps connections active, like query editor in SSMS and ADS. Tools that open new connection to execute queries aren't affected, like Synapse Studio.
 
 **Workaround**: The engineering team is currently aware of this behavior and working on a fix. <br>
 Following steps can be followed to work around the problem. 
 
-1) It is recommended switching to Service Principal, Managed Identity or Shared Access Signature instead of using user identity for long running queries. 
+1) It's recommended switching to Service Principal, Managed Identity or Shared Access Signature instead of using user identity for long running queries. 
 2) Restarting client (SSMS/ADS) acquires new token to establish the connection.
 
 ### Query failures from Serverless SQL pool to Azure Cosmos DB analytical store