fix spacing issues

Rob Boucher · Rob Boucher · commit c0683cdafd5c · 2020-03-17T01:23:23.000-07:00
diff --git a/articles/azure-monitor/platform/alerts-troubleshoot.md b/articles/azure-monitor/platform/alerts-troubleshoot.md
@@ -23,11 +23,11 @@ If you can see a fired alert in the Azure portal, but did not receive the email
 
 1. **Was the email suppressed by an [action rule](alerts-action-rules.md)**? 
 
-Check by clicking on the fired alert in the portal, and look at the history tab for suppressed [action groups](action-groups.md): 
+    Check by clicking on the fired alert in the portal, and look at the history tab for suppressed [action groups](action-groups.md): 
 
     ![Alert action rule suppression history](media/alerts-troubleshoot/history-action-rule.png)
 
-1. **Is the type of action “Email Azure Resource Manager Role”?**
+1. **Is the type of action "Email Azure Resource Manager Role"?**
 
     This action only looks at Azure Resource Manager role assignments that are at the subscription scope, and of type *User*.  Make sure that you have assigned the Resource Manager role at the subscription level, and not at the resource level or resource group level.
 
@@ -120,35 +120,32 @@ If you can see a fired alert in the portal, but its configured action did not tr
 
 1. **Did a webhook not trigger?**
 
-    1. **Have the source IP addresses been blocked?** 
-    
+    1. **Have the source IP addresses been blocked?**     
     Whitelist the [IP addresses](action-groups.md#action-specific-information) that the webhook is called from.
 
     1. **Does your webhook endpoint work correctly?** 
-    
     Verify the webhook endpoint you have configured is correct and the endpoint is working correctly. Check your webhook logs or instrument its code so you could investigate (for example, log the incoming payload). 
 
     1. **Are you calling Slack or Microsoft Teams?**  
-    
     Each of these endpoints expects a specific JSON format. Follow [these instructions](action-groups-logic-app.md) to configure a logic app action instead.
 
     1. **Did your webhook became unresponsive or returned errors?** 
-    
-    Our timeout period for a webhook response is 10 seconds. The webhook call will be retried up to two additional times when the following HTTP status codes are returned: 408, 429, 503, 504, or when the HTTP endpoint does not respond. The first retry happens after 10 seconds. The second and final retry happens after 100 seconds. If the second retry fails, the endpoint will not be called again for 30 minutes for any action group.
+
+        Our timeout period for a webhook response is 10 seconds. The webhook call will be retried up to two additional times when the following HTTP status codes are returned: 408, 429, 503, 504, or when the HTTP endpoint does not respond. The first retry happens after 10 seconds. The second and final retry happens after 100 seconds. If the second retry fails, the endpoint will not be called again for 30 minutes for any action group.
 
 ## Action or notification happened more than once 
 
-If you have received a notification for an alert (such as an email or an SMS) more than once, or the alert’s action (such as webhook or Azure function) was triggered multiple times, follow these steps: 
+If you have received a notification for an alert (such as an email or an SMS) more than once, or the alert's action (such as webhook or Azure function) was triggered multiple times, follow these steps: 
 
 1. **Is it really the same alert?** 
 
-In some cases, multiple similar alerts are fired at around the same time. So, it might just seem like the same alert triggered its actions multiple times. For example, an activity log alert rule might be configured to fire both when an event has started, and when it has finished (succeeded or failed), by not filtering on the event status field. 
+    In some cases, multiple similar alerts are fired at around the same time. So, it might just seem like the same alert triggered its actions multiple times. For example, an activity log alert rule might be configured to fire both when an event has started, and when it has finished (succeeded or failed), by not filtering on the event status field. 
 
     To check if these actions or notifications came from different alerts, examine the alert details, such as its timestamp and either the alert id or its correlation id. Alternatively, check the list of fired alerts in the portal. If that is the case, you would need to adapt the alert rule logic or otherwise configure the alert source. 
 
 1. **Does the action repeat in multiple action groups?** 
 
-When an alert is fired, each of its action groups is processed independently. So, if an action (such as an email address) appears in multiple triggered action groups, it would be called once per action group. 
+    When an alert is fired, each of its action groups is processed independently. So, if an action (such as an email address) appears in multiple triggered action groups, it would be called once per action group. 
 
     To check which action groups were triggered, check the alert history tab. You would see there both action groups defined in the alert rule, and action groups added to the alert by action rules: 
 
@@ -160,7 +157,7 @@ If you have received the alert, but believe some of its fields are missing or in
 
 1. **Did you pick the correct format for the action?** 
 
-Each action type (email, webhook, etc.) has two formats – the default, legacy format, and the [newer common schema format](alerts-common-schema.md). When you create an action group, you specify the format you want per action – different actions in the action groups may have different formats. 
+    Each action type (email, webhook, etc.) has two formats – the default, legacy format, and the [newer common schema format](alerts-common-schema.md). When you create an action group, you specify the format you want per action – different actions in the action groups may have different formats. 
 
     For example, for webhook action: 
 
@@ -173,7 +170,7 @@ Each action type (email, webhook, etc.) has two formats – the default, legacy
  
 1. **Activity log alerts: Is the information available in the activity log?** 
 
-[Activity log alerts](activity-log-alerts.md) are alerts that are based on events written to the Azure Activity Log, such as events about creating, updating or deleting Azure resources, service health and resource health events, or findings from Azure Advisor and Azure Policy. If you have received an alert based on the activity log but some fields that you need are missing or incorrect, first check the events in the activity log itself. If the Azure resource did not write the fields you are looking for in its activity log event, those fields will not be included in the corresponding alert. 
+    [Activity log alerts](activity-log-alerts.md) are alerts that are based on events written to the Azure Activity Log, such as events about creating, updating or deleting Azure resources, service health and resource health events, or findings from Azure Advisor and Azure Policy. If you have received an alert based on the activity log but some fields that you need are missing or incorrect, first check the events in the activity log itself. If the Azure resource did not write the fields you are looking for in its activity log event, those fields will not be included in the corresponding alert. 
 
 ## Action rule is not working as expected 
 
@@ -187,7 +184,7 @@ If you can see a fired alert in the portal, but a related action rule did not wo
 
 1. **Is it a service health alert?** 
 
-    Service health alerts (monitor service = “Service Health”) are not affected by action rules. 
+    Service health alerts (monitor service = "Service Health") are not affected by action rules. 
 
 1. **Did the action rule act on your alert?** 
 
@@ -204,20 +201,20 @@ If you can see a fired alert in the portal, but a related action rule did not wo
 
 1. **Does the action rule scope and filter match the fired alert?** 
 
-    If you think the action rule should have fired but didn’t, or that it shouldn’t have fired but it did, carefully examine the action rule scope and filter conditions versus the properties of the fired alert. 
+    If you think the action rule should have fired but didn't, or that it shouldn't have fired but it did, carefully examine the action rule scope and filter conditions versus the properties of the fired alert. 
 
 
 ## How to find the alert id of a fired alert
 
 When opening a case about a specific fired alert (such as – if you did not receive its email notification), you will need to provide the alert id. 
 
-To locate it, follow these steps: 
+To locate it, follow these steps:
 
 1. In the Azure portal, navigate to the list of fired alerts, and find that specific alert. You can use the filters to help you locate it. 
 
 1. Click on the alert to open the alert details. 
 
-1. Scroll down in the alert fields of the first tab (the summary tab) until you locate it, and copy it. That field also includes a “Copy to clipboard” helper button you can use.  
+1. Scroll down in the alert fields of the first tab (the summary tab) until you locate it, and copy it. That field also includes a "Copy to clipboard" helper button you can use.  
 
     ![find alert id](media/alerts-troubleshoot/get-alert-id.png)
 
@@ -236,4 +233,4 @@ If you received an error while trying to create, update or delete an [action rul
 
 ## Next steps
 
-Go back to the Azure portal[http://portal.azure.com to check if you've solved your issue with any of the advice above
+Go back to the [Azure portal](http://portal.azure.com) to check if you've solved your issue with any of the advice above
