added firmwares

Added STL file for printing body parts.

redid uf2s; moved files to be more clear in directory structure

updated firmwares to include a liftoff fix

updated case files to rev3

firmwares/README.md

@@ -0,0 +1,13 @@
+## What is "drag_scroll_click_and_hold" vs. "drag_scroll_toggle"?
+
+Each directory contains a type of firmware. For "click_and_hold", the drag scroll functionality works by clicking and holding the drag scroll button.
+
+For "toggle", the drag scroll functionality works by clicking to turn on the drag scroll, and clicking again to turn it off.
+
+## What is "semaphore_X"?
+
+That is a notation of how sensitive the drag scroll is.
+
+"semaphore_8" is the **least sensitive** drag scroll. That means, you'll have to move the ball more to scroll.
+
+"semaphore_0" is the **most sensitive** drag scroll. That means, you'll have to move the ball less to scroll.

hardware/mechanicals/README.md

@@ -1,10 +1,6 @@
 ## Only one file? Where are the parts?
 
-The STEP file contains all of the Adept trackball plastic parts in one file. Doing it this way preserves the assembly information, showing how the parts are supposed to fit together, as well as the expected clearances between parts. It also bundles all of the parts for a given revision together, so there's no accidental mixing of parts from different revisions.
-
-## Where are the STLs?
-
-There aren't any. STL files are to 3D models like compiled binaries are to code: useful, but not meaningfully open source. STEPs are editable and preserve design intent, which is why we're using them here.
+The STEP/STL files contain all of the Adept trackball plastic parts in one file. Doing it this way preserves the assembly information, showing how the parts are supposed to fit together, as well as the expected clearances between parts. It also bundles all of the parts for a given revision together, so there's no accidental mixing of parts from different revisions.
 
 ## How do I print this?
 
@@ -20,4 +16,4 @@ If you do not, then using the included .3mf file is likely going to cause you a
 
 ## Why don't you include a .gcode file?
 
-For your safety. Uploading a .gcode file onto a printer can be extremely hazardous if that .gcode file wasn't specifically generated for that printer. We don't want to come anywhere near that sort of scenario, so we are not going to upload a .gcode file.
+For your safety. Uploading a .gcode file onto a printer can be extremely hazardous if that .gcode file wasn't specifically generated for that printer. We don't want to come anywhere near that sort of scenario, so we are not going to upload a .gcode file.