Improving the "Common Requirements" pattern

Some ideas for improving the Common Requirements pattern:

• Improve the Patlet - escpecially describe how the Solution is improving upon the Problem
• Break up Forces into bullets - so that readers can check more easily if these forces apply in their orgs as well
• Decide what to do with the Resulting Context: It currently focuses mostly on other related challenges that may need to be solved after this pattern is in place. However it lacks explanation of how this pattern has helped to address the problem i.e. how can people confirm "did it work"?
• improving the visual e.g. by creating a new version digitally (so no scan), and explaining in the pattern what that visual illustrates

To even level the pattern up to Validated, we would have to find 2 more Known Instances of orgs using this pattern. As this might be hard to do, it could be achieved in multiple steps (and PRs) over time.

Start by reading patterns/2-structured/common-requirements.md and the contributor handbook section linked in the issue, then inspect assets/img/CommonReqtsv2.jpg. Break the work into the listed pattern, visual, and validation improvements; done means the selected changes are documented and the pattern has the required evidence, including two additional Known Instances if pursuing Validated status.