Update docs/configuring-playbook-mautrix-bridges.md: edit the section "Control the logging level"

Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>

docs/configuring-playbook-mautrix-bridges.md

@@ -89,6 +89,16 @@ matrix_mautrix_SERVICENAME_appservice_bot_username: "BOTNAME"
 
 Can be used to set the username for the bridge.
 
+### Configure the logging level (optional)
+
+```yaml
+matrix_mautrix_SERVICENAME_logging_level: WARN
+```
+
+to `vars.yml` to control the logging level, where you may replace WARN with one of the following to control the verbosity of the logs generated: TRACE, DEBUG, INFO, WARN, ERROR, or FATAL.
+
+If you have issues with a service, and are requesting support, the higher levels of logging will generally be more helpful.
+
 ### Extending the configuration
 
 There are some additional things you may wish to configure about the bridge.
@@ -127,16 +137,6 @@ matrix_appservice_double_puppet_enabled: true
 
 This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future.
 
-## Control the logging level (optional)
-
-```yaml
-matrix_mautrix_SERVICENAME_logging_level: WARN
-```
-
-to `vars.yml` to control the logging level, where you may replace WARN with one of the following to control the verbosity of the logs generated: TRACE, DEBUG, INFO, WARN, ERROR, or FATAL.
-
-If you have issues with a service, and are requesting support, the higher levels of logging will generally be more helpful.
-
 ## Usage
 
 To use the bridge, you need to start a chat with `@SERVICENAMEbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).