Skip to content

Commit

Permalink
turn refs to findoutmores into :find-out-more: refs in the Basics
Browse files Browse the repository at this point in the history
  • Loading branch information
adswa committed Nov 14, 2023
1 parent 61f74c7 commit 290503b
Show file tree
Hide file tree
Showing 4 changed files with 7 additions and 7 deletions.
8 changes: 4 additions & 4 deletions docs/basics/101-130-yodaproject.rst
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ In principle, you can prepare YODA-compliant data analyses in any programming
language of your choice. But because you are already familiar with
the `Python <https://www.python.org>`__ programming language, you decide
to script your analysis in Python. Delighted, you find out that there is even
a Python API for DataLad's functionality that you can read about in :ref:`a Findoutmore on DataLad in Python<fom-pythonapi>`.
a Python API for DataLad's functionality that you can read about in a :find-out-more:`on DataLad in Python<fom-pythonapi>`.

.. _pythonapi:
.. index::
Expand Down Expand Up @@ -187,7 +187,7 @@ For the purpose of this analysis, the DataLad handbook provides an ``iris_data``
dataset at `https://github.com/datalad-handbook/iris_data <https://github.com/datalad-handbook/iris_data>`_.

You can either use this provided input dataset, or find out how to create an
independent dataset from scratch in a :ref:`dedicated Findoutmore <fom-iris>`.
independent dataset from scratch in a dedicated :find-out-more:`on this topic <fom-iris>`.

.. index::
pair: create and publish dataset as dependency; with DataLad
Expand Down Expand Up @@ -769,7 +769,7 @@ command.
proportion of the previous handbook content as a prerequisite. In order to be
not too overwhelmingly detailed, the upcoming sections will approach
:dlcmd:`push` from a "learning-by-doing" perspective:
First, you will see a :dlcmd:`push` to GitHub, and the :ref:`Findoutmore on the published dataset <fom-midtermclone>`
First, you will see a :dlcmd:`push` to GitHub, and the :find-out-more:`on the published dataset <fom-midtermclone>`
at the end of this section will already give a practical glimpse into the
difference between annexed contents and contents stored in Git when pushed
to GitHub. The chapter :ref:`chapter_thirdparty` will extend on this,
Expand Down Expand Up @@ -837,7 +837,7 @@ an additional :gitcmd:`push` with the ``--tags`` option is required:
Yay! Consider your midterm project submitted! Others can now install your
dataset and check out your data science project -- and even better: they can
reproduce your data science project easily from scratch (take a look into the :ref:`Findoutmore <fom-midtermclone>` to see how)!
reproduce your data science project easily from scratch (take a look into the :find-out-more:`on the published dataset <fom-midtermclone>` to see how)!

.. index::
pair: work on published YODA dataset; with DataLad
Expand Down
2 changes: 1 addition & 1 deletion docs/basics/101-132-advancednesting.rst
Original file line number Diff line number Diff line change
Expand Up @@ -113,7 +113,7 @@ the ``midterm_project`` dataset, and your dataset's status is clean again.

This time in DataLad-101 is a convenient moment to dive a bit deeper
into the functions of the :dlcmd:`status` command. If you are
interested in this, checkout the :ref:`dedicated Findoutmore <fom-status>`.
interested in this, checkout the dedicated :find-out-more:`on the datalad status command <fom-status>`.

.. index::
pair: status; DataLad command
Expand Down
2 changes: 1 addition & 1 deletion docs/basics/101-135-help.rst
Original file line number Diff line number Diff line change
Expand Up @@ -212,7 +212,7 @@ To get extensive information on what :dlcmd:`status` does underneath the hood, y
$ datalad status
$ ...
You can find out a bit more on environment variable :ref:`in the Findoutmore on environment variables <fom-envvar>`.
You can find out a bit more on environment variable in the :find-out-more:`in on environment variables <fom-envvar>`.

The configuration variable can be used to set the log level on a user (global) or system-wide level with the :gitcmd:`config` command:

Expand Down
2 changes: 1 addition & 1 deletion docs/basics/101-139-gin.rst
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ Once you have `registered <https://gin.g-node.org/user/sign_up>`_
an account on the GIN server by providing your e-mail address, affiliation,
and name, and selecting a user name and password, you should upload your
:term:`SSH key` to allow SSH access
(you can find an explanation of what SSH keys are and how you can create one in :ref:`this Findoutmore <fom-sshkey>` in the general section :ref:`share_hostingservice`).
(you can find an explanation of what SSH keys are and how you can create one in this :find-out-more:`on SSH keys <fom-sshkey>` in the general section :ref:`share_hostingservice`).
To do this, visit the settings of your user account. On the left hand side, select
the tab "SSH Keys", and click the button "Add Key":

Expand Down

0 comments on commit 290503b

Please sign in to comment.