diff --git a/docs/content/patterns/alz/Alerts-Details.md b/docs/content/patterns/alz/Alerts-Details.md
index 1c9d24e30..7038b99bb 100644
--- a/docs/content/patterns/alz/Alerts-Details.md
+++ b/docs/content/patterns/alz/Alerts-Details.md
@@ -29,7 +29,7 @@ We have tried to make it so that the table doesn't require a lot of side to side
 
 {{< alzMetricAlerts >}}
 
-<sup>1</sup> See "Why are the availability alert thresholds lower than 100% in this solution when the product group documention recommends 100%?" in the [FAQ](FAQ.md) for more details.
+<sup>1</sup> See "Why are the availability alert thresholds lower than 100% in this solution when the product group documention recommends 100%?" in the [FAQ]({{< ref "FAQ.md" >}}) for more details.
 
 ## Azure Landing Zone Activity Log Alerts
 
diff --git a/docs/content/patterns/alz/Known-Issues.md b/docs/content/patterns/alz/Known-Issues.md
index d5bb4a064..8c6849bbf 100644
--- a/docs/content/patterns/alz/Known-Issues.md
+++ b/docs/content/patterns/alz/Known-Issues.md
@@ -16,7 +16,7 @@ The underlying data is not present in the Log Analytics table.
 
 ### Resolution
 
-For VM Alerts please enable [VM Insights](Monitoring-and-Alerting#log-alerts).
+For VM Alerts please enable [VM Insights]({{< ref "Monitoring-and-Alerting.md#log-alerts" >}}).
 
 ## Failed to deploy because of role assignemnt issue
 
diff --git a/docs/content/patterns/alz/Monitoring-and-Alerting.md b/docs/content/patterns/alz/Monitoring-and-Alerting.md
index 4833324f1..bd1df51b2 100644
--- a/docs/content/patterns/alz/Monitoring-and-Alerting.md
+++ b/docs/content/patterns/alz/Monitoring-and-Alerting.md
@@ -44,11 +44,11 @@ ALZ Alerts, Action Groups and Alert Processing Rules are deployed using Azure Po
 
 The following policy definition categories will be enabled as part of ALZ deployments for the hubs and landing zones defined by Azure landing zone:
 
-- Resource Metrics; See [here](../Alerts-Details#metric-alerts-settings) for details on which resource metrics are included.
-- Service and Resource Health; See [here](../Alerts-Details#activity-log-alerts) for details on which alerts are included.
-- Activity Logs; See [here](../Alerts-Details#activity-log-administrative) for details on which alerts are included.
-- VM Insights Log Alerts; See [here](../Alerts-Details#vm-insights-log-alerts) for details on which alerts are included.
-- Recovery Vault Alerts; See [here](../Alerts-Details#recovery-vault-alerts) for details on which alerts are included.
+- Resource Metrics; See [here]({{< ref "Alerts-Details.md#metric-alerts-settings" >}}) for details on which resource metrics are included.
+- Service and Resource Health; See [here]({{< ref "Alerts-Details.md#activity-log-alerts" >}}) for details on which alerts are included.
+- Activity Logs; See [here]({{< ref "Alerts-Details.md#activity-log-administrative" >}}) for details on which alerts are included.
+- VM Insights Log Alerts; See [here]({{< ref "Alerts-Details.md#vm-insights-log-alerts" >}}) for details on which alerts are included.
+- Recovery Vault Alerts; See [here]({{< ref "Alerts-Details.md#recovery-vault-alerts" >}}) for details on which alerts are included.
 
 #### Resource Metrics
 
@@ -120,4 +120,5 @@ Azure Backup now provides new and improved alerting capabilities via Azure Monit
 ```
 
 ### Notifications
+
 While alerts are generated by default and can't be turned off for destructive operations, the notifications are in the control of the user, allowing you to clearly specify which set of email address (or other notification endpoints) you wish to route alerts to. Notifications are configured by an alert processing rule, which will be created by default when deploying AMBA.