From 12a17cb8d395f525b5fe33b070d4eca4810abf6e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Matthias=20Ri=C3=9Fe?= <9308656+matrss@users.noreply.github.com> Date: Fri, 6 Sep 2024 15:52:10 +0200 Subject: [PATCH 1/4] Update 101-101-create.rst --- docs/basics/101-101-create.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/basics/101-101-create.rst b/docs/basics/101-101-create.rst index 2d7a7baff..46a37de6c 100644 --- a/docs/basics/101-101-create.rst +++ b/docs/basics/101-101-create.rst @@ -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 From e00d8bd5f10899583a594919bf2e7b075d230e24 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Matthias=20Ri=C3=9Fe?= <9308656+matrss@users.noreply.github.com> Date: Fri, 6 Sep 2024 15:55:13 +0200 Subject: [PATCH 2/4] Update 101-105-install.rst --- docs/basics/101-105-install.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/basics/101-105-install.rst b/docs/basics/101-105-install.rst index ad35afa9a..9dff3ea8b 100644 --- a/docs/basics/101-105-install.rst +++ b/docs/basics/101-105-install.rst @@ -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 From 173e93392258d2f536adfe64e0d51eb28f5a9487 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Matthias=20Ri=C3=9Fe?= <9308656+matrss@users.noreply.github.com> Date: Fri, 6 Sep 2024 15:58:14 +0200 Subject: [PATCH 3/4] Update 101-105-install.rst --- docs/basics/101-105-install.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/basics/101-105-install.rst b/docs/basics/101-105-install.rst index 9dff3ea8b..de6a2fb66 100644 --- a/docs/basics/101-105-install.rst +++ b/docs/basics/101-105-install.rst @@ -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 `. -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. From 8e29af1863bd84b3e746f7c0c18c4d40d94e876b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Matthias=20Ri=C3=9Fe?= <9308656+matrss@users.noreply.github.com> Date: Fri, 6 Sep 2024 15:59:45 +0200 Subject: [PATCH 4/4] Update 101-110-run2.rst --- docs/basics/101-110-run2.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/basics/101-110-run2.rst b/docs/basics/101-110-run2.rst index 4f4c130d6..113b541c6 100644 --- a/docs/basics/101-110-run2.rst +++ b/docs/basics/101-110-run2.rst @@ -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