corrected typos

balking/README.md

@@ -23,5 +23,5 @@ Use the Balking pattern when
 but for an unknown amount of time
 
 ## Related patterns
-* Guarded Suspendion Pattern
+* Guarded Suspension Pattern
 * Double Checked Locking Pattern

event-queue/README.md

@@ -11,7 +11,7 @@ tags:
 ---
 
 ## Intent
-Event Queue is a good pattern if You have a limited accesibility resource (for example: 
+Event Queue is a good pattern if You have a limited accessibility resource (for example: 
 Audio or Database), but You need to handle all the requests that want to use that.
 It puts all the requests in a queue and process them asynchronously.
 Gives the resource for the event when it is the next in the queue and in same time
@@ -22,7 +22,7 @@ removes it from the queue.
 ## Applicability
 Use the Event Queue pattern when
 
-* You have a limited accesibility resource and the asynchronous process is acceptable to reach that
+* You have a limited accessibility resource and the asynchronous process is acceptable to reach that
 
 ## Credits
 

feature-toggle/README.md

@@ -22,7 +22,7 @@ going to phase out is never removed, causing redundant code smells and increased
 ![alt text](./etc/feature-toggle.png "Feature Toggle")
 
 ## Applicability
-Use the Feature Toogle pattern when
+Use the Feature Toggle pattern when
 
 * Giving different features to different users.
 * Rolling out a new feature incrementally.

layers/README.md

@@ -21,7 +21,7 @@ Layers is an architectural style where software responsibilities are
 ## Applicability
 Use the Layers architecture when
 
-* you want clearly divide software responsibilities into differents parts of the program
+* you want clearly divide software responsibilities into different parts of the program
 * you want to prevent a change from propagating throughout the application
 * you want to make your application more maintainable and testable
 

promise/README.md

@@ -27,7 +27,7 @@ in a synchronous way.
 Promise pattern is applicable in concurrent programming when some work needs to be done asynchronously
 and:
 
-* code maintainablity and readability suffers due to callback hell.
+* code maintainability and readability suffers due to callback hell.
 * you need to compose promises and need better error handling for asynchronous tasks.
 * you want to use functional style of programming.
 
@@ -44,4 +44,4 @@ and:
 ## Credits
 
 * [You are missing the point to Promises](https://gist.github.com/domenic/3889970)
-* [Functional style callbacks using CompleteableFuture](https://www.infoq.com/articles/Functional-Style-Callbacks-Using-CompletableFuture)
+* [Functional style callbacks using CompletableFuture](https://www.infoq.com/articles/Functional-Style-Callbacks-Using-CompletableFuture)

prototype/README.md

@@ -36,7 +36,7 @@ In Java, it can be easily done by implementing `Cloneable` and overriding `clone
 
 ```
 class Sheep implements Cloneable {
-  privage String name;
+  private String name;
   public Sheep(String name) { this.name = name; }
   public void setName(String name) { this.name = name; }
   public String getName() { return name; }

tls/README.md

@@ -19,4 +19,4 @@ Securing variables global to a thread against being spoiled by other threads. Th
 Use the Thread Local Storage in any of the following situations
 
 * when you use class variables in your Callable / Runnable object that are not read-only and you use the same Callable instance in more than one thread running in parallel.
-* when you use static variables in your Callable / Runnable object that are not read-only and more than one instances of the Callable / Runnalbe may run in parallel threads.
+* when you use static variables in your Callable / Runnable object that are not read-only and more than one instances of the Callable / Runnable may run in parallel threads.