Update docs/configuring-playbook-s3-goofys.md: remove repetitive suggestions to create a backup

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

docs/configuring-playbook-s3-goofys.md

@@ -34,15 +34,13 @@ If you have local media store files and wish to migrate to Backblaze B2 subseque
 
 It's a good idea to [make a complete server backup](faq.md#how-do-i-backup-the-data-on-my-server) before migrating your local media store to an S3-backed one.
 
-Follow one of the guides below for a migration path from a locally-stored media store to one stored on S3-compatible storage:
+After making the backup, follow one of the guides below for a migration path from a locally-stored media store to one stored on S3-compatible storage:
 
 - [Migrating to any S3-compatible storage (universal, but likely slow)](#migrating-to-any-s3-compatible-storage-universal-but-likely-slow)
 - [Migrating to Backblaze B2](#migrating-to-backblaze-b2)
 
 ### Migrating to any S3-compatible storage (universal, but likely slow)
 
-It's a good idea to [make a complete server backup](faq.md#how-do-i-backup-the-data-on-my-server) before doing this.
-
 1. Proceed with the steps below without stopping Matrix services
 
 2. Start by adding the base S3 configuration in your `vars.yml` file (seen above, may be different depending on the S3 provider of your choice)
@@ -90,8 +88,6 @@ It's a good idea to [make a complete server backup](faq.md#how-do-i-backup-the-d
 
 ### Migrating to Backblaze B2
 
-It's a good idea to [make a complete server backup](faq.md#how-do-i-backup-the-data-on-my-server) before doing this.
-
 1. While all Matrix services are running, run the following command on the server:
 
     (you need to adjust the 3 `--env` line below with your own data)