Improve cadence flow example
Why is this change being made?
Improving flow between cadence items and removing definitions as those should only appear in the above section. Definitions consolidated in this MR
!119020 (merged)
Based on discussion with Sid
https://docs.google.com/document/d/1T-cSJ2S-no_Kixmj22OxeyBG5qgkfA99IXaR61pbl04/edit#bookmark=id.1huivv5gy9bj
Better match to descriptions and examples from quarter kick-off slides
https://docs.google.com/presentation/d/1BeYhIFFovN4dlAJmj9IVPugrDmGsRmnUDN3yvvRkGto/edit#slide=id.g1fe62023c23_4_78
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, and the content is SAFE
-
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
- The when to get approval handbook section explains the workflow in more detail
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
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.