diff --git a/docs/logging.md b/docs/logging.md
index 1bb177ac4f..3696097dc9 100644
--- a/docs/logging.md
+++ b/docs/logging.md
@@ -77,6 +77,8 @@ if the environment variable is set, the configuration key `log.file` will not ha
 RabbitMQ starts logging early on node start. See the [Configuration guide](./configure)
 for a general overview of how to configure RabbitMQ.
 
+The full list of available configuration options can be found in the [example rabbitmq.conf -file](https://github.com/rabbitmq/rabbitmq-server/blob/v3.13.x/deps/rabbit/docs/rabbitmq.conf.example).
+
 ### Logging to a File {#logging-to-a-file}
 
 Logging to a file is one of the most common options for RabbitMQ installations. In modern releases,
@@ -107,7 +109,7 @@ The following example instructs RabbitMQ to log to a file at the `debug` level:
 log.file.level = debug
 ```
 
-Supported log levels ca be found in the [example rabbitmq.conf file](https://github.com/rabbitmq/rabbitmq-server/blob/v3.13.x/deps/rabbit/docs/rabbitmq.conf.example).
+> Supported log levels are discussed in the [Log Levels -section](#log-levels) found below.
 
 Logging to a file can be deactivated with
 
@@ -217,7 +219,7 @@ The following example instructs RabbitMQ to use the `debug` logging level when l
 log.console.level = debug
 ```
 
-Supported log levels ca be found in the [example rabbitmq.conf file](https://github.com/rabbitmq/rabbitmq-server/blob/v3.13.x/deps/rabbit/docs/rabbitmq.conf.example).
+> Supported log levels are discussed in the [Log Levels -section](#log-levels) found below.
 
 Logging to console in JSON format: