update STRUCTURE.md to reflect VDML refactor

Author: liam-teale

docs/STRUCTURE.md

@@ -10,17 +10,17 @@ Looking at the file structure of a project like this can feel intimidating. This
 - `include` contains the header files
   - `include/common` headers used in various parts of the project
   - `include/pros` headers that are distributed to user projects
+    - `include/pros/devices` headers containing api for interacting with V5 devices
   - `include/rtos` headers for the scheduler (FreeRTOS)
   - `include/system` headers for low-level system functionality
     - `include/system/dev` headers for serial I/O and file management
     - `include/system/user_functions` a horrifying mess that should be destroyed
-  - `include/vdml` headers for the VEX Data Management Layer (VDML), a system to ensure thread-safety when interacting with VEX devices
 
 - `scripts` contains scripts used for building ZestCode and projects that use ZestCode
 
 - `src` contains the source files
   - `src/common` sources defining symbols used throughout the project
-  - `src/devices` implementations of VEX device abstractions. Files prefixed with `vdml_` indicate that the file makes use of the VDML
+  - `src/devices` implementations of VEX device abstractions
   - `src/rtos` sources, build scripts, and misc files of FreeRTOS
   - `src/system` sources for low-level system functionality
     - `src/system/dev` sources for serial I/O and file management