From 5ff98db4a23bf74d767178f14ec7aad194f245ad Mon Sep 17 00:00:00 2001
From: Andrew Haselton <andrewhaselton001@gmail.com>
Date: Fri, 11 Sep 2026 15:24:52 -0500
Subject: [PATCH 1/2] Add "why commands v3" blurb to stage 1b overview

---
 src/content/docs/learning-course/index.mdx | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/src/content/docs/learning-course/index.mdx b/src/content/docs/learning-course/index.mdx
index 4f7594bf..d4ea933d 100644
--- a/src/content/docs/learning-course/index.mdx
+++ b/src/content/docs/learning-course/index.mdx
@@ -99,3 +99,20 @@ or [Discord.](https://discord.com/invite/uUugPrPZFs)
 <CourseSection title="Stage 2" imageAlt="Course Setup">
     <p>TBD</p>
 </CourseSection>
+
+<Aside type="note">
+    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
+    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 />
+    <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,
+    enabling users to write the same functionality in a much simpler and easier
+    way.
+</Aside>

From 6faa30c210031e7e26d34b0dc7ed2c4da3971136 Mon Sep 17 00:00:00 2001
From: Andrew Haselton <andrewhaselton001@gmail.com>
Date: Fri, 11 Sep 2026 16:11:47 -0500
Subject: [PATCH 2/2] Move to correct file

---
 src/content/docs/learning-course/index.mdx      | 17 -----------------
 .../stage1/stage1b/stage-overview.mdx           | 17 +++++++++++++++++
 2 files changed, 17 insertions(+), 17 deletions(-)

diff --git a/src/content/docs/learning-course/index.mdx b/src/content/docs/learning-course/index.mdx
index d4ea933d..4f7594bf 100644
--- a/src/content/docs/learning-course/index.mdx
+++ b/src/content/docs/learning-course/index.mdx
@@ -99,20 +99,3 @@ or [Discord.](https://discord.com/invite/uUugPrPZFs)
 <CourseSection title="Stage 2" imageAlt="Course Setup">
     <p>TBD</p>
 </CourseSection>
-
-<Aside type="note">
-    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
-    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 />
-    <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,
-    enabling users to write the same functionality in a much simpler and easier
-    way.
-</Aside>
diff --git a/src/content/docs/learning-course/stage1/stage1b/stage-overview.mdx b/src/content/docs/learning-course/stage1/stage1b/stage-overview.mdx
index 18b35719..d27db013 100644
--- a/src/content/docs/learning-course/stage1/stage1b/stage-overview.mdx
+++ b/src/content/docs/learning-course/stage1/stage1b/stage-overview.mdx
@@ -29,3 +29,20 @@ This stage will cover the following topics:
 - [Suppliers in Command-Based](/learning-course/stage1/stage1b/suppliers-in-command-based/)
 - [Exercise: Kitbot Rewrite, Pt 2](/learning-course/stage1/stage1b/command-based-kitbot-pt2/)
 - [Bonus: Spot the Error, Pt 2](/learning-course/stage1/stage1b/spot-the-error-pt2/)
+
+<Aside type="note">
+    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
+    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 />
+    <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,
+    enabling users to write the same functionality in a much simpler and easier
+    way.
+</Aside>