diff --git a/docs/conf.py b/docs/conf.py
index 2a16993c35d0a7335566375608622e3f1e37810d..89afd3945a462d00654a2807dd2ff519a9be64b8 100644
--- a/docs/conf.py
+++ b/docs/conf.py
@@ -61,8 +61,8 @@ master_doc = 'index'
 
 # General information about the project.
 project = 'Tezos'
-copyright = '2018-2023, Nomadic Labs <contact@nomadic-labs.com>'
-author = 'Nomadic Labs <contact@nomadic-labs.com>'
+copyright = '2018-2024'
+author = 'Contributors to the Octez & Tezos protocol documentation'
 
 # The version info for the project you're documenting, acts as replacement for
 # |version| and |release|, also used in various other places throughout the
diff --git a/docs/shell/dal_run.rst b/docs/shell/dal_run.rst
index c462c9b94bfd7f9a3a7cc46f036431c8e3262ded..f79053e29520849660dcbf7ada96424316f1825b 100644
--- a/docs/shell/dal_run.rst
+++ b/docs/shell/dal_run.rst
@@ -81,13 +81,15 @@ Follow these steps to run a DAL node along with a layer 1 node and a baker.
 
    The baker daemon connects to the DAL node and attests to the availability of DAL data as well as its usual layer 1 baking function.
 
-#. In a new terminal window, verify that your baking daemon has attestation rights allocated, by running this command:
+#. In a new terminal window, verify that your baking daemon has attestation rights allocated for the current cycle, by running:
 
    .. code-block:: shell
 
-      octez-client rpc get "/chains/main/blocks/head/helpers/attestation_rights?delegate=$MY_ADDRESS"
+      octez-client rpc get "/chains/main/blocks/head" | jq '.metadata.level_info.cycle'
+      octez-client rpc get "/chains/main/blocks/head/helpers/attestation_rights?delegate=$MY_ADDRESS&cycle=<current-cycle>"
 
-   If the previous command reports no attestation rights (``[]``), first check that you do have attestation rights during the current cycle (by adding the ``"&cycle=<current_cycle>"`` argument). If that is not the case, you may have to register as a delegate or re-activate your delegate and wait for a few cycles to get some rights (see :ref:`DelegateRegistration`).
+   Be aware that the last command may take several minutes to execute if it returns a long list of rights.
+   In turn, if the previous command reports no attestation rights (``[]``), you may have to register as a delegate or re-activate your delegate and wait for a few cycles to get some rights (see :ref:`DelegateRegistration`).
 
 #. Verify that the DAL node is running properly:
 
diff --git a/docs/user/exits.rst b/docs/user/exits.rst
index e02f964c77cf092d889a572191467fc21c117aad..f5cd2fa5c8e1d050ccaceb6e952b44086088310e 100644
--- a/docs/user/exits.rst
+++ b/docs/user/exits.rst
@@ -35,8 +35,8 @@ Signals
 -------
 
 Upon receiving ``SIGINT`` (e.g., via Ctrl+C in an interactive session) or
-``SIGTERM`` (e.g., via ``systemctl stop``) the process will exit (with code 64 or
-255, see details below). Note that sending the same signal a second time (after
+``SIGTERM`` (e.g., via ``systemctl stop``) the process will exit with code 127 if the cleanup happens normally. However,
+sending the same signal a second time (after
 a one (1) second grace period) will terminate the process immediately,
-interrupting the normal clean-up functions of clean-up (in this case the exit
-code will be 255).
+interrupting the normal clean-up functions, and in this case the exit
+code will be 255.