docs/configuring-playbook-bot-baibot.md

@@ -46,7 +46,7 @@ matrix_bot_baibot_enabled: true
 matrix_bot_baibot_config_user_password: 'PASSWORD_FOR_THE_BOT'
 
 # An optional passphrase to use for backing up and recovering the bot's encryption keys.
-# You can put any string here, but generating a strong one is preferred (e.g. `pwgen -s 64 1`).
+# You can use any string here. Consider generating it with `pwgen -s 64 1`.
 #
 # If set to null, the recovery module will not be used and losing your session/database
 # will mean you lose access to old messages in encrypted room.

docs/configuring-playbook-bot-postmoogle.md

@@ -41,7 +41,7 @@ matrix_bot_postmoogle_password: PASSWORD_FOR_THE_BOT
 # matrix_bot_postmoogle_admins:
 #  - '@yourAdminAccount:domain.com'
 #
-# .. unless you've made yourself an admin of all bots/bridges like this:
+# .. unless you've made yourself an admin of all bridges like this:
 #
 # matrix_admin: '@yourAdminAccount:domain.com'
 ```

docs/configuring-playbook-external-postgres.md

@@ -3,9 +3,11 @@
 By default, this playbook would set up a PostgreSQL database server on your machine, running in a Docker container.
 If that's alright, you can skip this.
 
+If you'd like to use an external PostgreSQL server that you manage, you can edit your configuration file  (`inventory/host_vars/matrix.<your-domain>/vars.yml`).
+
 **Note**: using **an external Postgres server is currently [not very seamless](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1682#issuecomment-1061461683) when it comes to enabling various other playbook services** - you will need to create a new database/credentials for each service and to point each service to its corresponding database using custom `vars.yml` configuration. **For the best experience with the playbook, stick to using the integrated Postgres server**.
 
-If you'd like to use an external Postgres server that you manage, add the following configuration to your `inventory/host_vars/matrix.DOMAIN/vars.yml` file (adapt to your needs):
+If you'd like to use an external Postgres server, add the following configuration to your `inventory/host_vars/matrix.DOMAIN/vars.yml` file (adapt to your needs):
 
 ```yaml
 postgres_enabled: false

docs/configuring-playbook-matrix-registration.md

@@ -24,7 +24,7 @@ Add the following configuration to your `inventory/host_vars/matrix.DOMAIN/vars.
 ```yaml
 matrix_registration_enabled: true
 
-# Generate a strong secret here. Consider generating it with `pwgen -s 64 1`
+# Generate a strong secret using: `pwgen -s 64 1`.
 matrix_registration_admin_secret: "ENTER_SOME_SECRET_HERE"
 ```
 

docs/configuring-playbook-shared-secret-auth.md

@@ -10,11 +10,12 @@ Add the following configuration to your `inventory/host_vars/matrix.DOMAIN/vars.
 
 ```yaml
 matrix_synapse_ext_password_provider_shared_secret_auth_enabled: true
-
-# Generate a strong shared secret here. Consider generating it with `pwgen -s 64 1`
 matrix_synapse_ext_password_provider_shared_secret_auth_shared_secret: YOUR_SHARED_SECRET_GOES_HERE
 ```
 
+You can generate a strong shared secret with a command like this: `pwgen -s 64 1`
+
+
 ## Authenticating only using a password provider
 
 If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it: