additional edits

Author: Kat-Campise

articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-overview-develop.md

@@ -1,6 +1,6 @@
 ---
 title: Resources for developing a Synapse SQL pool in Azure Synapse Analytics
-description: Development concepts, design decisions, recommendations and coding techniques for SQL pool.
+description: Development concepts, design decisions, recommendations, and coding techniques for SQL pool.
 services: synapse-analytics
 author: XiaoyuMSFT
 manager: craigg

articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-tables-data-types.md

@@ -16,7 +16,7 @@ ms.custom: seo-lt-2019
 # Table data types in Synapse SQL pool
 Included in this article are recommendations for defining table data types in SQL pool. 
 
-## What are the data types?
+## Supported data types
 
 SQL pool supports the most commonly used data types. For a list of the supported data types, see [data types](/sql/t-sql/statements/create-table-azure-sql-data-warehouse#DataTypes) in the CREATE TABLE statement. 
 
@@ -44,7 +44,7 @@ WHERE y.[name] IN ('geography','geometry','hierarchyid','image','text','ntext','
 
 ## <a name="unsupported-data-types"></a>Workarounds for unsupported data types
 
-The following list shows the data types that SQL pool does not support and gives useful alternatives for unsupported data types.
+The following list shows the data types that SQL pool doesn't support and gives useful alternatives for unsupported data types.
 
 | Unsupported data type | Workaround |
 | --- | --- |
@@ -56,11 +56,12 @@ The following list shows the data types that SQL pool does not support and gives
 | [ntext](/sql/t-sql/data-types/ntext-text-and-image-transact-sql) |[nvarchar](/sql/t-sql/data-types/nchar-and-nvarchar-transact-sql) |
 | [sql_variant](/sql/t-sql/data-types/sql-variant-transact-sql) |Split column into several strongly typed columns. |
 | [table](/sql/t-sql/data-types/table-transact-sql) |Convert to temporary tables. |
-| [timestamp](/sql/t-sql/data-types/date-and-time-types) |Rework code to use [datetime2](/sql/t-sql/data-types/datetime2-transact-sql) and the [CURRENT_TIMESTAMP](/sql/t-sql/functions/current-timestamp-transact-sql) function. Only constants are supported as defaults, so current_timestamp can't be defined as a default constraint. If you need to migrate row version values from a timestamp typed column, then use [BINARY](/sql/t-sql/data-types/binary-and-varbinary-transact-sql)(8) or [VARBINARY](/sql/t-sql/data-types/binary-and-varbinary-transact-sql)(8) for NOT NULL or NULL row version values. |
+| [timestamp](/sql/t-sql/data-types/date-and-time-types) |Rework code to use [datetime2](/sql/t-sql/data-types/datetime2-transact-sql) and the [CURRENT_TIMESTAMP](/sql/t-sql/functions/current-timestamp-transact-sql) function. Only constants are supported as defaults, so current_timestamp can't be defined as a default constraint. If you need to migrate row version values from a timestamp typed column, use [BINARY](/sql/t-sql/data-types/binary-and-varbinary-transact-sql)(8) or [VARBINARY](/sql/t-sql/data-types/binary-and-varbinary-transact-sql)(8) for NOT NULL or NULL row version values. |
 | [xml](/sql/t-sql/xml/xml-transact-sql) |[varchar](/sql/t-sql/data-types/char-and-varchar-transact-sql) |
 | [user-defined type](/sql/relational-databases/native-client/features/using-user-defined-types) |Convert back to the native data type when possible. |
 | default values | Default values support literals and constants only. |
 
 
 ## Next steps
+
 For more information on developing tables, see [Table Overview](sql-data-warehouse-tables-overview.md).