diff --git a/docs/basics/101-109-rerun.rst b/docs/basics/101-109-rerun.rst
index 5e315bb53..750e00f2b 100644
--- a/docs/basics/101-109-rerun.rst
+++ b/docs/basics/101-109-rerun.rst
@@ -171,7 +171,7 @@ and another state from the dataset's history (a commit specified with
 ``-t``/``--to``). Let's do a :dlcmd:`diff` between the current state
 of the dataset and the previous commit (called "``HEAD~1``" in Git terminology [#f1]_):
 
-.. windows-wit:: please use datalad diff --from master --to HEAD~1
+.. windows-wit:: Use datalad diff --from master --to HEAD~1
 
    While this example works on Unix file systems, it will not provide the same output on Windows.
    This is due to different file handling on Windows.
@@ -256,7 +256,7 @@ other tools than from the machine-readable ``run record``.
 For example, to find out who (or what) created or modified a file,
 give the file path to :gitcmd:`log` (prefixed by ``--``):
 
-.. windows-wit:: use "git log master -- recordings/podcasts.tsv"
+.. windows-wit:: Use "git log master -- recordings/podcasts.tsv"
 
    A previous Windows Wit already advised to append ``main`` or ``master``, the common "default :term:`branch`", to any command that starts with ``git log``.
    Here, the last part of the command specifies a file (``-- recordings/podcasts.tsv``).
diff --git a/docs/basics/101-110-run2.rst b/docs/basics/101-110-run2.rst
index 812dc4842..ff6b79097 100644
--- a/docs/basics/101-110-run2.rst
+++ b/docs/basics/101-110-run2.rst
@@ -476,7 +476,7 @@ the ``--input`` and ``--output`` specification done before.
    can be accessed with an integer index, e.g., ``{inputs[0]}`` for the very first
    input.
 
-.. find-out-more:: ... wait, what if I need a curly bracket in my datalad run call?
+.. find-out-more:: Wait, what if I need a curly bracket in my datalad run call?
 
    If your command call involves a ``{`` or ``}`` character, you will need to escape
    this brace character by doubling it, i.e., ``{{`` or ``}}``.
diff --git a/docs/basics/101-115-symlinks.rst b/docs/basics/101-115-symlinks.rst
index 80e8125b3..ad7907fae 100644
--- a/docs/basics/101-115-symlinks.rst
+++ b/docs/basics/101-115-symlinks.rst
@@ -201,7 +201,7 @@ in certain situations. Later in this book we will have a section on how
 to manage the file system in a DataLad dataset (:ref:`filesystem`).
 
 
-.. find-out-more:: more about paths, checksums, object trees, and data integrity
+.. find-out-more:: Paths, checksums, object trees, and data integrity
    :name: fom-objecttree
 
    So how do these cryptic paths and names in the object tree come into existence?
diff --git a/docs/basics/101-135-help.rst b/docs/basics/101-135-help.rst
index ab1d969bd..7b3a5ead1 100644
--- a/docs/basics/101-135-help.rst
+++ b/docs/basics/101-135-help.rst
@@ -180,7 +180,7 @@ To get extensive information on what :dlcmd:`status` does underneath the hood, y
 
    $ datalad --log-level debug status
 
-.. find-out-more:: ... and how does it look when using environment variables or configurations?
+.. find-out-more:: How does it look when using environment variables or configurations?
 
    The log level can also be set (for different scopes) using the ``datalad.log.level`` configuration variable, or the corresponding environment variable ``DATALAD_LOG_LEVEL``.
 
diff --git a/docs/basics/101-141-push.rst b/docs/basics/101-141-push.rst
index 6a99f9a97..074f503a0 100644
--- a/docs/basics/101-141-push.rst
+++ b/docs/basics/101-141-push.rst
@@ -25,7 +25,7 @@ This, for instance, can be a :term:`GitHub`, :term:`GitLab`, or :term:`Gin`
 repository, but it can also be a Remote Indexed Archive (RIA) store for backup
 or storage of datasets [#f1]_, or a regular clone.
 
-.. find-out-more:: all of the ways to configure siblings
+.. find-out-more:: All of the ways to configure siblings
 
    .. index:: ! datalad command; create-sibling-github
    .. index:: ! datalad command; create-sibling-gitlab