Merge pull request #586 from Microsoft/tshoot-changes

Rename usb 'troubleshooting' paths

docs/device/usb.md

@@ -31,6 +31,6 @@ Here are instructions for different browsers on Windows and Mac computers. Choos
 
 ## ~hint
 
-Transfer not working? See some [troubleshooting tips](/device/usb/troubleshooting).
+Transfer not working? See some [troubleshooting tips](/device/usb/troubleshoot).
 
 ## ~

docs/device/usb/mac-chrome.md

@@ -64,6 +64,6 @@ your program will still run if the micro:bit is powered by battery.
 
 ## ~hint
 
-Transfer not working? See some [troubleshooting tips](/device/usb/troubleshooting).
+Transfer not working? See some [troubleshooting tips](/device/usb/troubleshoot).
 
 ## ~

docs/device/usb/mac-firefox.md

@@ -66,6 +66,6 @@ your program will still run if the micro:bit is powered by battery.
 
 ## ~hint
 
-Transfer not working? See some [troubleshooting tips](/device/usb/troubleshooting).
+Transfer not working? See some [troubleshooting tips](/device/usb/troubleshoot).
 
 ## ~

docs/device/usb/mac-safari.md

@@ -63,6 +63,6 @@ your program will still run if the micro:bit is powered by battery.
 
 ## ~hint
 
-Transfer not working? See some [troubleshooting tips](/device/usb/troubleshooting).
+Transfer not working? See some [troubleshooting tips](/device/usb/troubleshoot).
 
 ## ~

docs/device/usb/windows-chrome.md

@@ -79,6 +79,6 @@ Alternatively, right-click on the hex file, choose **Send to**, and then **MICRO
 
 ## ~hint
 
-Transfer not working? See some [troubleshooting tips](/device/usb/troubleshooting).
+Transfer not working? See some [troubleshooting tips](/device/usb/troubleshoot).
 
 ## ~

docs/device/usb/windows-edge.md

@@ -62,6 +62,6 @@ your program will still run if the micro:bit is powered by battery.
 
 ## ~hint
 
-Transfer not working? See some [troubleshooting tips](/device/usb/troubleshooting).
+Transfer not working? See some [troubleshooting tips](/device/usb/troubleshoot).
 
 ## ~

docs/device/usb/windows-firefox.md

@@ -59,6 +59,6 @@ your program will still run if the micro:bit is powered by battery.
 
 ## ~hint
 
-Transfer not working? See some [troubleshooting tips](/device/usb/troubleshooting).
+Transfer not working? See some [troubleshooting tips](/device/usb/troubleshoot).
 
 ## ~

docs/device/usb/windows-ie.md

@@ -61,6 +61,6 @@ your program will still run if the micro:bit is powered by battery.
 
 ## ~hint
 
-Transfer not working? See some [troubleshooting tips](/device/usb/troubleshooting).
+Transfer not working? See some [troubleshooting tips](/device/usb/troubleshoot).
 
 ## ~

docs/device/windows-app/troubleshoot.md

@@ -10,7 +10,8 @@ Make sure that your @boardname@ is connected to your computer with a micro USB c
 
 If you can't see the drive:
 
-* **Make sure that the USB cable is working.** Does the cable work on another computer? If not, find a different cable to use. Some cables may only provide a power connection and don't actually transfer data.
+* **Make sure that the USB cable is working.**
+>Does the cable work on another computer? If not, find a different cable to use. Some cables may only provide a power connection and don't actually transfer data.
 * **Try another USB port on your computer.**
 
 Is the cable good but you still can't see the **MICROBIT** drive? Hmm, you might have a problem with your @boardname@. Try the additional steps described in the [fault finding](https://support.microbit.org/support/solutions/articles/19000024000-fault-finding-with-a-micro-bit) page at microbit.org. If this doesn't help, you can create a [support ticket](https://support.microbit.org/support/tickets/new) to notify the Micro:bit Foundation of the problem.
@@ -31,7 +32,7 @@ If the version is **0234**, you **NEED** to update the [firmware](/device/firmwa
 1. Put your @boardname@ into **MAINTENANCE Mode**. To do this, unplug the USB cable from the @boardname@ and then re-connect the USB cable while you hold down the reset button. Once you insert the cable, you can release the reset button. You should now see a **MAINTENANCE** drive instead of the **MICROBIT** drive like before. Also, a yellow LED light will stay on next to the reset button.
 ![MAINTENANCE gesture](/static/mb/device/maintenance.gif)
 2. **[Download the firmware .hex file](https://support.microbit.org/helpdesk/attachments/19008095092)**
-3. Drag and drop that file into the **MAINTENANCE** drive.
+3. Drag and drop that file onto the **MAINTENANCE** drive.
 4. The yellow LED will flash while the `HEX` file is copying. When the copy finishes, the LED will go off and the @boardname@ resets. The **MAINTENANCE** drive now changes back to **MICROBIT**.
 5. The upgrade is complete! You can open the **DETAILS.TXT** file to check and see that the firmware version changed to the match the version of the `HEX` file you copied.