Added dev container config.

Author: snvgglebear

.devcontainer/devcontainer.json

@@ -0,0 +1,24 @@
+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
+// README at: https://github.com/devcontainers/templates/tree/main/src/debian
+{
+	"name": "Debian",
+	// Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
+	"image": "mcr.microsoft.com/devcontainers/base:trixie",
+	"features": {
+		"ghcr.io/devcontainers-extra/features/mkdocs:2": {},
+		"ghcr.io/devcontainers/features/python:1": {}
+	},
+	"postCreateCommand": "pip install --user -r requirements.txt"
+
+	// Features to add to the dev container. More info: https://containers.dev/features.
+	// "features": {},
+
+	// Use 'forwardPorts' to make a list of ports inside the container available locally.
+	// "forwardPorts": [],
+
+	// Configure tool-specific properties.
+	// "customizations": {},
+
+	// Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
+	// "remoteUser": "root"
+}

docs/programming/autonomous.md

@@ -4,7 +4,7 @@
 
 ## Overview
 
-In this section we will be going over
+In this section we will be going over:
 
 1. Creating an autonomous command group
 2. Using RobotPreferences to quickly change our autonomous values
@@ -20,9 +20,8 @@ In this section we will be going over
 
 - An autonomous command is a command that is ran during "autonomous mode" under the **autonomousInit** method in **Robot.java** 
 - It could be a single **command** or a **command group**
-- It's especially helpful to have if you don't have any cameras to drive the robot during a 
-"sandstorm" period (2019 game mechanic where the drivers couldn't see during the pre tele-op phase)
-- For this tutorial we will create an autonomous **command group** that makes the robot drive forward 5 feet, wait 5 seconds, and then pitch the shooter up during autonomous 
+- It's especially helpful to have if you don't have any cameras to drive the robot during autonomous (rare, but does happen)
+- For this tutorial we will create a simple autonomous **command ** that makes the robot drive forward slightly.
 
 ## Creating Commands For Autonomous
 

docs/programming/driving_robot.md

@@ -600,7 +600,7 @@ Since we will be using this command to control the robot we want it to run indef
 #### In the end method
 
 !!! summary ""
-    **1)** We will call the arcadeDrive method and give it 0 and 0 as the parameters. 
+    **1)** We will call the arcadeDrive method and give it 0 and 0 as the parameters. this will stop the robot when the command completes. 
 
     In the end() method type:
 
@@ -695,7 +695,7 @@ In order to drive our robot, it needs to know what will be controlling it. To do
     **1)** Open Constants.java
       Check and make sure the `kDriverControllerPort` constant is present.
     **2)** Open RobotContainer.java
-    - Change all `ExampleSubsystem` references to `DriveSubsystem`
+    - Change all `ExampleSubsystem` references to `DriveSubsystem` (or whatever the name of your drive subsystem is.)
 
 <!-- TODO: add details on how to find joystick port in driverstation tips -->
 
@@ -704,11 +704,11 @@ In order to drive our robot, it needs to know what will be controlling it. To do
 
 !!! summary ""
     **1)** Back in **RobotContainer.java** We will need to remove everything inside the `configureBindings` method.
-    **2)** in the `configureBindings`we will call the `setDefaultCommand` of `m_drivetrain` and create a new `DriveArcade` command with parameters. 
+    **2)** in the `configureBindings`we will call the `setDefaultCommand` of `drivetrain` and create a new `DriveArcade` command with parameters. 
 
     - Commands in this method will run when the robot is enabled.
       - They also run if no other commands using the subsystem are running.
-      - This is why we write **addRequirements(Robot.m_subsystemName)** in the commands we create, it ends currently running commands using that subsystem to allow a new command is run.
+      - This is why we write **addRequirements(Robot.subsystemName)** in the commands we create, it ends currently running commands using that subsystem to allow a new command is run.
     - We will the default command for the drive subsystem to an instance of the `DriveArcade` with the values provided by the joystick axes on the driver controller. 
       - The Y axis of the controller is inverted so that pushing the stick away from you (a negative value) drives the robot forwards (a positive value). 
       - Similarly for the X axis where we need to flip the value so the joystick matches the WPILib convention of counter-clockwise positive