Update custom-logs-migrate.md

Author: guywi-ms

articles/azure-monitor/logs/custom-logs-migrate.md

@@ -58,7 +58,7 @@ If you have an existing custom table to which you currently send data using the
     This is the preferred option, especially if you to need to make changes to the existing table. Changes to existing data types and multiple schema changes to existing Data Collector API custom tables can lead to errors.
 
 > [!TIP]
-> To identify which tables use the Data Collector API, [view table properties](../../logs/manage-logs-tables.md#view-table-properties). The **Type** property of tables that use the Data Collector API is set to **Custom table (classic)**. Note that tables that ingest data using the legacy Log Analytics agent (MMA) also have the **Type** property set to **Custom table (classic)**. Be sure to migrate from Log Analytics agent to Azure Monitor Agent before converting MMA tables; otherwise, you will stop ingesting data into custom fields in these tables after the table conversion.   
+> To identify which tables use the Data Collector API, [view table properties](../../logs/manage-logs-tables.md#view-table-properties). The **Type** property of tables that use the Data Collector API is set to **Custom table (classic)**. Note that tables that ingest data using the legacy Log Analytics agent (MMA) also have the **Type** property set to **Custom table (classic)**. Be sure to migrate from Log Analytics agent to Azure Monitor Agent before converting MMA tables. Otherwise, you'll stop ingesting data into custom fields in these tables after the table conversion.   
 
 This table summarizes considerations to keep in mind for each option: