Address blocking issues.

Author: TimShererWithAquent

learn-pr/azure/intro-to-azure-incident-readiness/includes/2-communication-philosophy.md

@@ -4,7 +4,7 @@ We recognize the significance of effective communications during incidents and u
 
     We want you to know it's *us*, not you as quickly as possible. This goal is our key objective. Our goal is to notify all affected subscriptions and tenants within 15 minutes of an outage.
 
-    Due to the complexity of our platform, this approach can't be achieved with human beings alone. The fact is why we continue to invest in our [AIOps](https://azure.microsoft.com/blog/advancing-azure-service-quality-with-artificial-intelligence-aiops/) technology.
+    Due to the complexity of our platform, this approach can't be achieved with human beings alone. That fact is why we continue to invest in our [AIOps](https://azure.microsoft.com/blog/advancing-azure-service-quality-with-artificial-intelligence-aiops/) technology.
 
 - **Accuracy** - *Which of my resources are impacted?*
 

learn-pr/azure/intro-to-azure-incident-readiness/includes/3-prepare-for-unexpected.md

@@ -1,4 +1,4 @@
-To ensure preparedness and minimize the impact of incidents, it's essential to follow the proactive recommendations outlined in this unit. These actions help you understand our incident communication process, locate pertinent information, and configure notifications to receive timely updates. Evaluating the resilience of your applications and implementing recommended measures create more reliable workloads, which reduce the potential impact of an incident. Reviewing and implementing security best practices fortify your environment and mitigate risks.
+To ensure preparedness and minimize the impact of incidents, it's essential to follow the proactive recommendations outlined in this unit. These actions help you understand our incident communication process, locate pertinent information, and configure notifications to receive timely updates. Evaluating the resilience of your applications and implementing recommended measures creates more reliable workloads, which reduce the potential impact of an incident. Reviewing and implementing security best practices fortifies your environment and mitigate risks.
 
 ## To stay informed, mitigate impact, and protect your investment, we recommend the following five actions:
 
@@ -123,7 +123,7 @@ There's a key distinction between 'service health' alerts and 'resource health'
 
 You can configure resource health alerts from the Resource Health pane in the Service Health page of the Azure portal.
 
-:::image type="content" source="../media/azure-service-health-resource-health.png" alt-text="Screenshot of the Azure Service Health resource health.":::
+:::image type="content" source="../media/azure-service-health-resource-health.png" alt-text="Screenshot of the Azure Service Health resource health." lightbox="../media/azure-service-health-resource-health.png":::
 
 You can also create [resource health alerts programmatically](/azure/service-health/resource-health-alert-arm-template-guide) using Azure Resource Manager templates and Azure PowerShell. Creating resource health alerts programmatically allows you to create and customize alerts in bulk.
 

learn-pr/azure/intro-to-azure-incident-readiness/includes/4-what-to-expect.md

@@ -10,7 +10,7 @@ Although we generally don't share speculation or the inner workings of troublesh
 
     > [!NOTE]
     >
-    > Set up [Service Health alert](/azure/service-health/alerts-activity-log-service-notifications-portal) for getting notified of portal communications with the channel of your choice, such as email, SMS, or webhook.
+    > Set up [Service Health alerts](/azure/service-health/alerts-activity-log-service-notifications-portal) for getting notified of portal communications with the channel of your choice, such as email, SMS, or webhook.
 
 2. **If there are issues accessing Service Health or the portal itself, check the public [Azure Status page](https://status.azure.com/)**.
 

learn-pr/azure/intro-to-azure-incident-readiness/includes/5-after-an-incident.md

@@ -36,7 +36,7 @@ After each livestream, we publish a recording of the session to [this YouTube pl
 
 The Service Level Agreements (SLA) describe Microsoft's commitments for uptime and connectivity for Microsoft Online Services. The current and archived editions of the SLA are [available for download](https://aka.ms/csla) and they cover Azure, as well as Dynamics 365, Office 365, and Intune. If we don't achieve and maintain the Service Levels for each Service as described in this SLA for any reason, including as a result of one or more service incidents, customers might be eligible for a credit towards a portion of their monthly service fees.
 
-In order for Microsoft to consider an SLA credit request claim, you must submit a claim to customer support within two months of the end of the billing month in which the incident that is the subject of the claim occurred. To submit a claim, sign in to the Azure portal, [create a new support request](https://go.microsoft.com/fwlink/p/?linkid=2202692), select an Issue type of **Billing**, select a Problem type of **Refund Request**. Provide as much detail as possible, including the incident Tracking ID from Azure Service Health, and information around which services and resources you believe were impacted as a result.
+In order for Microsoft to consider an SLA credit request claim, you must submit a claim to customer support within two months of the end of the billing month in which the incident that is the subject of the claim occurred. To submit a claim, sign in to the Azure portal, [create a new support request](https://go.microsoft.com/fwlink/p/?linkid=2202692), select an Issue type of **Billing**, and select a Problem type of **Refund Request**. Provide as much detail as possible, including the incident Tracking ID from Azure Service Health, and information around which services and resources you believe were impacted as a result.
 
 Our billing support teams validate which resources, services, and subscriptions were impacted. They calculate and apply any relevant SLA credits. We use commercially reasonable efforts to process claims during the subsequent month and within 45 days of receipt. If we determine that a service credit is owed to you, we apply the service credit to your applicable monthly service fees.
 

learn-pr/azure/intro-to-azure-incident-readiness/includes/6-when-to-engage-support.md

@@ -1,7 +1,7 @@
-## Major incident process
-
 Whenever you notice an issue, the first step is to use the Azure Admin Portal to check the Service Health page to see if there's an active Service Incident for your subscriptions. This approach applies whether it's something your internal monitoring picked up or your users report.
 
+## Major incident process
+
 If there's an active incident and it matches the issue you're experiencing, you shouldn't open a support case. You can obtain all the latest information from service health about the incident and next action plan. You should engage support if the issue you're experiencing isn't already represented in Service Health. You should engage support if you read the updates from engineering but require support to respond to the incident, for example, to implement your failover plans. You can open a Support Case from the Admin Portal with a reference to the Service Health ID number for that Service Incident.
 
 If you don't see any active incidents showing in the Service Health page **OR** the description of incidents showing don't match the issues they're experiencing, you should open a Support Case. In this event, there isn't any Service Health ID number to reference.