consistent use of naming (#7922)

Author: PhilBastian

persistence/azure-table/migration-from-azure-storage-table-to-cosmos-table.md

@@ -1,5 +1,5 @@
 ---
-title: Migration from Azure Storage Table to Azure Cosmos DB Table API
+title: Migration from Azure Table Storage to Azure Cosmos DB Table API
 component: ASP
 related:
 - persistence/azure-table
@@ -9,7 +9,7 @@ reviewed: 2025-11-24
 > [!WARNING]
 > The endpoint being migrated must be offline while migrating saga data. The migration scenario described assumes only saga data of one saga type is stored per table.
 
-This guide describes how to migrate saga data from Azure Storage Table to Azure Cosmos DB Table API. Teams that start with Azure Storage Tables may later find they need to migrate to Cosmos DB Table API for requirements such as global distribution, improved performance, or other Cosmos DB features. The migration process uses Microsoft's Azure Cosmos DB Desktop Data Migration Tool to transfer saga data from the source Azure Storage Table to the destination Cosmos DB Table API account.
+This guide describes how to migrate saga data from Azure Table Storage to Azure Cosmos DB Table API. Teams that start with Azure Table Storage may later find they need to migrate to Cosmos DB Table API for requirements such as global distribution, improved performance, or other Cosmos DB features. The migration process uses Microsoft's Azure Cosmos DB Desktop Data Migration Tool to transfer saga data from the source Azure Table Storage to the destination Cosmos DB Table API account.
 
 ## Import data
 
@@ -92,4 +92,4 @@ The tool will automatically read the `migrationsettings.json` file from the curr
 
 ## Data inspection
 
-Due to the [limited types](https://docs.microsoft.com/en-us/rest/api/storageservices/understanding-the-table-service-data-model#property-types) supported by Azure Storage Tables, some types are stored in the table by the [Azure Table persister](/persistence/azure-table) as serialized JSON strings. The data can and should be inspected for quality both before and after the import. The migrated endpoint and all saga types migrated should be thoroughly tested before moving into production to ensure the migration is correct.
+Due to the [limited types](https://docs.microsoft.com/en-us/rest/api/storageservices/understanding-the-table-service-data-model#property-types) supported by Azure Storage Tables, some types are stored in the table by the [Azure Table persister](/persistence/azure-table) as serialized JSON strings. The data can and should be inspected for quality both before and after the import. The migrated endpoint and all saga types migrated should be thoroughly tested before moving into production to ensure the migration is correct.