diff --git a/documentation/index.md b/documentation/index.md
index b5def79..6a1f37c 100644
--- a/documentation/index.md
+++ b/documentation/index.md
@@ -15,7 +15,7 @@ We are not responsible for any damaged devices or property resulting from this g
 
 * The Brocade only has one Out Of Band management port, so the code is only aware of the #1 OOB port. The #2 management port will no longer do anything. 
 * Due to a difference in PCB trace layout for the management port PHY, the management-only port may link at slower speeds than it did under Fastpath (eg at 100mbit). In a rare case, we saw it stop linking altogether until a software revert. For more information, please [click here](http://brokeaid.com/mgmt/). This only affects the management port. All other ports, including copper ports function perfectly. In-band management functions perfectly, it is only the OOB port PHY affected.
-* If you don't like the Brocade OS, or have other issues, you can always flash back to 100% stock Fastpath using the Revert guide to the left, so none of this is permanent.  
+* If you don't like the Brocade OS, or have other issues, you can always flash back to 100% stock Fastpath using the revert guide to the left, so none of this is permanent.  
 
 If you're looking to purchase an LB6M, we recommend [UnixPlus](https://www.unixplus.com/products/quanta-lb6m-24-port-10gbe-sfp-4x-1gbe-l2-l3-switch) - their stock is all brand new and of known origin.
 ## Prerequisites
diff --git a/documentation/mgmt.md b/documentation/mgmt.md
index 60db815..7daa973 100644
--- a/documentation/mgmt.md
+++ b/documentation/mgmt.md
@@ -1,9 +1,10 @@
+
 # Management Port Behavior
 
 ## What Happens
 The out of band management port is gigabit PHY - however for some users, after flashing the Brocade firmware it will instead start linking up at 100mbit. In even rarer cases, some users have seen it link at 10mbit. In all of these cases it continues to operate fine as it's only passing management traffic. In some extremely rare cases (observed on 2 chassis), it will refuse to link at all.  
 
-You can obviously still use in-band management IP's to access the switch, or even designate another switch port in its own isolated VLAN as a management-only port via ACLs. 
+You can obviously still use in-band management IP's to access the switch, or even designate another switch port in its own isolated VLAN as a management-only port via ACLs. Worst case you can revert to the stock Fastpath OS, and the management port will function perfectly as before (and your switch will be 100% back to stock).
 
 ## Why It Happens
 It's hard to say with 100% certainty without using an oscilloscope on the various clocks and data lines for the management PHY, and comparing scoped values to values seen while running Fastpath (when the port works properly). What is most likely happening is the Brocade firmware tells the management CPU to use slightly different clock speed values to drive the management PHY, as the traces from the management CPU to the management PHY are shorter in the Brocade.