Improve readability on TeamOps Decision Velocity

Why is this change being made?

• I made a few suggestions that would help the tenets beneath Decision Velocity be better understood by those from different backgrounds and cultural contexts and improve readability. This increases accessibility too and so is move inclusive. I did not change the meaning, just the way it's written.
• I also made a content suggestion under collaboration is not consensus to address how DRIs use this to be more effective as it wasn't immediately clear during the transition between the last two paragraphs of the section. Needed something in-between to help explain the connection there.
• My suggestion is part of the TEAMOPs requirement to submit MRs to complete my training

Author Checklist

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (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 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 affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
  • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

---