20220524 1407 build review

Author: WilliamDAssafMSFT

articles/synapse-analytics/migration-guides/netezza/1-design-performance-migration.md

@@ -153,7 +153,7 @@ Netezza implements some database objects that aren't directly supported in Azure
   - Temporal columns. For instance, `DATE`, `TIME`, and `TIMESTAMP`.
   - `CHAR` columns, if these are part of a materialized view and mentioned in the `ORDER BY` clause.
 
-  You can find out which columns have zone maps by using the nz_zonemap utility, which is part of the NZ Toolkit. Azure Synapse doesn't include zone maps, but you can achieve similar results by using other user-defined index types and/or partitioning.
+  You can find out which columns have zone maps by using the `nz_zonemap` utility, which is part of the NZ Toolkit. Azure Synapse doesn't include zone maps, but you can achieve similar results by using other user-defined index types and/or partitioning.
 
 - Clustered Base tables (CBT)—In Netezza, CBTs are commonly used for fact tables, which can have billions of records. Scanning such a huge table requires a lot of processing time, since a full table scan might be needed to get relevant records. Organizing records on restrictive CBT via allows Netezza to group records in same or nearby extents. This process also creates zone maps that improve the performance by reducing the amount of data to be scanned.
 

articles/synapse-analytics/migration-guides/netezza/5-minimize-sql-issues.md

@@ -79,7 +79,7 @@ Netezza implements some database objects that aren't directly supported in Azure
   - Temporal columns. For instance, `DATE`, `TIME`, and `TIMESTAMP`.
   - `CHAR` columns, if these are part of a materialized view and mentioned in the `ORDER BY` clause.
 
-  You can find out which columns have zone maps by using the nz_zonemap utility, which is part of the NZ Toolkit. Azure Synapse doesn't include zone maps, but you can achieve similar results by using other user-defined index types and/or partitioning.
+  You can find out which columns have zone maps by using the `nz_zonemap` utility, which is part of the NZ Toolkit. Azure Synapse doesn't include zone maps, but you can achieve similar results by using other user-defined index types and/or partitioning.
 
 - Clustered Base tables (CBT)—In Netezza, CBTs are commonly used for fact tables, which can have billions of records. Scanning such a huge table requires a lot of processing time, since a full table scan might be needed to get relevant records. Organizing records on restrictive CBT via allows Netezza to group records in same or nearby extents. This process also creates zone maps that improve the performance by reducing the amount of data to be scanned.
 

articles/synapse-analytics/migration-guides/teradata/2-etl-load-migration-considerations.md

@@ -39,7 +39,7 @@ It makes sense to only migrate tables that are in use in the existing system. Ta
 
 If enabled, Teradata system catalog tables and logs contain information that can determine when a given table was last accessed—which can in turn be used to decide whether a table is a candidate for migration.
 
-Here's an example query on dbc.tables that provides the date of last access and last modification:
+Here's an example query on `DBC.Tables` that provides the date of last access and last modification:
 
 ```sql
 SELECT TableName, CreatorName, CreateTimeStamp, LastAlterName,
@@ -77,7 +77,7 @@ With this approach, standard Teradata utilities, such as Teradata Parallel Data
 
 - The migration process is orchestrated and controlled entirely within the Azure environment.
 
-#### Migrating data marts—stay physical or go virtual?
+#### Migrating data marts - stay physical or go virtual?
 
 > [!TIP]
 > Virtualizing data marts can save on storage and processing resources.
@@ -130,7 +130,7 @@ The first step is always to build an inventory of ETL/ELT processes that need to
 
 In the preceding flowchart, decision 1 relates to a high-level decision about whether to migrate to a totally Azure-native environment. If you're moving to a totally Azure-native environment, we recommend that you re-engineer the ETL processing using [Pipelines and activities in Azure Data Factory](/azure/data-factory/concepts-pipelines-activities?msclkid=b6ea2be4cfda11ec929ac33e6e00db98&tabs=data-factory) or [Synapse Pipelines](/azure/synapse-analytics/get-started-pipelines?msclkid=b6e99db9cfda11ecbaba18ca59d5c95c). If you're not moving to a totally Azure-native environment, then decision 2 is whether an existing third-party ETL tool is already in use.
 
-In the Teradata environment, some or all ETL processing may be performed by custom scripts using Teradata-specific utilities like BTEQ and TPT. In this case, your approach should be to reengineer using Data Factory.
+In the Teradata environment, some or all ETL processing may be performed by custom scripts using Teradata-specific utilities like BTEQ and TPT. In this case, your approach should be to re-engineer using Data Factory.
 
 > [!TIP]
 > Leverage investment in existing third-party tools to reduce cost and risk.

articles/synapse-analytics/migration-guides/teradata/3-security-access-operations.md

@@ -84,8 +84,8 @@ The information about current users and roles in a Teradata system is found in t
 /***SQL to find all users***/
 SELECT
 DatabaseName AS UserName
-From dbc.databases
-Where dbkind = 'u';
+FROM DBC.Databases
+WHERE dbkind = 'u';
 
 /***SQL to find all roles***/
 SELECT A.ROLENAME, A.GRANTEE, A.GRANTOR,