Skip to content

Commit

Permalink
Merge pull request #1235 from matrss/patch-2
Browse files Browse the repository at this point in the history
Fixes for minor things I noticed while reading the handbook
  • Loading branch information
adswa authored Sep 9, 2024
2 parents 90783d8 + 8e29af1 commit 38b4d13
Show file tree
Hide file tree
Showing 3 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion docs/basics/101-101-create.rst
Original file line number Diff line number Diff line change
Expand Up @@ -82,7 +82,7 @@ However, all files and directories you store within the DataLad dataset
can be tracked (should you want them to be tracked).
*Tracking* in this context means that edits done to a file are automatically
associated with information about the change, the author of the edit,
and the time of this change. This is already informative important on its own
and the time of this change. This is already important information on its own
-- the :term:`provenance` captured with this can, for example, be used to learn
about a file's lineage, and can establish trust in it.
But what is especially helpful is that previous states of files or directories
Expand Down
4 changes: 2 additions & 2 deletions docs/basics/101-105-install.rst
Original file line number Diff line number Diff line change
Expand Up @@ -334,7 +334,7 @@ really helpful to save disk space for data you can easily reobtain, for example"
The :dlcmd:`drop` command will remove
file contents completely from your dataset.
You should only use this command to remove contents that you can :dlcmd:`get`
again, or generate again (for example, with next chapter's :dlcmd:`datalad run`
again, or generate again (for example, with next chapter's :dlcmd:`run`
command), or that you really do not need anymore.

Let's remove the content of one of the files that we have downloaded, and check
Expand Down Expand Up @@ -379,7 +379,7 @@ This was only a quick digression into :dlcmd:`drop`. The main principles
of this command will become clear after chapter
:ref:`chapter_gitannex`, and its precise use is shown in the paragraph on
:ref:`removing file contents <remove>`.
At this point, however, you already know that datasets allow you do
At this point, however, you already know that datasets allow you to
:dlcmd:`drop` file contents flexibly. If you want to, you could have more
podcasts (or other data) on your computer than you have disk space available
by using DataLad datasets -- and that really is a cool feature to have.
Expand Down
2 changes: 1 addition & 1 deletion docs/basics/101-110-run2.rst
Original file line number Diff line number Diff line change
Expand Up @@ -137,7 +137,7 @@ prior to running the command.
"convert -resize 400x400 recordings/longnow/.datalad/feed_metadata/logo_salt.jpg recordings/salt_logo_small.jpg"


Cool! You can see in this output that prior to the data command execution, DataLad did a :dlcmd:`get`.
Cool! You can see in this output that prior to the command execution, DataLad did a :dlcmd:`get`.
This is useful for several reasons. For one, it saved us the work of manually
getting content. But moreover, this is useful for anyone with whom we might share the
dataset: With an installed dataset one can very simply rerun :dlcmd:`run` commands
Expand Down

0 comments on commit 38b4d13

Please sign in to comment.