diff --git a/Servers/Microsoft Exchange/Scripts/DAG/Database Management.md b/Servers/Microsoft Exchange/Scripts/DAG/Database Management.md
index de7eb18..e113f76 100644
--- a/Servers/Microsoft Exchange/Scripts/DAG/Database Management.md	
+++ b/Servers/Microsoft Exchange/Scripts/DAG/Database Management.md	
@@ -38,7 +38,7 @@ Move-ActiveMailboxDatabase -Identity "DB01" -ActivateOnServer "MX-DAG-02" -Mount
 ### Troubleshooting
 You may run into issues where either the `Status` or `ContentIndexState` are either Unhealthy, Suspended, or Failed.  If this happens, you need to resume replication of the database from the production active/mounted server to the server that is having issues.  In the worst-case, you would re-seed the replica database from-scratch.
 
-### If `Status` is Unhealthy or Suspended
+#### If `Status` is Unhealthy or Suspended
 If one of the DAG members has a status of "**Unhealthy**", you can run the following command to attempt to resume replication.
 ```powershell
 Resume-MailboxDatabaseCopy -Identity "DB01\MX-DAG-02"
@@ -49,13 +49,13 @@ If this fails to cause replication to resume, you can try telling the database t
 Resume-MailboxDatabaseCopy -Identity "DB01\MX-DAG-02" -ReplicationOnly
 ```
 
-### If `ContentIndexState` is Unhealthy or Suspended
+#### If `ContentIndexState` is Unhealthy or Suspended
 If you see that the "ContentIndexState" is unhappy, you can run the following command to force it to re-seed / rebuild itself.  (This is non-destructive this this is happening on a replica database).
 ```powershell
 Update-MailboxDatabaseCopy "DB01\MX05" -CatalogOnly -BeginSeed
 ```
 
-### If Replica Database is FUBAR
+#### If Replica Database is FUBAR
 If the replica database just is not playing nice, you can take the *nuclear option* of completely rebuilding the replica database.  
 
 !!! warning