Trying to unbreak things please ignore

blog/2024-04-23-General-Status-Update-13.md

@@ -8,8 +8,8 @@ authors:
     title: Zero The Hut
 tags: [competition season]
 ---
-lots happening today as we get ready for state and dive into off season progects.
-* Revolution Reprair (Xiaohan, Davey): Xiaohan and Davey worked on geting Revolution back up and runing.
+Lots happening today as we get ready for state and dive into off season progects.
+* Revolution Repair (Xiaohan, Davey): Xiaohan and Davey worked on geting Revolution back up and runing.
 * Pattern Language Work (Serena): Serena worked on filling out or pattern languge and what we learned from this season.
 * PID Teaching (Rowan, Griffin): Rowan was teaching Griffen about PID tuning. 
 * AdvantageScope (Us Two): Zack and Augie worked on testing our AdvantageScope and figuring out how it works. 

docs/how-to-docu/_category_.json

@@ -1,5 +1,5 @@
 {
-  "label": "How To Docusaurous",
+  "label": "How To: Docusaurus",
   "position": 10,
   "link": {
     "type": "generated-index",

docs/how-to/_category_.json

@@ -1,8 +1,8 @@
 {
-  "label": "How To Do X",
+  "label": "How To: General",
   "position": 5,
   "link": {
     "type": "generated-index",
-    "description": "Collection of how to do something. One page. Not necesarily a robot thing."
+    "description": "Collection of how to do various things in one page. Not necessarily a robot thing."
   }
 }

docs/how-to/how-to-blog-post.md

@@ -1,5 +1,7 @@
-# How to make a blog post
+# How To Make a Blog Post
 
-## Interperting the slug
+## Interpreting the slug
 
-The slug is a funky thing that is used to identify blog posts. It is structured as followed: Year (currently two digits, find your own solution to Y100), week indicator (BW for Build Week, CW for Competition Week, OW for Off-Season Week, TW for Training Week), week number (BW -> CW at the week of the Duluth competition, CW -> OW after the last competition of the year, OW -> TW at the start of the next school year, and TW -> BW at Kickoff), 
+The slug is a funky thing that is used to identify blog posts. It is structured as followed: Year (currently two digits, find your own solution to Y100), week indicator (BW for Build Week, CW for Competition Week, OW for Off-Season Week, TW for Training Week), week number (BW -> CW at the week of the Duluth competition, CW -> OW after the last competition of the year, OW -> TW at the start of the next school year, and TW -> BW at Kickoff), and Weekday(T for Tuesday, H for Thursday, and S for Saturday. If any outlier practices were to occur, you would use the first letter that is not in use for another day)
+An example of this in use can be seen in the Blog Post for 2025/3/18, where the slug appears like this: 25-C4-T. 
+In this example, 25 is for 2025, C4 for Competition Week 4, and T for Tuesday. 

docs/how-to/how-to-edit-files.md

@@ -4,7 +4,7 @@ sidebar_position: 3
 
 # How to edit files
 
-If the question was asked "How do I edit a file" you would get lots of opinions, and it would matter what type of files we meant. You don't use a CAD program, an image editor, and a text editor all on the same file. At least most of us don't we use purpose built tools. Here I am only going to talk about text editors. And just the ones we use with robotics here at NoMythic. If you have a favorite, go ahead and use it, but the mentors may not be as knowledgeable about that tool if you have issues.
+If the question was asked "How do I edit a file?" you would get lots of opinions, and it would matter what type of files we meant. You don't use a CAD program, an image editor, and a text editor all on the same file- we use purpose built tools. Here I am only going to talk about text editors. And just the ones we use with robotics here at NoMythic. If you have a favorite, go ahead and use it, but the mentors may not be as knowledgeable about that tool if you have issues.
 
 ## Notepad on Windows, TextEdit on Mac
 
@@ -15,7 +15,7 @@ We often start with students with Circuit Python, and use this very basic editor
 
 ## Arduino IDE (c and arduino)
 
-Sometimes we code sik lights and sensors on helper boards. If we are coding these in the C like Arduino code, this IDE makes sense, and since the 2.0 version was released, it has become much better. It has a built in serial console, board library, and code library management. V2 has much improved code suggestions. Check out [here](https://docs.arduino.cc/software/ide-v2) to install it. 
+Sometimes we code lights and sensors on helper boards. If we are coding these in the C like Arduino code, this IDE makes sense, and since the 2.0 version was released, it has become much better. It has a built in serial console, board library, and code library management. V2 has much improved code suggestions. Check out [here](https://docs.arduino.cc/software/ide-v2) to install it. 
 
 ## VS Code (robot code, NoMythicApp, and docusaurus)
 

docs/how-to/how-to-git.md

@@ -6,21 +6,21 @@ sidebar_position: 2
 
 ## Installing Git
 
-If you are on a Mac, pat yourself on the back and go to the next section, git is built in.
+If you are on a Mac, pat yourself on the back and go to the next section, Git is built in.
 
-On Windows, I suggest installing GitBash. This will give you a terminal with the git tools installed. See [Install Git](https://www.gitkraken.com/learn/git/git-download)
+On Windows, I suggest installing GitBash. This will give you a terminal with the Git tools installed. See [Install Git](https://www.gitkraken.com/learn/git/git-download)
 
 ## What is Git?
 
-Git is a way to store and manage versions of things like text files and images. We use it to manage our source code for the robot and for docusaurous. Git is not the only way this could be done. These systems are called Version Control Systems. Git is very popular and what we use. We can use a command line, or various programs to do this. We will got to that later but we need to talk about the why.
+Git is a Version Control System, meaning it is a way to store and manage versions of things like text files and images. We use it to manage our source code for the robot and for docusaurus. We can use a command line, or various programs to use Git. We will get to that later, but first we need to talk about why we use Git.
 
 ## Why use Git?
 
-Git is a distributed version control system. This means that there doesn't have to be one server that holds all the code. In practice, most teams use someplace like GitHub (or Bitbucket, etc) to be the "official" repository of their code. We do too. But that does not mean that you edit the code on GitHub. You stil edit code locally on your computer and then "push" your code to the server. This is good becuase many people can work on one file, or files on their own computer, and then put them together on the server, called merging. We do this so that the last person to upload code doesn't win. We want to get everyones contributions. Lets back up.
+Git is a Distributed Version Control System. This means that there doesn't have to be one server that holds all the code. In practice, most teams use someplace like GitHub (or Bitbucket, etc) to be the "official" repository of their code. We use GitHub to store all of our code, but that does not mean that you can just edit the code on GitHub. You stil edit code locally on your computer and then "push" your code to the server. This is good becuase many people can work on one file, or work on files on their own computer, and then put them together on the server, by doing something called "merging". We do this so that the last person to upload code doesn't erase all the other contributions.
 
 ## How does this work?
 
-You get a "main" and you get a "main" and you get a "main. When I said there are versions of a file there are actually versions of a group of files. This group is called a branch. The main, or official branch is called "main" in most of our repositories. (Old ones were called master - we and the community have stopped calling it that) When you work on changes you will work on a different branch. Rember how I said this was distributed? That means that each computer that is working with a repository will have the main branch on their machine. Everyones main branch might not have exactly the same changes, but they could, by syncing with the main branch on Github.
+You get a "main" and you get a "main" and you get a "main". When I said there are versions of a file there are actually versions of a group of files. This group is called a branch. The main, or official branch is called "main" in most of our repositories. (Old ones were called master - we and the community have stopped calling it that) When you work on changes you will work on a different branch. Rember how I said this was distributed? That means that each computer that is working with a repository will have the main branch on their machine. Everyones main branch might not have exactly the same changes, but they could, by syncing with the main branch on Github.
 
 ## No really, how does this work?
 

docs/robot-docs/pneumatics.md

@@ -1,13 +1,9 @@
 # Pneumatics
 
-Pneumatics are air pressure powered pistons that provide explosive and strong power.
-
+Pneumatics are air pressure powered pistons that provide explosive and strong power. We control Pneumatics using  valves called "solenoids", which determine the direction that air flows. These valves can be programmed to provide mechanical motor, like motors and servos. We have used Pneumatics in the past(such as on Janus), but have mainly stopped using them.
 
 ## What comes with Pneumatics?
 
-I will preface that pneumatics are not actually called pneumatics in the code. They are called solenoids so from here on out I 
-may be calling them solenoids, but they're pretty much refer the same thing.
-
 There are really 3 main objects that come with the pneumatics package, the Pneumatics Control Module (PCM), the Compressor, and 
 the Solenoid. There are other things that exist, but in the code those are really the only things you need to worry about. The PCM 
 is the hub, both the solenoid and compressor both plug into the PCM and tells them what they should be doing. The solenoid is the 

docs/tutorials/_category_.json

@@ -1,5 +1,5 @@
 {
-  "label": "Robot Tutorials",
+  "label": "Tutorials for New Programmers",
   "position": 3,
   "link": {
     "type": "generated-index"

src/components/HomepageFeatures/index.js

@@ -10,18 +10,18 @@ const FeatureList = [
     imageurl: require('@site/static/img/Clover_Janusx200.jpg').default,
     description: (
       <>
-        Documentaion out team wants to know for next time. What worked, what didn't,
-        and info on each years robot is in this section.
+        Documentation of the things we learned during the year. What worked, what didn't,
+        and info on our robots are in this section.
       </>
-    ),
+    ),  
   },
   {
     title: 'Tutorials',
-    link: '/docs/category/robot-tutorials',
+    link: '/docs/category/tutorials-for-new-programmers',
     imageurl: require('@site/static/img/circuit_playground.jpg').default,
     description: (
       <>
-        Tutorials and How to's to help you learn different topics. From python on 
+        Tutorials and How Tos to help you learn different topics. From Python on 
         Adafruit Circuit boards to an Intro to Java, and more.
       </>
     ),