twrpme: misc updates for verbiage
Change-Id: I5ddd51bcd4a85d73b5606f1b52843c3bf4700cd0
diff --git a/_faq/OfficialMaintainer.markdown b/_faq/OfficialMaintainer.markdown
index 8dc3026..adc4ac5 100644
--- a/_faq/OfficialMaintainer.markdown
+++ b/_faq/OfficialMaintainer.markdown
@@ -7,9 +7,9 @@
<hr />
<ol>
<li>Device Tree</li>
-You need to have a device tree. You need to figure this out on your own. You can review other trees for help and modify it as necessary. You can use <a href="https://github.com/Tasssadar/libbootimg">libbootimg</a> to get the needed values from stock recovery to populate BoardConfig.mk.
-<li>Push your tree to Github.com.</li>
-We need to be able to fork your tree to our TeamWin repository. We can then add it to our Gerrit.twrp.me and Jenkins.twrp.me instance for building. If you want to be an active maintainer, we can give you +2 rights to merge new updates directly to our repository at Github.
+You need to have a device tree. You need to figure this out on your own. You can review other trees for help and modify it as necessary. You can use <a href="https://github.com/Tasssadar/libbootimg">libbootimg</a> to get the needed values from stock recovery to populate BoardConfig.mk.
+<li>Push your tree to GitHub.com.</li>
+We need to be able to fork your tree to our TeamWin repository. We can then add it to our Gerrit.twrp.me and Jenkins.twrp.me instance for building. If you want to be an active maintainer, we can give you +2 rights to merge new updates directly to our repository at GitHub.
<li>Verify your device tree works</li>
Make sure your image works as intended. You can use the following for a functional list to test your device:
<pre>
diff --git a/_faq/noos.markdown b/_faq/noos.markdown
index 23566d8..9f11283 100644
--- a/_faq/noos.markdown
+++ b/_faq/noos.markdown
@@ -9,6 +9,4 @@
You may be able to find a new "ROM" for your device at places like XDA or use Google to try to locate one. If you have TWRP 2.8.0.0 or newer you may be able to simply plug your device into your computer and use MTP to transfer files. If your device has a removable SD card you can use a card reader to easily transfer the flashable zip to the card then install it under the Install button in TWRP. On some devices you may also be able to use a USB thumb drive along with a special "On-The-Go" cable known as USB OTG to get the file installed. Some devices may support USB mass storage mode (found under the mount menu) to easily copy the file to the device. If all else fails, you can install ADB drivers and software to transfer files using adb push or pull. If you are using Windows (as most people do), it may be difficult to get your computer to properly recognize your device. Windows is really picky about its drivers. You may have to force install a driver or try something like universal or naked ADB drivers.
-If the above does not work for you, you can search again on XDA or Google to locate a guide for returning your device back to stock. The process varies depending on what type and brand of device you have. For HTC devices search for "RUU back to stock" plus your device's name. For Samsung search for "Odin back to stock" plus your device name. LG devices often use a "KDZ return to stock" plus your device name. Google posts factory images for Nexus devices here. Motorola posts factory images for some devices here.
-
-If you still can't get your device working, don't bother using the Contact Us button on our web page. We won't respond to these kinds of support requests.
+If the above does not work for you, you can search again on XDA or Google to locate a guide for returning your device back to stock. The process varies depending on what type and brand of device you have. For HTC devices search for "RUU back to stock" plus your device's name. For Samsung search for "Odin back to stock" plus your device name. LG devices often use a "KDZ return to stock" plus your device name. Google has factory images for [Nexus devices](https://developers.google.com/android/images).