Contracted contributor

book/toc.md

@@ -27,7 +27,7 @@ Instead edit toc_template.md
 * [InnerSource Portal](../patterns/2-structured/innersource-portal.md) - Create an intranet website that indexes all available InnerSource project information. This will enable potential contributors to more easily learn about projects that might interest them and for InnerSource project owners to attract an outside audience.
 * [Issue Tracker Use Cases](../patterns/2-structured/project-setup/issue-tracker.md) - The InnerSource host team fails to make not only plans and progress but also context for changes transparent. This is solved by increasing the use cases for the project issue tracker to also serve brainstorming, implementation discussion, and feature design.
 * [Maturity Model](../patterns/2-structured/maturity-model.md) - Teams have started adopting InnerSource. The practice is spreading to multiple departments. Understanding of what constitutes an InnerSource project are wide spread though. The solution is to provide a maturity model to allow for teams to go through a self check and discover patterns and practices that they are not yet aware of.
-* [Praise Participants](../patterns/2-structured/praise-participants.md) - After an inner source contribution, it's important to thank the contributor for their time and effort. This pattern gives guidance that not only effectively acknowledges the contribution but also endgenders further engagement from the contributor and others.
+* [Praise Participants](../patterns/2-structured/praise-participants.md) - After an inner source contribution, it's important to thank the contributor for their time and effort. This pattern gives guidance that not only effectively acknowledges the contribution but also engenders further engagement from the contributor and others.
 * [Repository Activity Score](../patterns/2-structured/repository-activity-score.md) - Potential contributors want to find active InnerSource projects in need of their help. By calculating a repository activity score for each project, a ranked list of projects can be created (e.g. on the InnerSource portal), so that potential contributors can more easily determine which project they want to contribute to.
 * [Review Committee](../patterns/2-structured/review-committee.md) - The InnerSource working model is a radical departure from more traditional approaches, for developers and managers alike. By establishing a review committee as an interface between the InnerSource initiative and all senior managers of business units participating in it, the latter are more likely to familiarise themselves with the initiative and support it, as it affords them a certain level of oversight and control without fostering micromanagement.
 * [Service vs. Library](../patterns/2-structured/service-vs-library.md) - Teams in a DevOps environment may be reluctant to work across team boundaries on common code bases due to ambiguity over who will be responsible for responding to service downtime. The solution is to realize that often it's possible to either deploy the same service in independent environments with separate escalation chains in the event of service downtime or factor a lot of shared code out into one library and collaborate on that.

patterns/2-structured/contracted-contributor.md

@@ -10,15 +10,15 @@ Associates wanting to contribute to InnerSource are discouraged from doing so by
 
 Without support by middle management, the total number of contributors and, as
 a result, the amount of contributions made and value generated by the
-InnerSource initiative will likely fall below expectation of top level
+InnerSource initiative will likely fall below expectation of top-level
 management. This will likely be amplified if there is no adequate funding for
 and empowerment of [Dedicated Community Leaders](dedicated-community-leader.md).
-This runs the risk of top level management abandoning the InnerSource idea.
+This runs the risk of top-level management abandoning the InnerSource idea.
 
 ## Context
 
 A large corporation has started an InnerSource initiative. Major goals for the
-initiative are to increase the efficiency of distributed software develoment
+initiative are to increase the efficiency of distributed software development
 and to foster innovation by allowing every associate to voluntarily
 contribute to InnerSource projects, regardless of topic and business unit.
 
@@ -27,12 +27,12 @@ them, the InnerSource initiative is just one of many initiatives to foster
 innovation and efficiency, though. They are funding InnerSource with money and
 capacity for community leaders and are largely giving autonomy as for how the
 budget is spent. They are also limiting the breadth and duration of the
-initiative and partake in periodic reviews until there is proof that it yields
+initiative and partake in periodic reviews until there is proof it yields
 the expected results (see [Review Committee](review-committee.md)).  Top level
 management has announced their support for InnerSource on various company
 internal meetings.
 
-However, top level management has not yet empowered or incentivised mid-level
+However, top-level management has not yet empowered or incentivised mid-level
 managers to allow or even motivate their employees to participate in
 cross-divisional InnerSource activities. In addition to that, the capacity of
 every associate is usually allocated to non InnerSource projects for 100 % of
@@ -64,7 +64,7 @@ hours, not during free time.
   his teammates in his business unit increase.
 - Individual contributors will likely consider participating in InnerSource
   as an opportunity to enhance their professional network within the company
-  and to gain knowledege and experience in the technical area of her
+  and to gain knowledge and experience in the technical area of her
   contributions.
 
 ## Solution
@@ -77,7 +77,7 @@ time.
 - The contracting specifies a maximum percentage of the associates work time in
   InnerSource.
 - The contracting clearly states that work in the contributor's business unit
-  takes precendence over work in InnerSource.
+  takes precedence over work in InnerSource.
 - The contracting states that it is not required to work in InnerSource for the
   maximum percentage specified in the contract.
 - The contracting is signed by the contributor, the contributor's line manager,
@@ -111,11 +111,11 @@ empowering middle management to sign off on it:
 
 A formal contracting is also beneficial for contributors and communities:
 
-- With a stable group of contributors, it is more likely that some of them will
+- With a stable group of contributors, it is more likely some of them will
   eventually achieve [Trusted Committer](./trusted-committer.md) status.
 - A formal contracting provides a basis for resolving conflict related to
   participation in InnerSource activities. Note that mediation will likely be
-  successful only for a few companies with a culture condusive to that.
+  successful only for a few companies with a culture conducive to that.
 
 ## Known Instances