Fixing Typos (#2)

docs/guidelines/doors.md

@@ -14,7 +14,7 @@ matter since switching this technology is relatively simple in the overall schem
 
 ## One-Way Doors
 
-A one-way door is a decision that is difficult to reverse. This is a sitaution where when you walk through the door,
+A one-way door is a decision that is difficult to reverse. This is a situation where when you walk through the door,
 the door is closed behind you and you can't easily open it or go back through it the other way. An example would be
 selecting the framework that the application runs on.
 
@@ -23,19 +23,19 @@ can with the information we have.
 
 ## How to apply this guideline
 
-Two-way door questions should be decided on a "best answer at the time" or a "compeitition of ideas". This means that
+Two-way door questions should be decided on a "best answer at the time" or a "competition of ideas". This means that
 if there is disagreement on a particular way forward, the team should spend a small amount of time discussing it, or
 even implement a POC of both solutions and then decide quickly which one to adopt based on their knowledge and
 experience.
 
 For two-way door questions, the person who is successful in their approach should never gloat and the person who is not
-successful should never take it personally. No decision made in a two-way door scenario is irreversable. If a person
+successful should never take it personally. No decision made in a two-way door scenario is irreversible. If a person
 who does not win their preferred solution feels later on that their solution might address a problem faced by the team,
 they should raise it again politely. The team should reconsider. While the decision may not be changed, the discussion
 is important.
 
-One-way door questions are an opportunity for discussion and a time-out. If a decision is effectively irreversable, or
-changing it is so difficult that it's essentially irreversable, the team needs to be certain that it's the best decision
+One-way door questions are an opportunity for discussion and a time-out. If a decision is effectively irreversible, or
+changing it is so difficult that it's essentially irreversible, the team needs to be certain that it's the best decision
 they can make *at the time*.
 
 ## Passionate debate, polite disagreement
@@ -46,5 +46,5 @@ of one's ideas is perfectly acceptable, but also, we must disagree politely.
 Debate the *merits* of a solution, not the *qualities* of the person proposing it. Don't engage in ad hominem or other
 types of personal attacks. 
 
-Where possible, reach consensus. When consensus is not possible, it is the responsibiltiy of the team lead to make a
+Where possible, reach consensus. When consensus is not possible, it is the responsibility of the team lead to make a
 final decision. Once a final decision is reached the team should embrace it, and move forward with it.

docs/guidelines/index.md

@@ -6,7 +6,7 @@ permalink: /guidelines/
 
 The AspirePress guidelines are just that - guidelines.
 
-They are not rules, they are not policies, they are not enforcable and they are not set in stone.
+They are not rules, they are not policies, they are not enforceable and they are not set in stone.
 
 They are intended to guide our implementation of the project in the best way possible through general consensus, but
 they do not provide a set of hard-and-fast rules that inform every decision we have to make. Some situations won't be

docs/index.md

@@ -23,14 +23,14 @@ This site contains three sections:
    followed* as a matter of course. Breaking these policies can be grounds for discipline or removal from the project.
 
 **In general** our goal is to have more guidelines and core principles than actual policies. A policy exists where no
-alternative was available. We implement polciies to resolve conflicts or issues that cannot be resolved through less
+alternative was available. We implement policies to resolve conflicts or issues that cannot be resolved through less
 restrictive means. Policies carry the force of official rules in this project, while guidelines and core principles are
-signposts tha guide our behavior and decision-making without fully constricting it.
+signposts that guide our behavior and decision-making without fully constricting it.
 
 ## Code of Conduct
 
 AspirePress also implements a [Code of Conduct](https://github.com/aspirepress/.github/blob/main/CODE_OF_CONDUCT.md),
-adherance to which is required by all members of the project.
+adherence to which is required by all members of the project.
 
 ## Credits
 

docs/policies/index.md

@@ -39,7 +39,7 @@ The following governs how a policy is written and published as a policy in Aspir
    make comments on the proposed change. If the change is an emergency change this time period may be limited to 5 days.
 3. The Executive Board of AspirePress will meet to discuss the policy. They may take action on the policy in one of four
    ways: they may reject the policy, they may approve the policy, they may request changes to the policy, and they may
-   request a vote of the entire membership on the policy. This vote may be binding or non-binding at teh discretion of
+   request a vote of the entire membership on the policy. This vote may be binding or non-binding at the discretion of
    the Executive Committee.
 4. Upon acceptance of a policy, the policy is merged into `main` as Ratified and becomes official policy of AspirePress.