spell out DW

Author: v-shorestris

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

@@ -105,7 +105,7 @@ The primary drivers for choosing a virtual data mart implementation over a physi
 
 - Lower total cost of ownership—a virtualized implementation requires fewer data stores and copies of data.
 
-- Elimination of ETL jobs to migrate and simplify DW architecture in a virtualized environment.
+- Elimination of ETL jobs to migrate and simplify data warehouse architecture in a virtualized environment.
 
 - Performance—although physical data marts have historically been more performant, virtualization products now implement intelligent caching techniques to mitigate.
 

articles/synapse-analytics/migration-guides/netezza/4-visualization-reporting.md

@@ -92,7 +92,7 @@ There's a lot to think about here, so let's look at all this in more detail.
 > [!TIP]
 > A lift and shift data warehouse migration are likely to minimize any disruption to reports, dashboards, and other visualizations.
 
-## Minimizing the impact of DW migration on BI tools and reports using data virtualization
+## Minimizing the impact of data warehouse migration on BI tools and reports using data virtualization
 
 > [!TIP]
 > Data virtualization allows you to shield business users from structural changes during migration so that they remain unaware of changes.

articles/synapse-analytics/migration-guides/netezza/7-beyond-data-warehouse-migration.md

@@ -20,7 +20,7 @@ This article is part seven of a seven part series that provides guidance on how
 
 One of the key reasons to migrate your existing data warehouse to Azure Synapse is to utilize a globally secure, scalable, low-cost, cloud-native, pay-as-you-use analytical database. Azure Synapse also lets you integrate your migrated data warehouse with the complete Microsoft Azure analytical ecosystem to take advantage of, and integrate with, other Microsoft technologies that help you modernize your migrated data warehouse. This includes integrating with technologies like:
 
-- Azure Data Lake Storage—for cost effective data ingestion, staging, cleansing and transformation to free up DW capacity occupied by fast growing staging tables
+- Azure Data Lake Storage—for cost effective data ingestion, staging, cleansing and transformation to free up data warehouse capacity occupied by fast growing staging tables
 
 - Azure Data Factory—for collaborative IT and self-service data integration [with connectors](/azure/data-factory/connector-overview) to cloud and on-premises data sources and streaming data
 

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

@@ -100,7 +100,7 @@ The primary drivers for choosing a virtual data mart implementation over a physi
 
 - Lower total cost of ownership—a virtualized implementation requires fewer data stores and copies of data.
 
-- Elimination of ETL jobs to migrate and simplify DW architecture in a virtualized environment.
+- Elimination of ETL jobs to migrate and simplify data warehouse architecture in a virtualized environment.
 
 - Performance—although physical data marts have historically been more performant, virtualization products now implement intelligent caching techniques to mitigate.
 

articles/synapse-analytics/migration-guides/teradata/4-visualization-reporting.md

@@ -92,7 +92,7 @@ There's a lot to think about here, so let's look at all this in more detail.
 > [!TIP]
 > A lift and shift data warehouse migration are likely to minimize any disruption to reports, dashboards, and other visualizations.
 
-## Minimizing the impact of DW migration on BI tools and reports using data virtualization
+## Minimizing the impact of data warehouse migration on BI tools and reports using data virtualization
 
 > [!TIP]
 > Data virtualization allows you to shield business users from structural changes during migration so that they remain unaware of changes.

articles/synapse-analytics/migration-guides/teradata/7-beyond-data-warehouse-migration.md

@@ -20,7 +20,7 @@ This article is part seven of a seven part series that provides guidance on how
 
 One of the key reasons to migrate your existing data warehouse to Azure Synapse is to utilize a globally secure, scalable, low-cost, cloud-native, pay-as-you-use analytical database. Azure Synapse also lets you integrate your migrated data warehouse with the complete Microsoft Azure analytical ecosystem to take advantage of, and integrate with, other Microsoft technologies that help you modernize your migrated data warehouse. This includes integrating with technologies like:
 
-- Azure Data Lake Storage—for cost effective data ingestion, staging, cleansing and transformation to free up DW capacity occupied by fast growing staging tables
+- Azure Data Lake Storage—for cost effective data ingestion, staging, cleansing and transformation to free up data warehouse capacity occupied by fast growing staging tables
 
 - Azure Data Factory—for collaborative IT and self-service data integration [with connectors](/azure/data-factory/connector-overview) to cloud and on-premises data sources and streaming data