diff --git a/doc/administration/postgresql/replication_and_failover_troubleshooting.md b/doc/administration/postgresql/replication_and_failover_troubleshooting.md
index 7a4e70e080976d32b4e4303628cfbaa5faf848e2..1ac35d4973e0b442e564005aeeb37b9a13f70633 100644
--- a/doc/administration/postgresql/replication_and_failover_troubleshooting.md
+++ b/doc/administration/postgresql/replication_and_failover_troubleshooting.md
@@ -95,8 +95,8 @@ If a replica cannot start or rejoin the cluster, or when it lags behind and cann
    sudo gitlab-ctl patroni reinitialize-replica --member gitlab-database-2.example.com
    ```
 
-   This can be run on any Patroni node, but be aware that `sudo gitlab-ctl patroni
-   reinitialize-replica` without `--member` restarts the server it is run on.
+   This can be run on any Patroni node, but be aware that `sudo gitlab-ctl patroni reinitialize-replica`
+   without `--member` restarts the server it is run on.
    You should run it locally on the broken server to reduce the risk of
    unintended data loss.
 1. Monitor the logs: