Skip to content
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

Fix two minor typos #775

Merged
merged 3 commits into from
Oct 28, 2021
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
2 changes: 1 addition & 1 deletion docs/basics/101-115-symlinks.rst
Original file line number Diff line number Diff line change
Expand Up @@ -186,7 +186,7 @@ This leads to a few conclusions:

The first is that you should not be worried
to see cryptic looking symlinks in your repository -- this is how it should look.
You can read the :find-out-more:` on why these paths look so weird <fom-objecttree>` and what all of this has to do with data integrity, if you want to.
You can read the :ref:`find-out-more on why these paths look so weird <fom-objecttree>` and what all of this has to do with data integrity, if you want to.
Its additional information that can help to establish trust in that your data are safely stored and tracked, and understanding more about the object tree and knowing bits of the git-annex basics can make you more confident in working with your datasets.

The second is that it should now be clear to you why the ``.git`` directory
Expand Down
2 changes: 1 addition & 1 deletion docs/basics/101-122-config.rst
Original file line number Diff line number Diff line change
Expand Up @@ -318,7 +318,7 @@ the dataset, these configurations will also be shared together with the dataset.
``.git/config``, however, behaves just as your global or system-wide configurations.
These configurations are in effect on a system, or for a user, or for a dataset,
but are not shared.
A :command:`datalad clone` command of someone's dataset will not get your their
A :command:`datalad clone` command of someone's dataset will not get your
editor configuration, should they have included one in their config file.
Instead, upon a :command:`datalad clone`, a new config file will be created.

Expand Down