diff --git a/Servers/Microsoft Exchange/Scripts/DAG/Database Management.md b/Servers/Microsoft Exchange/Scripts/DAG/Database Management.md
index e293e40..de7eb18 100644
--- a/Servers/Microsoft Exchange/Scripts/DAG/Database Management.md	
+++ b/Servers/Microsoft Exchange/Scripts/DAG/Database Management.md	
@@ -13,7 +13,7 @@ Get-MailboxDatabaseCopyStatus * | Format-Table Name, Status, CopyQueueLength, Re
 | DB01\MX-DAG-01 | Mounted | 0 | 0 | Healthy |
 | DB01\MX-DAG-02 | Healthy | 0 | 0 | Healthy |
 
-!!! note "Example Output Breakdown"
+!!! info "Example Output Breakdown"
     In the above example output, you can see that there are two member servers in the DAG, `MX-DAG-01` and `MX-DAG-02`.  Then you will see that there is a status of `Mounted`, this means that `MX-DAG-01` is the active production server; this means that it is handling all mailflow and web requests / webmail.  
 
     **CopyQueueLength**: This is a number of database "*transaction logs*" that have taken place since a replica database stopped getting updates.  This is the queue of all database transactions that are being copied from the production (mounted) database to replica databases.  This data is not immediately written to the replica database(s).