diff --git a/documentation/mac.md b/documentation/mac.md
index 4709cd8..70344c0 100644
--- a/documentation/mac.md
+++ b/documentation/mac.md
@@ -1,12 +1,33 @@
 
 
+
 # Fixing The MAC Address
 
 ## Why Do This?
-The flashing procedure resets the switches base MAC to 00e0.5200.0100 - this is the MAC address used for the management port, as well as the base address used to generate MACs for all the individual ports and vlan interfaces. Being set to this default MAC isn't a problem on it's own, but will cause serious issues if you use multiple flashed switches together.
+The flashing procedure resets the switches MAC to 00e0.5200.0100 - The OS iterates upon this base MAC to generate MACs for the management port, VE interfaces, etc. This isn't a problem by itself, but will cause serious issues if you use multiple flashed switches together (they'll all have the same MAC addresses).
 
-## Customizing The Chassis
-There's a diagnostic menu that allows you to easily enter a new MAC as well as serial information (the serial string is what's displayed in the output of ```show version```). You'll need serial port access to the switch (just like you had during the flash guide). Assuming that's taken care of, reboot the switch, then hit b to enter the bootloader prompt:
+## Fast And Easy
+If you're lazy, there's a single command in the bootloader you can use. You’ll need serial port access to the switch (just like you had during the flash guide). Assuming that’s taken care of, reboot the switch, then hit ```b``` to enter the bootloader prompt:
+```
+enable
+reload
+#watch the output and hit b when prompted
+```
+Now that we're in the bootloader, run the ```set ether-address``` command to set the base MAC back to the factory assigned address. It can usually be found on a sticker on the side of the chassis. If you can’t find it but want to set a unique MAC, you can use an [online MAC generator](https://www.miniwebtool.com/mac-address-generator/). Stick that MAC in the command below, adhering to the same formatting:
+```
+set ether-address 68a6.23fb.e3b4
+```
+Now we tell it to boot into the OS. This won't reload the bootloader, so once it boots the OS, tell it to reload. Then it will do a full reboot:
+```
+boot system flash primary
+#wait for it to load the OS, then:
+enable
+reload
+```
+It will do a full reboot and come up with your new MAC. To double check, look at the bottom output of ```show chassis```.
+
+## Slightly Longer -  Customizing The Chassis Info
+If you'd like to be thorough, there's a diagnostic menu that allows you to easily completely program the onboard EEPROM, which is where the chassis info is stored- including the MAC and serial string (the serial string is what's displayed in the output of ```show version```). You'll need serial port access to the switch (just like you had during the flash guide). Assuming that's taken care of, reboot the switch, then hit b to enter the bootloader prompt:
 ```
 enable
 reload
@@ -54,7 +75,9 @@ After some trial and error it will tell you the length and format each item need
 
 After finishing each item, it will write to EEPROM and you're done. Hit ESC until you're back to the main diagnostic menu, then enter ```7``` to reset the switch. It will reboot into the OS as normal, and now ```show chassis``` should have your new MAC at the bottom of the output. If the MAC displayed there is off by the end character, that's normal - it's using your specified base MAC to iterate upon. If you set a custom serial, you can also see that with ```show version``` - your chassis is now properly customized.  
 
-**Note to advanced users:** This custom information is all stored in EEPROM. In the ```t2``` test menu (initiated from the bootloader or hidden OS prompt), there are tests that wipe all this data. Namely the I2C and EEPROM tests - they both write garbage data to the EEPROM. If for some reason you need to run these tests, you'll need to run this customization procedure again.
+## Note To Advanced Users
+
+ The MAC and chassis information is all stored in EEPROM. In the ```t2``` test menu (initiated from the bootloader or hidden OS prompt), there are tests that wipe all this data. Namely the I2C and EEPROM tests - they both write garbage data to the EEPROM. If for some reason you need to run these tests, you'll need to run this customization procedure again.
 
 
 
diff --git a/documentation/mgmt.md b/documentation/mgmt.md
new file mode 100644
index 0000000..2e177f5
--- /dev/null
+++ b/documentation/mgmt.md
@@ -0,0 +1,18 @@
+# Management Port Behavior
+
+## What Happens
+
+
+## Why It Happens
+
+
+## Emergency Workaround
+
+
+
+### Thanks:
+[**Jon Sands**](http://fohdeesha.com/)  
+[**Bengt-Erik Norum**](http://amateurfoundation.org/)  
+
+### 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.  
diff --git a/documentation/revert.md b/documentation/revert.md
index 472529a..5e89e56 100644
--- a/documentation/revert.md
+++ b/documentation/revert.md
@@ -3,17 +3,15 @@
 # Reverting To Stock Fastpath
 
 ## Introduction 
-If for some reason you'd like to flash back to garbage stock fartpath, that's now possible. You'll need the [Brocade Firmware Zip](http://brokeaid.com/files/Brocade-TI.zip) ```(zip updated: 2-14-2018)```  - the same one linked on the main flash page.
+If you'd like to flash back to garbage stock Fartpath, that's now possible. You'll need the firmware ZIP linked on the main page. This guide can also be used to flash the Fastpath OS to an actual Brocade TurboIron, if you wanted to do that for some ungodly reason.  
 
-The zip was recently amended with a new uboot file - you *must* have this version. In the ```Fastpath Revert``` folder there should be a file named ```ubootenv.bin```  - if you have ```uboot.bin``` instead, you have an old copy of the zip.  
-
-Now that you have the proper contents of the ```Fastpath Revert``` folder (```ubootenv.bin``` and ```lb6m.1.2.0.18.img```) we can begin - copy those two files onto your TFTP server.
+In the ```Fastpath Revert``` folder, copy both ```ubootenv.bin``` and ```lb6m.1.2.0.18.img``` to your TFTP server. If you don't see a ```ubootenv.bin``` but instead have ```uboot.bin```, you have an old version of the ZIP. Delete it and re-download. 
 
 ## Preparing U-Boot
 
 As we are overwriting the boot sector again, the same warnings still apply. Copy and paste commands only (no typing). Have the device on a UPS if possible. 
 
-Connect to the serial console port of the switch and open a terminal window (9600 8N1). Also be sure to connect the #1 management port on the switch to a network that has layer 2 access to your tftp server.
+Connect to the serial console port of the switch and open a terminal window (9600 8N1). Also be sure to connect the #1 management port on the switch to a network that has layer 2 access to your TFTP server.
 
 Reboot the switch (```reload``` at the enable CLI level) while watching the serial output - it should prompt you to hit the ```b``` key to interrupt boot. Do so, which should take you here: 
 
@@ -44,7 +42,7 @@ Carrying on, assuming your output matched ours: It's time to load in the u-boot
 ```
 ip address 192.168.1.50/24
 ```
-Now copy the u-boot bootloader to a file in onboard flash named ```quanta``` (substitute the IP with the IP of your tftp server):
+Now copy the u-boot bootloader to a file in onboard flash named ```quanta``` (substitute the IP with the IP of your TFTP server):
 ```
 copy tftp flash 192.168.1.49 ubootenv.bin quanta
 ```
@@ -73,7 +71,7 @@ If your output matches, move on to the next section. If it doesn't match, you ca
 
 ## Erasing and replacing the bootloader
 
-You now have u-boot stored in RAM - The last step is to copy it from that RAM address to the bootloader address. From here on, be incredibly careful, and follow the commands exactly.
+You now have u-boot stored in RAM - The last step is to copy it from that RAM address to the bootloader address. From here on be incredibly careful, and follow the commands exactly.
 
 
 Copy u-boot from RAM to the boot sector. This single command handles erasing and writing flash properly:
@@ -111,7 +109,7 @@ fffffffc: 4bfff004 xxxxxxxx xxxxxxxx xxxxxxxx
 0000002c: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
 ```
 
-If it matches, skip on to **Booting Quanta** below - the risky part is over. However if it doesn't match, don't panic. You either entered a command wrong, or skipped one. Do not reboot yet! To recover the original Brocade bootloader back, run the below command. You'll need to make sure brocadeboot.bin from the zip is on your tftp server:
+If it matches, skip on to **Booting Quanta** below - the risky part is over. However if it doesn't match, don't panic. You either entered a command wrong, or skipped one. Do not reboot yet! To recover the original Brocade bootloader back, run the below command. You'll need to make sure brocadeboot.bin from the zip is on your TFTP server:
 
 ```
 #for recovery only!
@@ -123,7 +121,7 @@ If that command finishes succesfully, you can reboot into the bootloader again a
 
 
 ## Booting Quanta
-You now have u-boot in the proper section of flash - we just need to reboot. The "reset" command in Brocade's bootloader is bugged (will just freeze), so to make it reboot you must pull power to the switch, then re-apply. It should boot up to a u-boot prompt:
+You now have u-boot in the proper section of flash - we just need to reboot. The "reset" command in Brocade's bootloader is bugged (it will just freeze), so to make it reboot you must pull power to the switch, then re-apply. It should boot up to a u-boot prompt:
 
 ```
 =>