Merge pull request coffeescript-cookbook#88 from nepsilon/adapter-pattern-typos

Anglicize and fix typos for the Adapter design pattern page.

Author: peterhellberg

chapters/design_patterns/adapter.md

@@ -1,13 +1,16 @@
 ---
 layout: recipe
-title: Adapter patter
+title: Adapter pattern
 chapter: Design patterns
 ---
 ## Problem
 
-Suppose we have 3-rd party grid component. We want to apply there our own custom sorting but a small problem. Our custom sorter does not implement required interface by grid component.
-To understand the problem completely best example would be an socket from our usual life. Everybody knows this device. In some countries it has 3 pins and in other contries it has only 2 pins. 
-This is exactly right situation to use [adapter pattern](https://en.wikipedia.org/wiki/Adapter_pattern). 
+Imagine you are traveling to a foreign country and once at your hotel room you realize your power cord socket is not compatible with the wall socket.
+Luckily, you remembered you've brought your power adapter with you.
+It will connect your power cord socket on one side and wall socket on the other side, allowing for communication between them.
+
+The same situation may arise in code, when 2 (or more) instances (of classes, modules, etc.) want to talk to each other, but whose communication protocol (e.i. the language they use to communicate) is different from each other.
+In such a situation, the [Adapter Pattern](//en.wikipedia.org/wiki/Adapter_pattern) comes in handy. It will do the translation, from one side to the other.
 
 ## Solution
 
@@ -47,5 +50,5 @@ agrid.sort() # sort data with custom sorter through adapter
 
 ## Discussion
 
-Adapter is usefull when you have to organize an interaction between two objects with different interfaces. It can happen when you use 3-rd party libraries  or you work with legacy code. 
-In any case be carefull with adapter: it can be helpfull but it can instigate design errors. 
+Adapter is useful when you have to organize an interaction between two objects with different interfaces. It can happen when you use 3rd party libraries  or you work with legacy code. 
+In any case be careful with adapter: it can be helpful but it can instigate design errors.