Fixes errors (#452)

Author: sarahsimpers

source/includes/extracts-alerts.yaml

@@ -17,9 +17,9 @@ content: |
      :stub-columns: 1
 
      * - {+bagent+} has too many conf call failures
-       - The cluster topology known to monitoring does not match the backup
-         configuration from :term:`conf calls <conf call>` the {+bagent+}
-         makes. 
+
+       - The cluster topology known to monitoring does not match the
+         backup configuration from :term:`conf calls <conf call>` the {+bagent+} makes. 
 
          The number of attempts meets the threshold you specified in
          :setting:`maximumFailedConfCalls
@@ -28,6 +28,7 @@ content: |
 
          You can use this alert as a :ref:`global alert <mms-manage-global-alerts>` only.
 
+
 ---
 ref: alert-global-alerts
 content: |
@@ -42,9 +43,10 @@ content: |
 
          For example, reasons that a job might fail to bind include, but are not limited to:
 
-         - No :manual:`primary </reference/glossary/#std-term-primary>` is found for the backed-up replica
-         set. At the time the binding occurred, the {+magent+} did not detect a primary. Ensure that the replica
-         set is healthy.
+         - No :manual:`primary </reference/glossary/#std-term-primary>`
+           is found for the backed-up replica
+           set. At the time the binding occurred, the {+magent+} did not detect a primary. Ensure that the replica
+           set is healthy.
      
          - Not enough space is available on any Backup Daemon.
 
@@ -131,6 +133,7 @@ content: |
      :stub-columns: 1
 
      * - Host is down
+
        - |mms| does not receive a ping from a host for more than 4
          minutes. Under normal operation, the {+magent+} connects
          to each monitored host about once per minute. |mms| waits 4