Skip to content

fix typos: "the the" -> "the" #1221

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 8, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/basics/101-136-filesystem.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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`
Expand Down
2 changes: 1 addition & 1 deletion docs/basics/101-138-sharethirdparty.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion docs/beyond_basics/101-181-metalad.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
Loading