Merge pull request #50662 from TimShererWithAquent/tr1055052

Technical review and freshness 1055052: Introduction to Azure Incident Readiness

Author: JillGrant615

learn-pr/azure/intro-to-azure-incident-readiness/includes/1-introduction.md

@@ -1,9 +1,11 @@
-Welcome to the "Azure Incident Readiness" module, where we not only provide you with the essential knowledge needed to handle Azure incidents but also emphasize the importance of readiness.
+Welcome to the "Azure Incident Readiness" module. Here, we not only provide you with the essential knowledge needed to handle Azure incidents but also emphasize the importance of readiness.
 
-We believe in fostering a culture of preparedness and proactiveness, ensuring that you're well-equipped to mitigate impact, protect your environment, and stay informed throughout incident lifecycles.
+We believe in fostering a culture of preparedness and proactiveness. We want to ensure that you're well-equipped to mitigate impact, protect your environment, and stay informed throughout incident lifecycles.
 
-Microsoft categorizes cloud incidents into three types: service incidents, privacy incidents, and security incidents.
+Microsoft categorizes cloud incidents into three types: *service incident*, *privacy incident*, and *security incident*.
 
-A service incident is an event or a series of events that can cause an interruption or degraded experience for customers using one or more of Microsoft's services. These incidents are effectively unplanned downtime including outages impacting availability, performance degradation impacting users, and problems interfering with service administration/management.
+- A *service incident* is an event or a series of events that can cause an interruption or degraded experience for customers who use one or more of Microsoft's services. These incidents are effectively unplanned downtime. This downtime includes outages impacting availability, performance degradation impacting users, and problems interfering with service administration and management.
 
-Security incidents are a confirmed breach that leads to destruction, loss, or unauthorized disclosure of customer data, or access to customer or personal data while being processed by Microsoft. Privacy incidents pertain to potential unauthorized use or disclosure of customer data.
+- A *privacy incident* is a potential unauthorized use or disclosure of customer data.
+
+- A *security incident* is a confirmed breach that leads to destruction, loss, or unauthorized disclosure of customer data, or access to customer or personal data while being processed by Microsoft.

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

@@ -1,24 +1,23 @@
-We recognize the significance of effective communications during incidents and understand how critical they're to you. In our efforts to provide you with the right information at the right time, we operate by these five pillars that guide our communications strategy:
+We recognize the significance of effective communications during incidents and understand how critical they're to you. In our efforts to provide you with the right information at the right time, these five pillars that guide our communications strategy:
 
-- **Speed** - _"Is it me or is it Azure?"_
+- **Speed** - *Is it me or is it Azure?*
 
-    We want you to know it's _us_, not you as quickly as possible. This is our key objective. Our goal is to notify all impacted subscriptions and tenants within 15 minutes of an outage. 
+    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.
 
-    This can't be achieved with human beings alone due to the vast complexity of our platform, which 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?"_
+- **Accuracy** - *Which of my resources are impacted?*
 
-    We understand that when an incident causes impact, you need to know exactly which resources are affected. Using [Resource Health](/azure/service-health/resource-health-overview) signals and alerts, we're able to show you the health of your resources and which are impacted by an incident.
+    We understand that when an incident causes impact, you need to know exactly which resources are affected. Using [Resource Health](/azure/service-health/resource-health-overview) signals and alerts, we're able to show you the health of your resources and which the incident affects.
 
-- **Discoverability** - _"How can I be notified proactively?"_
+- **Discoverability** - *How can I be notified proactively?*
 
     We encourage you to configure relevant notifications based on who needs to receive them and how they would best be notified.
 
-- **Parity** - _"How can I standardize operations across services?"_
+- **Parity** - *How can I standardize operations across services?*
 
-    We aim to standardize operations and achieve consistency across Azure services, addressing challenges such as providing consistent experiences across our service health communication types and harmonizing the Microsoft cloud ecosystem for a more seamless experience for you.
+    We aim to standardize operations and achieve consistency across Azure services. This approach provides consistent experiences across our service health communication types. The approach harmonizes the Microsoft cloud ecosystem for a more seamless experience.
 
-- **Transparency** - _"What really happened?"_
-
-    We think of transparency as a DIAL and not a SWITCH. We know that to build trust in the cloud, we need to be transparent with you. Transparent about what happened, transparent about where our failings were and what we're doing about it, and transparent about what you could have done to avoid this.
+- **Transparency** - *What really happened?*
 
+    We think of transparency as a DIAL and not a SWITCH. We know that to build trust in the cloud, we need to be transparent with you. Transparent about what happened, transparent about where our failings were and what we're doing about it, and transparent about what you could have done to avoid this incident.