Merge pull request #65 from paradoxical-duck/master

A ton of random minor updates

Author: paradoxical-duck

…ants/followers/BSpline Follower/page.mdx app/docs/BSpline Follower/page.mdxapp/docs/constants/followers/BSpline Follower/page.mdx renamed to app/docs/BSpline Follower/page.mdx app/docs/constants/followers/BSpline Follower/page.mdx renamed to app/docs/BSpline Follower/page.mdx

@@ -16,7 +16,7 @@ of Java programming in FTC!
 
 ## When will it be released?
 Apex Pathing is currently not officially released to the public, but it's still in development. 
-We're aiming to release our first version of Apex Pathing in the next few months, before the Biobuzz FTC season begins.
+We're aiming to release our first version of Apex Pathing in the next few months, before the 2026-27 FTC season begins.
 
 
 ## What makes Apex special and different?

app/docs/about/page.mdx

@@ -2,5 +2,5 @@ export default {
     "setup": "Setup",
     "drivetrains" : "Drivetrain Configuration",
     "localizers" : "Localizer Configuration",
-    "followers" : "Follower Configuration"
+    "followers" : "Follower Configuration",
 }

app/docs/constants/_meta.js

@@ -62,7 +62,7 @@ The swerve drivetrain takes multiple arguments in the constants file:
 * Trackwidth and wheelbase measurements
 * maximum power
 * angular offsets for each module
-It's structured slightly differently by declaring stuff per module.
+Note: The swerve drivetrain constants require declarations grouped together in modules.
 ```java
 public DrivetrainConstants setDrivetrainConstants() { // Any DrivetrainConstants
         return new SwerveConstants()

app/docs/constants/drivetrains/page.mdx

@@ -28,5 +28,5 @@ Once the cloning process is complete, Android Studio will automatically open the
 </Callout>
 
 ## Constants Setup
-Now that you have the project cloned, head over to the [Constants Setup](/docs/constants/setup/) page to set up your
-Constants file and get your robot ready for tuning.
+Once you have the project cloned, head over to the [Constants Setup](/docs/constants/setup/) page to commence
+the tuning process and set up your Constants file.

app/docs/installation/page.mdx

@@ -3,7 +3,8 @@
 
 ## What are PDS controllers good for?
 A PDS controller is a precise alternative to a traditional PID controller. This controller removes the I term which can cause overshoots when it builds up.
-It's extremely advantageous for pathing applications, as the S term helps to break through static friction, thus increasing accuracy and precision.
+It's extremely advantageous for pathing applications, as the S term helps to break through static friction, thus increasing accuracy and precision. PDS controllers
+play a huge role in Apex, helping us achieve exemplarily precise pathing.
 
 ## Overview 
 This controller contains 3 terms:
@@ -23,7 +24,3 @@ generally when tuning it, you want your robot or mechanism to reach the target p
 
 The D term is generally supposed to be a very small number and it's meant to counteract the oscilation that the P term causes.
 However, it can also cause extreme oscilation or a slow response time if it's too large. The D term when tuned just right should help your robot to "snap right to the target position"
-
-
-## What role do PDS controllers play in Apex Pathing?
-

app/docs/misc/pds/page.mdx

@@ -3,7 +3,7 @@ export default {
     "heading-tuner": "Heading Tuner",
     "lateral-tuner": "Lateral Tuner",
     "axial-tuner": "Axial Tuner",
-    "teleop-test": "Teleop Test",
     "swerve-offsets": "Swerve Offsets",
+    "teleop-test": "Teleop Test",
     "bspline-tuner": "BSpline Tuner"
 }

app/docs/tuning/_meta.js

@@ -11,7 +11,7 @@ Select the **BSpline Tuner** OpMode on your Driver Station.
 Open Panels on your device and adjust the parameters as shown on the [Overview page](/docs/tuning/overview).
 
 ### Test as you tune
-Use the controls below to test your B-Spline follower tracking. Observe the pathing, adjust the parameters in your constants file, and test again until you are satisfied with the results.
+Use the controls below to test your B-Spline follower tracking. Observe the pathing, adjust the parameters in Panels, and continue running the tuner until you are satisfied with the results.
 
 | Button | Action |
 |--------|--------|

app/docs/tuning/bspline-tuner/page.mdx

@@ -41,10 +41,29 @@ tiny oscilations and allow the robot to coompletely stop.
 </Callout>
 
 ## Tuning Process -- Mecanum and Tank Drive
-Before anything else, the heading controller should be tuned to ensure that the robot can maintain its heading while 
-tuning the lateral and axial controllers. The heading tuner should be run first, followed by the lateral and axial
-tuners in any order.
+
+<Steps>
+### Heading Tuner
+Start by running the [heading tuner](/docs/tuning/heading-tuner) to tune your heading controller. This is to ensure
+that the robot can maintain its heading while running subsequent tuners.
+
+### Axial/Lateral Tuners
+Once your heading controller is tuned, you can run the [axial tuner](/docs/tuning/axial-tuner) or the [lateral tuner](/docs/tuning/lateral-tuner)
+in any order.
+</Steps>
 
 ## Tuning Process -- Swerve Drive
-The swerve module angle offsets should be debugged prior to running any of the tuners or the tuning won't do anything.
-After that, run the standard three tuners.
+
+<Steps>
+### Swerve Module Angle Offsets
+Start by debugging your [swerve module angle offsets](/docs/tuning/swerve-offsets) before running any tuner. This step is crucial to running Apex on a
+Swerve Drive robot.
+
+### Heading Tuner
+Start by running the [heading tuner](/docs/tuning/heading-tuner) to tune your heading controller. This is to ensure
+that the robot can maintain its heading while running subsequent tuners.
+
+### Axial/Lateral Tuners
+Once your heading controller is tuned, you can run the [axial tuner](/docs/tuning/axial-tuner) or the [lateral tuner](/docs/tuning/lateral-tuner)
+in any order.
+</Steps>

app/docs/tuning/overview/page.mdx

@@ -21,9 +21,9 @@ import { Steps, Callout} from 'nextra/components'
     .setModuleAngleOffset(0) //degrees
     ```
 
-    ### After doing this, your robot should be ready to run the teleop test!
+    ### Congratulations! Your robot is now ready to run the TeleOpTest.
 
 </Steps>
 <Callout type="info">
-    After doing this, all the rest of the tuning process should be the same as a mecanum drive! 
+    From this point onwards, the tuning process is the same as any other drivetrain.
 </Callout>