Acrolinx

Author: whhender

articles/synapse-analytics/sql/create-use-external-tables.md

@@ -15,6 +15,7 @@ ms.reviewer: whhender, wiassaf
 In this section, you'll learn how to create and use [native external tables](develop-tables-external-tables.md) in Synapse SQL pools. Native external tables have better performance when compared to external tables with `TYPE=HADOOP` in their external data source definition. This is because native external tables use native code to access external data. 
 
 External tables are useful when you want to control access to external data in Synapse SQL pool. External tables are also useful if you want to use tools, such as Power BI, in conjunction with Synapse SQL pool. External tables can access two types of storage:
+
 - Public storage where users access public storage files.
 - Protected storage where users access storage files using SAS credential, Microsoft Entra identity, or Managed Identity of Synapse workspace.
 
@@ -31,7 +32,7 @@ The following table lists the data formats supported:
 |delta  |  Yes  |  No  |
 |Spark  |  Yes  | No |
 |Dataverse |  Yes | No  |
-|Azure Cosmos DB data formats (JSON, BSON etc.)  |  No (Alternatively, [create views](query-cosmos-db-analytical-store.md?tabs=openrowset-credential#create-view)) | No  |
+|Azure Cosmos DB data formats (JSON, BSON, etc.)  |  No (Alternatively, [create views](query-cosmos-db-analytical-store.md?tabs=openrowset-credential#create-view)) | No  |
 
 ## Prerequisites
 
@@ -83,7 +84,7 @@ You can create external tables that access data on an Azure storage account that
 The following query creates an external table that reads *population.csv* file from SynapseSQL demo Azure storage account that is referenced using `sqlondemanddemo` data source and protected with database scoped credential called `sqlondemand`.
 
 > [!NOTE]
-> Change the first line in the query, i.e., [mydbname], so you're using the database you created.
+> Change the first line in the query, that is, [mydbname], so you're using the database you created.
 
 ```sql
 USE [mydbname];
@@ -129,7 +130,7 @@ CREATE EXTERNAL TABLE Taxi (
 You can specify the pattern that the files must satisfy in order to be referenced by the external table. The pattern is required only for Parquet and CSV tables. If you're using Delta Lake format, you need to specify just a root folder, and the external table will automatically find the pattern.
 
 > [!NOTE]
-> The table is created on partitioned folder structure, but you cannot leverage some partition elimination. If you want to get better performance by skipping the files that do not satisfy some criterion (like specific year or month in this case), use [views on external data](create-use-views.md#partitioned-views).
+> The table is created on partitioned folder structure, but you cannot leverage some partition elimination. If you want to get better performance by skipping the files that don't satisfy some criterion (like specific year or month in this case), use [views on external data](create-use-views.md#partitioned-views).
 
 ## External table on appendable files
 
@@ -153,7 +154,7 @@ WITH (
 );
 ```
 
-The `ALLOW_INCONSISTENT_READS` read option will disable file modification time check during the query lifecycle and read whatever is available in the files that are referenced by the external table. In appendable files, the existing content isn't updated, and only new rows are added. Therefore, the probability of wrong results is minimized compared to the updateable files. This option might enable you to read the frequently appended files without handling the errors.
+The `ALLOW_INCONSISTENT_READS` read option disables file modification time check during the query lifecycle and read whatever is available in the files that are referenced by the external table. In appendable files, the existing content isn't updated, and only new rows are added. Therefore, the probability of wrong results is minimized compared to the updateable files. This option might enable you to read the frequently appended files without handling the errors.
 
 This option is available only in the external tables created on CSV file format.
 
@@ -188,7 +189,7 @@ External tables can't be created on a partitioned folder. Review the other known
 External tables in serverless SQL pools don't support partitioning on Delta Lake format. Use [Delta partitioned views](create-use-views.md#delta-lake-partitioned-views) instead of tables if you have partitioned Delta Lake data sets. 
  
 > [!IMPORTANT]
-> Do not create external tables on partitioned Delta Lake folders even if you see that they might work in some cases. Using unsupported features like external tables on partitioned delta folders might cause issues or instability of the serverless pool. Azure support will not be able to resolve any issue if it is using tables on partitioned folders. You would be asked to transition to [Delta partitioned views](create-use-views.md#delta-lake-partitioned-views) and rewrite your code to use only the supported feature before proceeding with issue resolution.
+> Don't create external tables on partitioned Delta Lake folders even if you see that they might work in some cases. Using unsupported features like external tables on partitioned delta folders might cause issues or instability of the serverless pool. Azure support won't be able to resolve any issue if it's using tables on partitioned folders. You would be asked to transition to [Delta partitioned views](create-use-views.md#delta-lake-partitioned-views) and rewrite your code to use only the supported feature before proceeding with issue resolution.
 
 ## Use an external table
 
@@ -197,7 +198,7 @@ You can use [external tables](develop-tables-external-tables.md) in your queries
 The following query demonstrates this using the *population* external table we created in previous section. It returns country/region names with their population in 2019 in descending order.
 
 > [!NOTE]
-> Change the first line in the query, i.e., [mydbname], so you're using the database you created.
+> Change the first line in the query, that is, [mydbname], so you're using the database you created.
 
 ```sql
 USE [mydbname];