Merge pull request #261924 from tksh164/patch-1

prmerger-automator[bot] · web-flow · commit b5cf9c2d2e41 · 2024-01-03T19:13:59.000Z
Fix typo
diff --git a/articles/azure-monitor/agents/azure-monitor-agent-custom-text-log-migration.md b/articles/azure-monitor/agents/azure-monitor-agent-custom-text-log-migration.md
@@ -12,7 +12,7 @@ This article describes the steps to migrate a [MMA Custom text log](data-sources
 MMA custom text logs must be configured to support new features in order for AMA custom text log DCRs to write to it. The following actions are taken:
 - The table is reconfigured to enable all DCR-based custom logs features.
 - All MMA custom fields stop updating in the table. AMA can write data to any column in the table. 
-- The MMS Custom text log can write to noncustom fields, but it will not be able to create new columns. The portal table management UI can be used to change the schema after migration.
+- The MMA Custom text log can write to noncustom fields, but it will not be able to create new columns. The portal table management UI can be used to change the schema after migration.
 
 ## Migration procedure
 You should follow the steps only if the following criteria are true:  
