diff --git a/docs/content/patterns/alz/FAQ.md b/docs/content/patterns/alz/FAQ.md
index 2b8840a96..2c96edbe7 100644
--- a/docs/content/patterns/alz/FAQ.md
+++ b/docs/content/patterns/alz/FAQ.md
@@ -8,10 +8,6 @@ weight: 80
 
 *No but you will need to be using Azure Management groups and for now our focus is on the resources frequently deployed as part of Azure Landing Zone deployments.*
 
-## Do I need to deploy to each region that I want to monitor?
-
-*No deploying to multiple regions is not necessary. The definitions and assignments are scoped to a management group and are not region specific.*
-
 ## Do I need to use the thresholds defined as default values in the metric rule alerts?
 
 *It's provided as a starting point, we've based the initial thresholds on what we've seen and what Microsoft's documentation recommends. You will need to adjust the thresholds at some point.*
diff --git a/docs/content/patterns/alz/Known-Issues.md b/docs/content/patterns/alz/Known-Issues.md
index 13d516b42..ce1586fc1 100644
--- a/docs/content/patterns/alz/Known-Issues.md
+++ b/docs/content/patterns/alz/Known-Issues.md
@@ -48,19 +48,18 @@ When a role or a role assignement is removed, some orphaned object can still app
 
 ### Cause
 
-A deployment has been performed using one region, for example "uksouth", and when you try to deploy again to the same scope but to a different region you will receive an error. This happens even when a cleanup has been performed (see [Cleaning up a Deployment](../Cleaning-up-a-Deployment) for more details). This is because deployment entries still exists from the previous operation, so a region conflict is detected blocking you to run another deployment using a different region.
+A deployment has been performed using one region (i.e. 'uksouth') in the command line. A subsequent cleanup is performed to allow a second deploy against a different region (i.e. 'westeurope'). Deployment entries still exists from the previous operation, so a region conflict is detected blocking you to run another deployment using a different region.
 
 ### Resolution
-Situation 1: You are trying to deploy to a different region in addition to a previous deployment. Deploying to the same scope in a different region is not necessary. The definitions and assignments are scoped to a management group and are not region specific. No action is required.
 
-Situation 2: You cleaned up a previous implementation and want to deploy again to a different region. To resolve this issue, follow the steps below:
+To resolve this issue, follow the steps below:
 
 1. Navigate to ***Management Groups***
 2. Select the management group (corresponding to the value entered for the *enterpriseScaleCompanyPrefix* during the deployment) were AMBA deployment was targeted to
 3. Click ***Deployment***
 4. Select all the deployment instances related to AMBA and click ***Delete***.
 
-{{< hint type=Note >}}
+{{< hint type=Important >}}
 To recognize the deployment names belonging to AMBA, select those whose names start with:
 
 1. amba-