Update manual_failovers.md

Author: davissp14

docs/manual_failovers.md

@@ -5,12 +5,12 @@ While automatic failures are already baked-in, there may be times where a manual
 _**Note: The promotion candidate must reside within your PRIMARY_REGION.**_
 
 **1. Connect to the Machine you wish to promote**
-```
+```bash
 fly ssh console -s <app-name>
 ```
 
 **2. Confirm the member is healthy**
-```
+```bash
 # Switch to the postgres user and move to the home directory.
 su postgres
 cd ~
@@ -34,7 +34,7 @@ Node "fdaa:0:2e26:a7b:7d17:9b36:6e4b:2":
 
 Open up a separate terminal and stop the Machine running `primary`.
 
-```
+```bash
 # Identify the primary
 fly status --app <app-name>
 
@@ -50,7 +50,7 @@ fly machines stop 6e82931b729087 --app <app-name>
 **3. Run the standby promotion command**
 Go back to the first terminal you opened that's connected to your promotion candidate.
 
-```
+```bash
 # Issue a dry-run to ensure our candidate is eligible for promotion.
 repmgr standby promote --siblings-follow --dry-run
 
@@ -66,7 +66,7 @@ INFO: prerequisites for executing STANDBY PROMOTE are met
 **WARNING: It's important that you specify `--siblings-follow`, otherwise any other standbys will not be reconfigured to follow the new primary.**
 
 If everything looks good, go ahead and re-run the command without the `--dry-run` argument.
-```
+```bash
 repmgr standby promote --siblings-follow
 
 NOTICE: promoting standby to primary
@@ -82,7 +82,7 @@ INFO: STANDBY FOLLOW successfully executed on all reachable sibling nodes
 ```
 
 **4. Start the Machine that was previously operating as Primary**
-```
+```bash
 fly machines start 6e82931b729087 --app <app-name>
 ```