Properly Formatted Mentions of Commands v2 and v3

src/content/docs/educators-guide/introduction/preparation.mdx

@@ -9,9 +9,9 @@ If you're new to FRC programming or Java, we recommend going pretty deep through
 If you're pretty experienced with Java and FRC programming, you might just go through the Educator's Guide to get a complete overview of the course and get up to speed with practice.
 
 <Aside type="note">
-    While the commands v3 library retains many elements from the v2 library,
+    While the Commands v3 library retains many elements from the v2 library,
     there are many significant changes that impact how it is used and how to
-    best structure code. If you have experience with commands v2 but not v3, a
+    best structure code. If you have experience with Commands v2 but not v3, a
     deeper dive into the v3 library is recommended.
 </Aside>
 

src/content/docs/educators-guide/stage1/stage1b.mdx

@@ -8,14 +8,14 @@ Students refactor their Stage 1A kitbot code into `Command`s, `Trigger`s, and `M
 
 ## Commands v3 and the 2027 Framework
 
-This stage uses commands v3, which differs in syntax compared to commands v2 (the predominant commands framework used
+This stage uses Commands v3, which differs in syntax compared to Commands v2 (the predominant commands framework used
 from 2020-2026).
-Commands V3 uses coroutine-based command bodies rather than chaining `Commands.run()` and `Commands.runOnce()` blocks together.
+Commands v3 uses coroutine-based command bodies rather than chaining `Commands.run()` and `Commands.runOnce()` blocks together.
 
 As such, it is highly recommended for educators to finish Stage 1B themselves before teaching it
 to students.
 
-Students and educators should also consult the [commands v3 API documentation](https://github.wpilib.org/allwpilib/docs/2027/java/org/wpilib/command3/package-summary.html)
+Students and educators should also consult the [Commands v3 API documentation](https://github.wpilib.org/allwpilib/docs/2027/java/org/wpilib/command3/package-summary.html)
 for more information.
 
 ## Still a Kitbot

src/content/docs/educators-guide/stage2/index.mdx

@@ -90,11 +90,11 @@ Core objectives include:
 
 ### Stage 2F: State Machine Teleop
 
-In this stage, students will create an advanced teleop utilizing the commands v3 state machine API.
+In this stage, students will create an advanced teleop utilizing the Commands v3 state machine API.
 This will allow MIDTIDE to automatically intake and index coral, utilizing sensor inputs, automatically hand off the coral, and to score on levels 2-4 of the reef.
 Core objectives include:
 
-- Introducing state machines and the commands v3 state machine API
+- Introducing state machines and the Commands v3 state machine API
 - Creating intuitive driver controls
 - Using state machines for automation
 - When to choose a command or a state machine to implement different components of automation

src/content/docs/learning-course/stage1/stage1a/getting-started.mdx

@@ -85,7 +85,7 @@ Thus, the only files shown in the structure tree are the ones directly responsib
 <Aside type="note">
     For those who have programmed in FRC before, WPILib is currently undergoing
     a massive rewrite for the 2027 version, especially with regards to OpModes
-    and Commands V3, so some files and components may be completely new!
+    and Commands v3, so some files and components may be completely new!
 </Aside>
 
 ### `Main.java`

src/content/docs/learning-course/stage1/stage1b/command-based-kitbot-pt2.mdx

@@ -195,7 +195,7 @@ Just like in stage 1A, you can press `W` to drive forward, `S` to drive backward
 
 Shooting is still mapped to the `Q` button; however, you now have to hold the button down
 for >2 seconds before a shooting animation appears.
-Commands V3 has made it easier
+Commands v3 has made it easier
 for us to program a "spinup" sequence, where the launcher can get up to speed for 2 secs
 before balls are serialized through it.
 

src/content/docs/learning-course/stage1/stage1b/commands-and-mechanisms.mdx

@@ -25,8 +25,8 @@ in your robot class:
 ```
 
 <Aside type="note">
-    **Ignore this if you haven't used Commands V2!** Mechanisms in Commands V3
-    are identical to Subsystems in Commands V2. The difference is that you have
+    **Ignore this if you haven't used Commands v2!** Mechanisms in Commands v3
+    are identical to Subsystems in Commands v2. The difference is that you have
     to define your own `periodic()` method while calling it manually in
     `robotPeriodic()`, instead of overriding a method from `SubsystemBase`.
 </Aside>
@@ -58,7 +58,7 @@ you call `named()`:
 ```
 
 <Aside type="note">
-    **Ignore this if you haven't used Commands V2!** Unlike in Commands V2, the
+    **Ignore this if you haven't used Commands v2!** Unlike in Commands v2, the
     code inside of a `run()` method won't run repeatedly! Use while loops inside
     of the `run()` method to run code repeatedly.
 </Aside>

src/content/docs/learning-course/stage1/stage1b/stage-overview.mdx

@@ -37,18 +37,17 @@ This stage will cover the following topics:
 - [Bonus: Spot the Error, Pt 2](/learning-course/stage1/stage1b/spot-the-error-pt2/)
 
 <Aside type="note">
-    Why commands v3? <br />
+    Why Commands v3? <br />
     <br /> If you're an experienced programmer, you likely know about or have
-    used commands v2 in the past. Commands v3 is a major change from commands
+    used Commands v2 in the past. Commands v3 is a major change from Commands
     v2, changing the internals of the scheduler to run on Java's continuations
-    API. This much of the boilerplate code commands v2 necessitated to be
-    removed and makes writing commands more akin to writing regular Java code.{' '}
-    <br />
+    API. This change cleared much of the boilerplate required by Commands v2.
+    Writing commands is now more akin to writing regular Java code. <br />
     <br /> Commands v3 also brings many improvements related to commands
     requiring mechanisms, allowing triggers to be scoped to an opmode or
-    command, and a new state machine API. For all of these reasons, commands v3
-    was chosen for this course, as its authors believe that commands v3 offers a
-    significantly better and simpler user experience compared to commands v2,
+    command, and a new state machine API. For all of these reasons, Commands v3
+    was chosen for this course, as its authors believe that Commands v3 offers a
+    significantly better and simpler user experience compared to Commands v2,
     enabling users to write the same functionality in a much simpler and easier
     way.
 </Aside>