Update 1. Side effects.md

Tiltman · Tiltman · commit e2ce0f69ddf8 · 2015-07-21T17:33:47.000+02:00
diff --git a/Part 3 - Taming the sequence/1. Side effects.md b/Part 3 - Taming the sequence/1. Side effects.md
@@ -4,7 +4,7 @@ So far we've learned how to create observables and how to extract relevant data
 
 # Side effects
 
-Functions without side-effects interact with the rest of the program exclusively through their arguments and return values. When the operations within a function can affect the outcome of another function (or a subsequent call to the same function), we say that the function has side effects. Common side effects are writes to storage, logging, debugging or prints to a user interface. A more language-dependent form of side effect is the ability to modify the state of an object that is visibible to other functions, which is something that Java considers legal. A function passed as an argument to an Rx operator can modify values in a wider scope, perform IO operations or update a display.
+Functions without side-effects interact with the rest of the program exclusively through their arguments and return values. When the operations within a function can affect the outcome of another function (or a subsequent call to the same function), we say that the function has side effects. Common side effects are writes to storage, logging, debugging or prints to a user interface. A more language-dependent form of side effect is the ability to modify the state of an object that is visible to other functions, which is something that Java considers legal. A function passed as an argument to an Rx operator can modify values in a wider scope, perform IO operations or update a display.
 
 Side effects can be very useful and are unavoidable in many cases. But they also have pitfalls. Rx developers are encouraged to avoid unnecessary side effects, and to have a clear intention when they do use them. While some cases are justified, abuse introduces unnecessary hazards.
 
@@ -114,7 +114,7 @@ indexed.subscribe(w -> System.out.println("2nd observer: " + w.index + ": " + w.
 2nd observer: 4: please
 ```
 
-The result now is valid. We removed the shared state between the two subscriptions and now they can't affect eachother.
+The result now is valid. We removed the shared state between the two subscriptions and now they can't affect each other.
 
 ## do
 
