fix typos

See #6

docs/blinks.ipynb

@@ -71,7 +71,7 @@
     "- Second, blinks are defined as everything between two crossings of the velocity profile (from negative to positive).\n",
     "- Finally, detected blinks have to be at least `min_duration` duration (in customizable `units`).\n",
     "\n",
-    "As a consequence, there are several parameters that can be adjusted (see the [API-docs](/docs/api.rst) for details).\n",
+    "As a consequence, there are several parameters that can be adjusted (see the [API-docs](api.html) for details).\n",
     "The most important ones are the following:\n",
     "\n",
     "- `min_duration`: minimum duration for a sequence of missing numbers to be treated as blink\n",
@@ -121,7 +121,7 @@
    "source": [
     "We see that a period of seemingly valid pupil-data (around times 4.05 and 4.15 min) was marked as blink because of a sudden downward change in the pupil signal which might resemble the onset of a blink (a likely source of these artifacts are sudden eye-movements but we would need eyetracking-data to corrobate this hypothesis). \n",
     "\n",
-    "his problem can be fixed by setting a stricter value for the velocity-profile based onset detection `vel_onset` or requiring a more prolonged onset-transient by increasing `min_onset_len`:"
+    "This problem can be fixed by setting a stricter value for the velocity-profile based onset detection `vel_onset` or requiring a more prolonged onset-transient by increasing `min_onset_len`:"
    ]
   },
   {

docs/pipes.ipynb

@@ -94,7 +94,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "We see that sampling rate, number o datapoints and more is automatically printed along with the history of all operations applied to the dataset. This information can also be retrieved separately and in a form useful for further processing the function `summary()` which returns the information in the form of a `dict`:"
+    "We see that sampling rate, number of datapoints and more is automatically printed along with the history of all operations applied to the dataset. This information can also be retrieved separately and in a form useful for further processing the function `summary()` which returns the information in the form of a `dict`:"
    ]
   },
   {

docs/plotting.ipynb

@@ -6,7 +6,7 @@
    "source": [
     "# Plotting pupillometric data for exploration\n",
     "\n",
-    "It is crucial to validate preprocessing steps by visually inspecting the results using plots. Therefore, `pypillometry` implements several plotting facilities that encourage active exploration of the dataset. Some of the plotting functions require a Jupyter-notebook with enable widgets (see Installation instructions) so that the plots can be changed interactively, others are purely :mod:`matplotlib`-based."
+    "It is crucial to validate preprocessing steps by visually inspecting the results using plots. Therefore, `pypillometry` implements several plotting facilities that encourage active exploration of the dataset. Some of the plotting functions require a Jupyter-notebook with enable widgets (see Installation instructions) so that the plots can be changed interactively, others are purely `matplotlib`-based."
    ]
   },
   {

docs/summary.ipynb

@@ -22,7 +22,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "The `pypillometry` package provides several functions for summarizing datasets. Simply `print()`ing a :class:`PupilData` object gives a readable summary of the main properties of the dataset and also prints the complete history of operations applied to the dataset."
+    "The `pypillometry` package provides several functions for summarizing datasets. Simply `print()`ing a `PupilData` object gives a readable summary of the main properties of the dataset and also prints the complete history of operations applied to the dataset."
    ]
   },
   {