fixes deploy and upload

Author: h00die

documentation/modules/exploit/multi/http/tomcat_mgr_deploy.md

@@ -3,7 +3,7 @@ This documentation is slightly different from the standard module documentation
 This documentation is broken down by OS, Tomcat version, then privilege to show exploitation in each variation.
 
 # Cleanup
-It should be stated outright that the exploit does NOT undeploy the shellcode from Tomcat.  This can be done [manually](#manual-cleanup).
+It should be stated outright that the exploit MAY NOT undeploy the shellcode from Tomcat.  This can be done [manually](#manual-cleanup).
 
 # tomcat_mgr_upload
 This module is VERY similar to `exploit/multi/http/tomcat_mgr_upload`, the main difference is this uses a `PUT` HTTP request, instead of going through a `POST` HTTP request through the GUI.
@@ -205,10 +205,10 @@ Of note, the user was given `manager-gui` permissions by default.
 
 1. Edit `/etc/tomcat6/tomcat-users.xml` to add the following:
 
-  ```
-  <role rolename="manager"/>
-  <user username="tomcat" password="tomcat" roles="manager"/>
-  ```
+    ```
+    <role rolename="manager"/>
+    <user username="tomcat" password="tomcat" roles="manager"/>
+    ```
 
 2. Restart Tomcat: `sudo service tomcat6 restart`
 
@@ -323,10 +323,10 @@ Of note, as of 7, the permission role 'manager' has been divided into several su
 
 1. Edit `/etc/tomcat8/tomcat-users.xml` to add:
 
-  ```
-  <role rolename="manager-script"/>
-  <user username="tomcat" password="tomcat" roles="manager-script"/>
-  ```
+    ```
+    <role rolename="manager-script"/>
+    <user username="tomcat" password="tomcat" roles="manager-script"/>
+    ```
 
 2. Restart tomcat: `sudo service tomcat8 restart`
   1. To verify the permissions are all set correctly, browse to `http://192.168.2.118:8087/manager/text/deploy`, and you should see `FAIL - Invalid parameters supplied for command [/deploy]
@@ -375,4 +375,4 @@ Of note, as of 7, the permission role 'manager' has been divided into several su
 
 ## Manual Cleanup
 
-Manual cleanup can be done by logging into the `/manager` website.  From there, click `Undeploy` within the `Application` list to remove the malicious app from Tomcat.
+Manual cleanup can be done by logging into the `/manager` website.  From there, click `Undeploy` within the `Application` list to remove the malicious app from Tomcat.