diff --git a/docs/configuring-playbook-bridge-matrix-bridge-sms.md b/docs/configuring-playbook-bridge-matrix-bridge-sms.md
index 5ea15577d..c580f26c5 100644
--- a/docs/configuring-playbook-bridge-matrix-bridge-sms.md
+++ b/docs/configuring-playbook-bridge-matrix-bridge-sms.md
@@ -30,7 +30,6 @@ matrix_sms_bridge_provider_android_password: supeSecretPassword
 # (optional) if your android-sms-gateway-server uses a self signed vertificate, the bridge needs a "truststore". This can be the certificate itself.
 matrix_sms_bridge_provider_android_truststore_local_path: android-sms-gateway-server.p12
 matrix_sms_bridge_provider_android_truststore_password: 123
-
 ```
 
 ### Extending the configuration
diff --git a/docs/configuring-playbook-matrix-corporal.md b/docs/configuring-playbook-matrix-corporal.md
index 1e387e046..946a0209d 100644
--- a/docs/configuring-playbook-matrix-corporal.md
+++ b/docs/configuring-playbook-matrix-corporal.md
@@ -1,12 +1,8 @@
 # Setting up Matrix Corporal (optional, advanced)
 
-<hr/>
-
 > [!WARNING]
 > This is an advanced feature! It requires prior experience with Matrix and a specific need for using [Matrix Corporal](https://github.com/devture/matrix-corporal). If you're unsure whether you have such a need, you most likely don't.
 
-<hr/>
-
 The playbook can install and configure [matrix-corporal](https://github.com/devture/matrix-corporal) for you.
 
 In short, it's a sort of automation and firewalling service, which is helpful if you're instaling Matrix services in a controlled corporate environment.
diff --git a/docs/configuring-playbook-s3.md b/docs/configuring-playbook-s3.md
index 2f6f1ad49..3679b6add 100644
--- a/docs/configuring-playbook-s3.md
+++ b/docs/configuring-playbook-s3.md
@@ -84,9 +84,7 @@ The `keyID` value is your **Access Key** and `applicationKey` is your **Secret K
 For configuring [Goofys](configuring-playbook-s3-goofys.md) or [s3-synapse-storage-provider](configuring-playbook-synapse-s3-storage-provider.md) you will need:
 
 - **Endpoint URL** — this is the  **Endpoint** value you saw above, but prefixed with `https://`
-
 - **Region** — use the value you see in the Endpoint (e.g. `us-west-002`)
-
 - **Storage Class** — use `STANDARD`. Backblaze B2 does not have different storage classes, so it doesn't make sense to use any other value.
 
 ## Other providers
diff --git a/docs/maintenance-synapse.md b/docs/maintenance-synapse.md
index cd8f11697..e7cb17c9d 100644
--- a/docs/maintenance-synapse.md
+++ b/docs/maintenance-synapse.md
@@ -3,13 +3,9 @@
 This document shows you how to perform various maintenance tasks related to the Synapse chat server.
 
 Table of contents:
-
 - [Purging old data with the Purge History API](#purging-old-data-with-the-purge-history-api), for when you wish to delete in-use (but old) data from the Synapse database
-
 - [Compressing state with rust-synapse-compress-state](#compressing-state-with-rust-synapse-compress-state)
-
 - [Browse and manipulate the database](#browse-and-manipulate-the-database), for when you really need to take matters into your own hands
-
 - [Make Synapse faster](#make-synapse-faster)
 
 💡 See this page for details about configuring Synapse: [Configuring Synapse](configuring-playbook-synapse.md)