Final tweaks to build workflow

Author: MaddyGuthridge

.github/workflows/build.yml

@@ -15,5 +15,5 @@ jobs:
         python-version: 3.9
     - uses: actions/upload-artifact@v3
       with:
-        name: UniversalController.zip
+        name: 'UniversalController'
         path: src

docs/setup.md

@@ -16,10 +16,11 @@ intend to contribute code to the script, you should follow the
 4.  In a different window, navigate to
     `Documents/Image-Line/FL Studio/Settings/Hardware` in your file manager.
 
-5.  Extract the `UniversalController` folder from within the zip folder to the
-    `Hardware` folder.
+5.  Extract the zip folder to a new `UniversalController` folder located within
+    the `Hardware` folder.
 
-6.  Launch (or close and relaunch) FL Studio, and open the MIDI Settings window.
+6.  Launch (or close and relaunch) FL Studio, and open the MIDI Settings
+    window.
 
 7.  Set your desired controller's ports to be the same (non-zero) value in both
     the input and output sections. Refer to the image for an example setup. For
@@ -29,20 +30,21 @@ intend to contribute code to the script, you should follow the
 8.  Select the controller in the input section, and change the controller type
     to `Universal Controller (user)`. Make sure the controller is enabled.
 
-9.  Navigate to the script output window (View > Script output), and select your
-    device's tab.
+9.  Navigate to the script output window (View > Script output), and select
+    your device's tab.
 
-10. Wait 3 seconds - if no errors appear, your device was detected successfully.
+10. Wait 3 seconds - if no errors appear, your device was detected
+    successfully.
 
 11. Familiarise yourself with your device's specific functionality in the
-    [devices section](devices/README.md), making sure to complete any additional
-    setup requirements. Enjoy using your device!
+    [devices section](devices/README.md), making sure to complete any
+    additional setup requirements. Enjoy using your device!
 
 12. If you get an error, then your device couldn't be detected. Usually this
     means that your device doesn't have a definition (I'd love if you
     [contributed one](contributing/README.md)), but if you're sure your
-    device does, it may just need some manual configuration. Refer to its manual
-    page in the [devices section](devices/devices.md).
+    device does, it may just need some manual configuration. Refer to its
+    manual page in the [devices section](devices/devices.md).
 
 Don't forget to read the basic [usage instructions](usage.md) for the script
 so that you can take full advantage of the integration it provides!