Merge branch 'Doc' into 'master'

Fixed some spelling

See merge request !4

docs/idareplayobserver.rst

@@ -3,7 +3,7 @@ IDAReplayObserver
 
 .. class:: library.IDAReplayObserver
 
-   This is a class for following a replay. Se :ref:`Replays <replays>` for a example.
+   This is a class for following a replay.
 
    Inherited methods:
 

docs/index.rst

@@ -30,7 +30,7 @@ Table of contents
    constants
    replays
    idareplayobserver
-   replayuinit
+   replayunit
    
 .. autosummary::
    :toctree: _autosummary

docs/replays.rst

@@ -60,7 +60,7 @@ Here is a short example that uses SC2Reader to extract the build order.
 
 SC2Reader has good documation_ that also describe what information
 could be found. `What is in a Replay`_ and Events_ gives a good idea
-if the information you want could be colleced whithe SC2Reader.
+if the information you want could be collected with SC2Reader.
 
 .. _documation: https://sc2reader.readthedocs.io/en/latest/index.html
 .. _What is in a Replay: https://sc2reader.readthedocs.io/en/latest/articles/whatsinareplay.html
@@ -68,8 +68,8 @@ if the information you want could be colleced whithe SC2Reader.
 
 ReplayObserver
 --------------
-This is the second technique it is much like using a bot but whit the diffrens
-that no action can be preform just observations
+This is the second technique it is much like using a bot but whit the difference
+that no action can be preform just observations.
 
 
 .. code-block:: python

docs/replayunit.rst

@@ -4,7 +4,7 @@ ReplayUnit
 .. class:: library.ReplayUnit
 
    An instance of the class Unit represents one unit in a replay. A ReplayUnit is a
-   :class`library.Unit` white some limitations.
+   :class:`library.Unit` white some limitations.
 
    It is possible to use ReplayUnit as keys in a dictionary, which might be helpful
    for bookkeeping.