Merge pull request #1221 from magland/fix-typos

fix typos: "the the" -> "the"

docs/basics/101-136-filesystem.rst

@@ -119,7 +119,7 @@ only using Git tools only, outlined in the :find-out-more:`on faster renaming <f
 
    Git has built-in commands that provide a solution in two steps.
 
-   If you have followed along with the previous :dlcmd:`save`, let's revert the renaming of the the files:
+   If you have followed along with the previous :dlcmd:`save`, let's revert the renaming of the files:
 
    .. runrecord:: _examples/DL-101-136-105
       :language: console
@@ -278,7 +278,7 @@ the best option to turn to.
 
 .. index::
    pair: fix; git-annex command
-.. gitusernote:: 'datalad save' internals: 'git annex fix' 
+.. gitusernote:: 'datalad save' internals: 'git annex fix'
 
    A :dlcmd:`save` command internally uses a :gitcmd:`commit` to save changes to a dataset.
    :gitcmd:`commit` in turn triggers a :gitannexcmd:`fix`

docs/basics/101-138-sharethirdparty.rst

@@ -74,7 +74,7 @@ You have already done this in section :ref:`yoda_project` when you shared your `
 
 However, most Git repository hosting services do not support hosting the file content
 of the files managed by :term:`git-annex`.
-For example, the the results of the analysis in section :ref:`yoda_project`,
+For example, the results of the analysis in section :ref:`yoda_project`,
 ``pairwise_comparisons.png`` and ``prediction_report.csv``, were not published to
 GitHub: There was meta data about their file availability, but if a friend cloned
 this dataset and ran a :dlcmd:`get` command, content retrieval would fail

docs/beyond_basics/101-181-metalad.rst

@@ -178,7 +178,7 @@ The following call would add the metadata entry to the current dataset, ``cozy-s
 	But there are also some internal checks that might be surprising.
 	If you want to add the metadata above to your own dataset, you should make sure to adjust the ``dataset_id`` to the ID of your own dataset, found via the command ``datalad configuration get datalad.dataset.id`` - otherwise you'll see an error [#f4]_, and likewise the ``dataset_version``.
 	And in case you'd supply the ``extraction_time`` as "this morning at 8AM" instead of a time stamp, the command will be unhappy as well.
-	In case an error occurs, make sure to read the error message, and turn the the commands' ``--help`` for insights about requirements you might have missed.
+	In case an error occurs, make sure to read the error message, and turn the commands' ``--help`` for insights about requirements you might have missed.
 
 After the metadata has been added, you can view it via the command :dlcmd:`meta-dump`.
 The simplest form of this command is ``meta-dump -r``, which will show all metadata that is stored in the dataset in the current directory.