spell check

3-meetings.md

@@ -19,7 +19,7 @@ Things you can discuss on a meeting:
 
 ## How do I schedule a meeting?
 
-Any member can shedule a meeting.
+Any member can schedule a meeting.
 
 1. Create a pad for the meeting topics and the meeting notes.
 2. Pick a date (preferably not during the social evening).
@@ -64,7 +64,7 @@ More important information from the statutes.
 
 Most decisions don't require a rigid structure but we need a rigid structure to fall back on when there is extreme conflict that divides the space or when people don't agree on how a decision is made. In such cases, a consensus-based system is used in order to re-unite the space.
 
-In short; the topic needs to be put on the agenda three days the first meeting. During the first meeting, a decision needs 100% consensus. If no decision is made, a second meeting is sheduled where a decision on a topic only requires 80% consensus, so a decision is made when 20% or less members object. If no decision is made, a third meeting is sheduled where a decision is made using the "point system", an over-complicated system where a decision will always be made.
+In short; the topic needs to be put on the agenda three days the first meeting. During the first meeting, a decision needs 100% consensus. If no decision is made, a second meeting is scheduled where a decision on a topic only requires 80% consensus, so a decision is made when 20% or less members object. If no decision is made, a third meeting is scheduled where a decision is made using the "point system", an over-complicated system where a decision will always be made.
 
 | PLAN/TIME                       | ACTION                                                      | DECISION       |
 | ------------------------------- |:-----------------------------------------------------------:| --------------:|
@@ -104,7 +104,7 @@ The point system is a **last-resort** option. This should not be the general pro
 
 * Each voter has a certain number of points that he can distribute over the different proposals.
 * The proposal with the most points wins.
-* In case of tie; revote.
+* In case of tie; re-vote.
 * **Number of points per voter  =** `(#_of_options * 2 ) + 1`
 * Results should be given to the group in binary format: what proposal won and what lost. This is to strengthen the support of the decision.
 

4-the-board.md

@@ -4,7 +4,7 @@ The board exists to make sure the hacker environment survives. The board members
 
 Specifically, the board has two roles, and for everything that doesn't fall into these roles, the board members are regarded as regular members.
 
-1. *Warden of the physical core infrastructure of the space.* This stems from [the infrastructure pattern](https://wiki.hackerspaces.org/The_Infrastructure_Pattern). Provide a room with power, internet, a bar and [a kitchen](https://wiki.hackerspaces.org/The_Kitchen_Pattern) and the hackers will come. An important aspect of this is keeping a good relationship with the surroundings as said in [the landlord and neighbourhood pattern](https://wiki.hackerspaces.org/The_Landlord_and_Neighbourhood_Pattern).
+1. *Warden of the physical core infrastructure of the space.* This stems from [the infrastructure pattern](https://wiki.hackerspaces.org/The_Infrastructure_Pattern). Provide a room with power, internet, a bar and [a kitchen](https://wiki.hackerspaces.org/The_Kitchen_Pattern) and the hackers will come. An important aspect of this is keeping a good relationship with the surroundings as said in [the landlord and neighborhood pattern](https://wiki.hackerspaces.org/The_Landlord_and_Neighbourhood_Pattern).
 2. *Counselor for the people in the space.* When conflict happens that can't be resolved in the group, the board is responsible for resolving the conflict. A great way to do this is [the private talk pattern](https://wiki.hackerspaces.org/The_Private_Talk_Pattern): go talk to the involved parties in private, listen to the person and let them know how the group feels.
 
 It's important for the board to communicate openly about what they do.

README.md

@@ -23,6 +23,6 @@ The main system running the Hackerspace is **the do-ocracy**, explained further
 
 However, when you want to do something that affect a lot of people in the space, or when you want to make sure that people will support what you want to do, discuss it with the other members on a **meeting** as explained in Section 3.
 
-Every organisation has a number of unspoken guidelines of how you should behave, we have written down some of ours in Section 6 in order to make it easier for people to get a sense of what to do in certain situations. These **guidelines** are not meant to be strict rules, but they give an overview of what is good and bad behavior in the space.
+Every organization has a number of unspoken guidelines of how you should behave, we have written down some of ours in Section 6 in order to make it easier for people to get a sense of what to do in certain situations. These **guidelines** are not meant to be strict rules, but they give an overview of what is good and bad behavior in the space.
 
 Because every good idea that was once written down has been misinterpreted, we included information that led us to the system and the guidelines. We call it **the legacy**. It is a collection of information that we used to create Hack the Hackerspace, it gives more context to why the system is the way it is. The legacy should by used as a "cipher" to interpret the system and the guidelines correctly and to explain a bit of the rationale behind them.