docs: additional v6 upgrade detail (Azure#1002)

docs/wiki/[User-Guide]-Module-upgrade-guidance.md

@@ -46,6 +46,7 @@ If jumping multiple release versions, take care to note additional changes docum
 
 Please refer to the following upgrade guides when updating between major release:
 
+- [Upgrade from v5.2.1 to v6.0.0][wiki_upgrade_from_v5_2_1_to_v6_0_0]
 - [Upgrade from v5.1.0 to v5.2.0][wiki_upgrade_from_v5_1_0_to_v5_2_0]
 - [Upgrade from v4.2.0 to v5.0.0][wiki_upgrade_from_v4_2_0_to_v5_0_0]
 - [Upgrade from v3.3.0 to v4.0.0][wiki_upgrade_from_v3_3_0_to_v4_0_0]
@@ -64,6 +65,7 @@ Please refer to the following upgrade guides when updating between major release
 [module_releases]:     https://github.com/Azure/terraform-azurerm-caf-enterprise-scale/releases "Releases - Azure/terraform-azurerm-caf-enterprise-scale"
 
 [wiki_module_releases]:               %5BUser-Guide%5D-Module-Releases "Wiki - [User Guide] Module Releases"
+[wiki_upgrade_from_v5_2_1_to_v6_0_0]: %5BUser-Guide%5D-Upgrade-from-v5.2.1-to-v6.0.0 "Wiki - Upgrade from v5.2.1 to v6.0.0"
 [wiki_upgrade_from_v5_1_0_to_v5_2_0]: %5BUser-Guide%5D-Upgrade-from-v5.1.0-to-v5.2.0 "Wiki - Upgrade from v5.1.0 to v5.2.0"
 [wiki_upgrade_from_v4_2_0_to_v5_0_0]: %5BUser-Guide%5D-Upgrade-from-v4.2.0-to-v5.0.0 "Wiki - Upgrade from v4.2.0 to v5.0.0"
 [wiki_upgrade_from_v3_3_0_to_v4_0_0]: %5BUser-Guide%5D-Upgrade-from-v3.3.0-to-v4.0.0 "Wiki - Upgrade from v3.3.0 to v4.0.0"

docs/wiki/[User-Guide]-Upgrade-from-v5.2.1-to-v6.0.0.md

@@ -5,7 +5,7 @@ This is a major release, following the update of Azure Landing Zones with it's m
 
 ## ‼️ Breaking Changes
 
-1. Minimum AzureRM provider version now 3.107.0`
+1. Minimum AzureRM provider version now `3.107.0`
 2. Minimum Terraform version now `1.7.0`
 3. `var.configure_management_resources` schema change, removing legacy components and adding support for AMA resources
 
@@ -41,8 +41,9 @@ If you wish to continue using the MMA, you will need to manage this outside of t
 
 As MMA resources were deployed using Azure Policy (DeployIfNotExists), the resources will not be cleaned up automatically.
 You will need to manually clean up the resources.
+Please see product group guidance on how to clean up the MMA resources: <https://learn.microsoft.com/azure/azure-monitor/agents/azure-monitor-agent-mma-removal-tool?tabs=single-tenant%2Cdiscovery>.
 
-We will publish a link to the MMA migration guidance once it is released, this will contain the steps to clean up the legacy MMA resources.
+We will publish a link to additional ALZ tooling once it is published.
 
 ## Notable changes from our awesome community