diff --git a/documentation/config.md b/documentation/config.md
index 030d31c..401457d 100644
--- a/documentation/config.md
+++ b/documentation/config.md
@@ -1,7 +1,8 @@
+
 ## Getting Started
 
 
-Brocade's CLI is nearly 90% identical to Cisco, with the majority of the differences being related to VLAN configuration. This short intro will get you set up with an account, SSH, and an in-band IP for the switch on one VLAN. The Layer 3 firmware comes with all ports in VLAN 1 by default, so if you just need layer 2 switching, you can leave the VLAN/virtual interface config as-is and use the out of band management port to talk to the switch.
+Brocade's CLI is 80% identical to Cisco, with the majority of the differences being related to VLAN configuration. This short intro will get you set up with an account, SSH, and an IP for the switch. The Layer 3 firmware comes with all ports in VLAN 1 by default, so if you just need layer 2 switching, you can leave the VLAN/virtual interface config as-is and use the out of band management port to talk to the switch.
 
 
 To enter the enable level:
@@ -30,7 +31,21 @@ Give the switch a name/hostname:
 hostname blinkenmaschine
 ```
 
-To give the switch an IP that's accessible via the normal ports, we need to a assign a virtual interface to the VLAN you'd like it to be accessible on, and give it an IP.  That virtual interface is configurable just like a normal physical interface. At it's config level you can set jumbo frames, IP addr, etc. This is also how you enable inter-VLAN routing, you just give multiple VLAN's a router interface with an IP like below, and that's it.  
+## Assigning an out-of-band management IP
+
+If you plan on using the OOB management port to talk to the switch, follow this section. If you'd rather use an in-band management IP on your VLANs, skip this section. Assuming you're still at the ```configure terminal``` level from before, run the following, replacing the IP with your own choice:
+
+```
+int management 1
+ip addr 192.168.1.50/24
+exit
+```
+You can now telnet/SSH to that IP over the OOB management port.
+
+## Assigning an in-band management IP + VLAN VE Config
+You can also assign an IP to one of the VLANs, so the switch is accessible from the normal ports. You don't have to choose one or the other, you can have in-band and out-of-band management both configured simultaneously, but the IP's will need to be on different subnets.  
+
+To give the switch an IP that's accessible via the normal ports, we need to a assign a virtual interface to the VLAN you'd like it to be accessible on, and give it an IP.  That virtual interface is configurable just like a normal physical interface. At it's config level you can set routing protocols, IP addr, etc. This is also how you enable inter-VLAN routing, you just give multiple VLAN's a router interface with an IP like below, and that's it.  
 
 Enter the config level for a vlan:
 ```
diff --git a/documentation/index.md b/documentation/index.md
index 2a15947..9f45b56 100644
--- a/documentation/index.md
+++ b/documentation/index.md
@@ -1,14 +1,17 @@
 
 
+
 # Flashing the LB6M to a Brocade TurboIron 24X
 
 ## Disclaimer & Caveats
 We are not responsible for any damaged devices or property resulting from this guide. This guide assumes you own a legitimate Brocade TurboIron and therefore have rights to the firmware & its use.
 Two things will also change due to hardware differences:
 
-* The SFP+ activity/status LEDs stop doing anything. The copper ports and chassis LEDs continue to work as normal. The Quanta uses a CPLD to multiplex the LED signals, while the Brocade uses native CPU I/O. There's no way around this difference.
+* The SFP+ port activity/status LEDs stop doing anything. The copper ports and chassis LEDs continue to work as normal. The Quanta uses a CPLD to multiplex the LED signals, while the Brocade uses native CPU I/O. There's no way around this difference.
 
-* The Brocade only has one Out Of Band management port. Your #2 OOB port will no longer do anything. You'll still have OOB management as usual on mgmt #1, and of course in-band management on all the normal ports.
+* 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. 
+* The Brocade code seems to also use a different clock or MII registers to configure the management port PHY (since it only expects one), which results in the management port not linking up at full speed for some.  
+For some it links up at 100mbps and works fine, for others, only 10mbps. In rare cases it will refuse to link up at all. You still have management access on all other ports as usual if you configure in-band management access. If your management port refuses to link up, and you need it to TFTP firmware (or other emergency), [it can be forced to link](http://brokeaid.com/mgmt/). To reiterate, this only effects the out of band management port.
 
 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
@@ -230,4 +233,4 @@ You'll need to pick up some official Brocade or Foundry optics on ebay, or buy s
 ### Contributing:
 The markdown source for these guides is hosted on [**our Github repo.**](https://github.com/Fohdeesha/quanta-brocade) If you have any suggested changes or additions feel free to submit a pull request.  
 
-```Documentation version:``` [ v2.1 (02-21-18)](https://github.com/Fohdeesha/quanta-brocade/commits/master) 
\ No newline at end of file
+```Documentation version:``` [ v2.2 (02-21-18)](https://github.com/Fohdeesha/quanta-brocade/commits/master) 
\ No newline at end of file