Updating the CMS handbook page to (rearrange data, consolidate failure guidelines)

Why is this change being made?

• Attempting to consolidate and enrich information around what to do in case of scenario failure.
  • My assumption is that highlighting this in one location - even if repeated elsewhere - could reduce risk of skewed calculations or wasting resources.
• Rearranging the ranges in the CMS analysis table to order from low-high instead of high-low.
  • The ranges in the CMS table previously read from High # - Low #. I changed this to Low # - High #. It was difficult for me to scan these ranges previously as I am used to viewing them Low-high. This could just be my lack of data analysis knowledge, or that I am from the states. 🤔 I wanted to raise it though. For example:

Before	After

• Various copy and formatting changes.
  • I tried not to reword when possible, but moved some of the content around within sections to better consolidate.

Author Checklist

• Provided a concise title for the MR
• Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
• Assign this change to the correct DRI
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
  • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files. (this requirement has been removed pending identification of a new DRI for the handbook)