Adding some elements to explain the structure of the Solution section in more detail

Author: spier

patterns/1-initial/governance-based-project-setup.md

@@ -28,23 +28,29 @@ A team has decided that they want to publish an InnerSource project. They are tr
 
 Support new Trusted Committers with a list of resources targeted at each of the three governance levels.
 
-### Governance Level: "Bug reports and Issues welcome"
+This solution ties together various resources that are provided by the InnerSource Commons:
+- the [maturity model](../2-structured/maturity-model.md)
+- InnerSource Patterns applicable to each level
+
+Your organization may have other custom resources relevant for each of these governance levels, that you could link to in addition to the above.
+
+### Governance Level: "Bug Reports and Issues Welcome"
 
 Definition:
 > People outside the core development team may use the code. They can submit feature requests and bug reports for things they would like to see changed.
 
-Ideally the host team goes through the [InnerSource Learning Path](https://innersourcecommons.org/learn/learning-path/) to get a first understanding of the concepts and roles involved.
-
 To reach this level, a team needs to make their source code readable. They need to give write access to their issue tracker.
 
-For the [maturity model](../2-structured/maturity-model.md), the relevant levels needed are at least:
+Ideally the host team goes through the [InnerSource Learning Path](https://innersourcecommons.org/learn/learning-path/) to get a first understanding of the concepts and roles involved.
+
+The relevant levels of the [maturity model](../2-structured/maturity-model.md) are at least:
 
 PP-1, DP-1, DC-1, RS-1, ST-1, CF-1, LS-1, OF-2, CB-2, SP-2, PA-2, RW-1, MP-1, SM-1, CL-1, RO-1
 
-For InnerSource patterns, start by looking at the following ones:
+These InnerSource patterns, start by looking at the following ones:
 
 * [Base Documentation](../2-structured/base-documentation.md)
-* [Communiation Tooling](../2-structured/communication-tooling.md)
+* [Communication Tooling](../2-structured/communication-tooling.md)
 * [Issue Tracker](../2-structured/issue-tracker.md)
 * [Praise Participants](../2-structured/praise-participants.md)
 * [Standard Release Process](../2-structured/release-process.md)
@@ -58,7 +64,7 @@ Definition:
 
 To reach this level, a team needs to give contributors the option to submit pull requests. In addition, contributors need to have clear options to follow the development of the project in order to better understand project direction and established best practices. In addition the host team needs to set aside time for mentoring contributors and giving timely feedback.
 
-For the [maturity model](../2-structured/maturity-model.md), the relevant levels needed are at least:
+The relevant levels of the [maturity model](../2-structured/maturity-model.md) are at least:
 
 PP-2, DP-2, DC-2, RS-3, ST-3, CF-2, LS-2, OF-2, CB-2, SP-2, PA-2, RW-2, MP-2, SM-2, CL-3, RO-2
 
@@ -83,7 +89,7 @@ To reach this level the host team, mixed of members of different teams in the or
 
 All project decisions need to be taken where they can not only be seen by others but influenced by the entire team of Trusted Committers - even if not everybody can make it to all meetings.
 
-For the [maturity model](../2-structured/maturity-model.md), the relevant levels needed are at least:
+The relevant levels of the [maturity model](../2-structured/maturity-model.md) are at least:
 
 PP-3, DP-3, DC-3, RS-3, ST-3, CF-3, LS-3, OF-3, CB-3, SP-3, PS-3, RW-3, MP-3, SM-3, CL-3, RO-3