Various typos and a double space

30-day-warranty.md

@@ -4,7 +4,7 @@
 
 # Context
 
-Teams depends on another team accepting their contributions so that a component produced by the receiving team can be used by the contributing team. The receiving team does not have the resources, knowledge, permission, inclination to write the contributed component.
+Teams depend on another team accepting their contributions so that a component produced by the receiving team can be used by the contributing team. The receiving team does not have the resources, knowledge, permission, and/or inclination to write the contributed component.
 
 - TBD: link to pattern "setting clear expectations for contributing code"
 

contracted-contributor.md

@@ -36,7 +36,7 @@ hours, not during free time.
 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
-management. This will likely be ampflified if there is no adequate funding for
+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.
 
@@ -68,7 +68,7 @@ This runs the risk of top level management abandoning the InnerSource idea.
 
 ## Solution
 
-Set up a formal contracting between the contributor, her line manager and a
+Set up a formal contracting between the contributor, their line manager and a
 centrally funded and steered InnerSource governance office (ISGO). Have the
 ISGO reimburse business units who contracted contributors for the contracted
 time. 

dedicated-community-leader.md

@@ -15,7 +15,7 @@ Selecting the wrong persons and/or not providing enough capacity for them risks
 
 ## Story
 
-Consider the following story. A company wants to start an InnerSource initiative in order to foster collaboration across organizational boundaries. They have decided to start with an experimental phase with limited scope. Management has selected a suitable pilot topic for the first InnerSource community and expects contributions from many business units across the organization. The company has nominated a new hire to head the community for 50 % of his work time, because he was not yet 100 % planned for. After 6 months, the community has received only a few contributions, most of which are from a single business unit. The company replaces the community leader with someone who has a longer history in the company, this time for only 30 % of his time. After another 6 months, the number of contributions has picked up only  marginally. The company is no longer convinced that InnerSource helps to achieve their goal of increased, cross divisional collaboration and abandons InnerSource. 
+Consider the following story. A company wants to start an InnerSource initiative in order to foster collaboration across organizational boundaries. They have decided to start with an experimental phase with limited scope. Management has selected a suitable pilot topic for the first InnerSource community and expects contributions from many business units across the organization. The company has nominated a new hire to head the community for 50 % of his work time, because he was not yet 100 % planned for. After 6 months, the community has received only a few contributions, most of which are from a single business unit. The company replaces the community leader with someone who has a longer history in the company, this time for only 30 % of his time. After another 6 months, the number of contributions has picked up only marginally. The company is no longer convinced that InnerSource helps to achieve their goal of increased, cross divisional collaboration and abandons InnerSource. 
 
 ## Context
 

service-vs-library.md

@@ -66,12 +66,12 @@ Both teams get to know their respective escalation policy and deployment setup,
 potentially identifying improvements for their own setup.
 
 The likelihood that changes are needed and made in the shared source code
-increases, leading to more frequent oportunities to refine, improve and optimise
+increases, leading to more frequent opportunities to refine, improve and optimise
 the implementation.
 
 ## See also
 
-Related to this pattern is the [Thirty day warrenty](https://github.com/paypal/InnerSourcePatterns/blob/master/30-day-warranty.md) pattern that takes a different approach to solving the forces described above.
+Related to this pattern is the [Thirty day warranty](https://github.com/paypal/InnerSourcePatterns/blob/master/30-day-warranty.md) pattern that takes a different approach to solving the forces described above.
 
 ## Known instances