Typos

Froussios · Froussios · commit 9dfd57032c6a · 2015-05-19T00:57:05.000+02:00
diff --git a/Part 2 - Sequence Basics/2. Reducing a sequence.md b/Part 2 - Sequence Basics/2. Reducing a sequence.md
@@ -2,11 +2,11 @@
 
 The examples we've seen so far where all very small. Nothing should stop you from using Rx on a huge stream of realtime data, but what good would Rx be if it dumped the whole data onto you, and let you handle it like you would otherwise? Here we will explore operators that will filter out irrelevant data, or reduce the data to the single value that you want.
 
-As usual, most of the operators here will be familiar to anyone that has worked with Java's `Stream`s, or functional programming in general. All the operators here return a new observable and do _not_ affect the original observable. This principle is present throughout Rx. Transformations of observables create a new observable every time and leave the original remain unaffected. Subscribers to the original observable will notice no change.
+As usual, most of the operators here will be familiar to anyone that has worked with Java's `Stream`s, or functional programming in general. All the operators here return a new observable and do _not_ affect the original observable. This principle is present throughout Rx. Transformations of observables create a new observable every time and leave the original unaffected. Subscribers to the original observable should notice no change, but we will see in later chapters that guaranteeing this may require caution from the developer as well.
 
 ### Marble diagrams
 
-This is an appropriate time to introduce to concept of marble diagrams. It is a popular way of explaining the operators in Rx, because of their intuitive and graphical nature. They are present a lot in the documetation of RxJava and only makes sense that we take advantage of their explanatory nature. The format is mostly self-explanatory: time flows left to right, shapes represent values, a slash is a onCompletion, an X is an error. The operator is applied to the top sequence and results in the sequence below.
+This is an appropriate time to introduce to concept of marble diagrams. It is a popular way of explaining the operators in Rx, because of their intuitive and graphical nature. They are present a lot in the documetation of RxJava and it only makes sense that we take advantage of their explanatory nature. The format is mostly self-explanatory: time flows left to right, shapes represent values, a slash is a onCompletion, an X is an error. The operator is applied to the top sequence and the result is the sequence below.
 
 ![](https://raw.github.com/wiki/ReactiveX/RxJava/images/rx-operators/legend.png)
 
