diff --git a/docs/operator/installing_daemons.md b/docs/operator/installing_daemons.md
index b234668927..b76c01f7a2 100644
--- a/docs/operator/installing_daemons.md
+++ b/docs/operator/installing_daemons.md
@@ -74,9 +74,8 @@ docker run --name=rucio-judge-cleaner \
 ## Environment Variables
 
 As shown in the examples above the rucio-daemon image can be configured
-using environment variables that are passed with [docker
-run]{.title-ref}. Below is a list of all available variables and their
-behaviour:
+using environment variables that are passed with `docker run`. 
+Below is a list of all available variables and their behaviour:
 
 ### RUCIO_DAEMON
 
diff --git a/docs/operator/installing_server.md b/docs/operator/installing_server.md
index ebf1cde4f4..cdda525d49 100644
--- a/docs/operator/installing_server.md
+++ b/docs/operator/installing_server.md
@@ -147,7 +147,7 @@ you set this variable to `True` the output will be written to `access_log` and
 
 ### RUCIO_LOG_LEVEL
 
-The default log level is [info]{.title-ref}. You can change it using this
+The default log level is `info`. You can change it using this
 variable.
 
 ### RUCIO_LOG_FORMAT
diff --git a/docs/operator/setting_up_demo.md b/docs/operator/setting_up_demo.md
index 27c0ef54a3..e0478aad85 100644
--- a/docs/operator/setting_up_demo.md
+++ b/docs/operator/setting_up_demo.md
@@ -16,7 +16,7 @@ Please make sure that you install this recent Docker version especially
 if you are on CentOS, i.e. its default version is ancient and does not
 support some features we rely on.
 
-Start the Docker daemon with [sudo systemctl start docker]{.title-ref}.
+Start the Docker daemon with `sudo systemctl start docker`.
 You can confirm that Docker is running properly by executing (might need
 `sudo`:
 
diff --git a/docs/user/developing_with_rucio.md b/docs/user/developing_with_rucio.md
index d0768cb801..023428d4ac 100644
--- a/docs/user/developing_with_rucio.md
+++ b/docs/user/developing_with_rucio.md
@@ -25,7 +25,7 @@ The methods are separated per resource type. The API in full can be viewed
 In the case of an error, Rucio returns a Python Exception with the appropriate
 Traceback, a detailed error string, and a unique error number. If the error
 occurred on the server side, it will be propagated to the client. The command
-line clients will exit back to the shell with the POSIX [errno]{.title-ref} of
+line clients will exit back to the shell with the POSIX `errno` of
 the unique Rucio error number. The full and up to date list can be found in the
 [Exception
 definition](https://github.com/rucio/rucio/blob/master/lib/rucio/common/exception.py).