Spelling corrections (#530)

* Typo: maintaining

* Typos: potentially, involve

* Typo: ad hoc

Author: rrrutledge

contributor/05-benefits-of-contribution-article.asciidoc

@@ -17,7 +17,7 @@ The most obvious motivation is what typically draws early contributors into open
 source as well.
 
 Remember that annoying bug you've been working around for so long? The time
-and energy that maintainting those workarounds costs? What if instead of waiting for
+and energy that maintaining those workarounds costs? What if instead of waiting for
 the upstream team to fix that issue sometime in the future, you could go ahead
 and fix it yourself? In this "scratch your own itch" situation first-time contributors
 often start with fixing issues in projects they depend on for their

introduction/07-faq.asciidoc

@@ -26,7 +26,7 @@ image::https://user-images.githubusercontent.com/9609562/151901209-52b3468b-dedd
 === Will we just be reviewing PRs all day every day?
 If so then your core team is understaffed. A healthy team is staffed so that there is time for assisting contributors and making core contributions yourself.
 
-You can mitigate this by setting expectation, potentialy via SLAs. If contributors expect PR reviews within an hour, maybe you will be stuck reviewing PRs all the time, but if you set an SLA of 1 day or 1 week, this won't be the case.
+You can mitigate this by setting expectation, potentially via SLAs. If contributors expect PR reviews within an hour, maybe you will be stuck reviewing PRs all the time, but if you set an SLA of 1 day or 1 week, this won't be the case.
 
 === How do we convince management this is a good idea?
 Figure out what they want and get a https://innersourcecommons.org/stories[working example of InnerSource], preferably within your organisation, that shows them getting it. If your organization's OSPO manages InnerSource projects, reach out to them for support.
@@ -41,7 +41,7 @@ InnerSource gives engineers the opportunity to develop their career, both in ter
 Also, many engineers value open source; InnerSource embraces open source practices, and can be a step towards open source for many projects.
 
 === What are the expectations on part of both host and contributor?
-Work together! This may be completely async via Pull Requests, or invovle regular community catchups - whatever works for you.
+Work together! This may be completely async via Pull Requests, or involve regular community catchups - whatever works for you.
 
 Communication and support must go in both directions and be open and collaborative, fostering a culture of psychological safety. Feedback on contributions, or existing code, must be approached with a growth mindset, and as partnership to make things better.
 

introduction/08-is-innersource-right.asciidoc

@@ -23,7 +23,7 @@ You will need to encourage and support contributions via activities such as:
 * Inviting users to make the contributions that they need and following up with them to ensure that they do them.
 * Maintaining an https://patterns.innersourcecommons.org/p/base-documentation#contributing.md[CONTRIBUTING.md] document that contains everything an engineer needs to know to contribute to the project.
 * Giving up-front guidance and direction as to how to implement a given contribution.
-* Being available during regular hours for any ad-hoc questions that contributors have.
+* Being available during regular hours for any ad hoc questions that contributors have.
 * Timely review of incoming pull requests.
 * Ongoing maintenance of submitted code (after the https://patterns.innersourcecommons.org/p/30-day-warranty[warranty window]).