Fixed additional markdown formatting errors.

Author: snvgglebear

docs/programming/autonomous.md

@@ -29,11 +29,11 @@ In this section we will be going over:
 
 ## Creating a basic Autonomous Command 
 
-!!! summary ""
+!!! abstract ""
     **1)** Create a new command called **AutoCommand** using the `create new class/command` feature in Vscode.
 
 
-!!! summary ""
+!!! abstract ""
     **2)** Before the constructor create a **double** called **distance**
 	```java
 		private Double distance;
@@ -49,33 +49,33 @@ In this section we will be going over:
 
 	- This will be used to control how long the robot will move for. 
 
-!!! summary ""
+!!! abstract ""
     **3)** In the **AutoCommand** constructor add a **DriveSubsystem** parameter called **driveSubsystem**
 
-!!! summary ""
+!!! abstract ""
     **4)** Inside type:
 
 	```java
 	distance = inches;
 	```
 
-!!! summary ""
+!!! abstract ""
     **5)** In **initialize** add our **resetDriveEncoder** method
 
     - We want to reset the encoder before we drive so that it counts the distance from zero
 
-!!! summary ""
+!!! abstract ""
     **6)** In **execute** add our **arcadeDrive** method and change the **moveSpeed** parameter to a **RobotPreference** named **driveDistanceSpeed** and **rotateSpeed** to 0.0
 
     - We only want to drive the robot forward; a **RobotPreference** will help us tune the drive speed
 
-!!! summary ""
+!!! abstract ""
     **7)** In **isFinished** type:
 
 	```java
 	return Robot.m_drivetrain.getDriveEncoderDistance() == distance;
 	```
-!!! summary ""
+!!! abstract ""
     **8)** In **end** stop the **Drivetrain** and call **end** in **interrupted**
 
 ??? Example
@@ -137,10 +137,10 @@ In this section we will be going over:
 
 - We will create an **Autonomous command group** with the **DriveDistance** command and the **ShooterPitchUp** command
 
-!!! summary ""
+!!! abstract ""
     **1)** Create a new **Command Group** named **Autonomous**
 
-!!! summary ""
+!!! abstract ""
  	**2)** In the constructor type
 
 	```java
@@ -155,30 +155,30 @@ In this section we will be going over:
 - In order to add timing in between our **commands** in our **command groups** we will need to create a **DoDelay** command
 - Unlike regular **delays** the **DoDelay** command will not stall our robot, but wait a certain amount of time before running a command
 
-!!! summary ""
+!!! abstract ""
 	**1)** Create a new command called **DoDelay**
 
-!!! summary ""
+!!! abstract ""
 	**2)** Before the constructor add two private **doubles** called **expireTime** and **timeout**
 
-!!! summary ""
+!!! abstract ""
 	**3)** In the constructor add a **double** called **seconds** in the parameter
 
-!!! summary ""
+!!! abstract ""
 	**4)** Inside the constructor set **timeout** equal to **seconds**
 
-!!! summary ""
+!!! abstract ""
 	**5)** Create a protected **void** method called **startTimer**
 
-!!! summary ""
+!!! abstract ""
 	**6)** Inside set **expireTime** equal to **timeSinceInitialized** + **timeout**
 
 	- This will let the robot know how much time will have passed since the command was initialized when it finishes
 
-!!! summary ""
+!!! abstract ""
 	**7)** In **initialized** add our **startTimer** method
 
-!!! summary ""
+!!! abstract ""
 	**8)** In **isFinished** return **timeSinceInitialized** is greater or equal to **expireTime**
 
 ??? Example
@@ -237,7 +237,7 @@ In this section we will be going over:
 
 ## Adding the DoDelay Command to Autonomous.java
 
-!!! summary ""
+!!! abstract ""
 	- Add our **DoDelay** command in between **DriveDistance** and **ShooterPitchUp** with a **RobotPreference** called **autoDelay**
 
 ??? Example 

docs/programming/deploying.md

@@ -27,12 +27,12 @@ To deploy code, first make sure your computer is  connected to the robot in **ON
 !!! note
 		Make sure your team number in **wpilib_preferences.json** in the **.wpilib** folder is set to the same team number your roboRIO was programmed for (it should be the number you set when creating the project and you will NOT need to check this every time as it should not change by itself).
 
-!!! summary “”
+!!! abstract “”
     **1)** Select the **W icon** from the tab bar or use the shortcut by holding down **Ctrl+Shift+P** at the same time. (Replace ctrl with cmd on macOS)
 
 	![](../assets/images/deploying/w_icon.png)
 
-!!! summary “”
+!!! abstract “”
     **2)** Type and hit enter or select: WPILib: Deploy Robot Code
 
 	![](../assets/images/deploying/deploy_command.png)

docs/programming/new_project.md

@@ -15,36 +15,36 @@ Before we can start programing a robot, we must create a new project in Visual S
 
 ## Creating a New Project
 
-!!! summary ""
+!!! abstract ""
 	**1)** Select the **W icon** from the tab bar or use the shortcut by holding down **Ctrl+Shift+P** at the same time. (Replace ctrl with command on macOS)  
 
 	![](../assets/images/new_project/project/step_1.png)
 
-!!! summary ""
+!!! abstract ""
 	**2)** Type and hit enter or select **WPILib: Create a new project**
 
 	![](../assets/images/new_project/project/step_2.png)
 
-!!! summary ""
+!!! abstract ""
 	**3)** Click **Select a Project Type** and choose **Template**  
 	**4)** Click **Select a Language** and choose **Java**  
 	**5)** Click **Select a project base** and choose **Command Robot**  
 
 	![](../assets/images/new_project/project/step_3.png)
 
-!!! summary ""
+!!! abstract ""
 	**6)** Click **Select a new project folder** and choose where on your computer you would like to store the program
 
 	![](../assets/images/new_project/project/step_4.png)
 
-!!! summary ""
+!!! abstract ""
 	**7)** **Enter a project name** in the text field labeled as such  
 	**8)** **Enter your team number** in the text field labeled as such  
 	**9)** Select **Generate Project**  
 
 	![](../assets/images/new_project/project/step_5.png)
 
-!!! summary ""
+!!! abstract ""
 	**10)**  When prompted **“Would you like to open the folder?”**, select **Yes (Current Window)**
 
 	![](../assets/images/new_project/project/step_6.png)
@@ -82,24 +82,24 @@ Newly created projects have many files within them. We only care about the conte
 
 ## Creating a New Subsystem
 
-!!! summary ""
+!!! abstract ""
 	**1)** Click on the **src** folder to expand it.  
 	**2)** Do the same for **java** then **subsystems**
 
 	![](../assets/images/new_project/subsystem/step_1.png)
 
-!!! summary ""
+!!! abstract ""
 	**3)** Right click on **subsystems** and select **Create a new class/ command.**
 
 	![](../assets/images/new_project/subsystem/step_2.png)
 
-!!! summary ""
+!!! abstract ""
 	**4)** Select **Subsystem (New)** and type your **DesiredSubsystemName** (i.e. **Drivetrain**) for the name and hit enter on your keyboard.
 
 	![](../assets/images/new_project/subsystem/step_3.png)  
 	![](../assets/images/new_project/subsystem/step_4.png)
 
-!!! summary ""
+!!! abstract ""
 	**5)** Click on the newly created **DesiredSubsystemName.java** (or **Drivetrain.java** if you named it that)
 
 	![](../assets/images/new_project/subsystem/step_5.png)
@@ -113,7 +113,7 @@ Newly created projects have many files within them. We only care about the conte
 
 	!!! danger "***We must do this for EVERY subsystem we create***"
 
-!!! summary ""
+!!! abstract ""
 	**1)** In RobotContainer.java we will create a new **public** **global** **constant** variable of type `DesiredSubsystemName` (i.e. `Drivetrain`):  
     `public static final m_desiredSubsystemName = new DesiredSubsystemName();`  
     (i.e. `public static final m_drivetrain = new Drivetrain();`)
@@ -156,24 +156,24 @@ Newly created subsystems are empty with the exception of the periodic.
 
 ## Creating a New Command
 
-!!! summary ""
+!!! abstract ""
 	**1)** Click on the **src** folder to expand it (if it isn't already).  
 	**2)** Do the same for **commands**
 
 	![](../assets/images/new_project/command/step_1.png)
 
-!!! summary ""
+!!! abstract ""
     **3)** Right click on **commands** and select **Create a new class/ command.**  
 
 	![](../assets/images/new_project/command/step_2.png)
 
-!!! summary ""
+!!! abstract ""
 	**4)** Select **Command (New)** and type **DesiredCommandName** (i.e. DriveArcade) for the name and hit enter on your keyboard.  
 
 	![](../assets/images/new_project/command/step_3.png)  
 	![](../assets/images/new_project/command/step_4.png)
 
-!!! summary ""
+!!! abstract ""
     **5)** Click on the newly created **DesiredCommandName.java** (or **DriveArcade.java** if you named it that)
 
 	![](../assets/images/new_project/command/step_5.png)

docs/programming/pneumatics.md

@@ -39,7 +39,7 @@ See [Creating a New Subsystem](new_project.md#creating-a-new-subsystem){target=_
 
 ### What will be added to the Shooter subsystem
 
-!!! summary ""
+!!! abstract ""
     **1)** 
 
     - Create a new Shooter subsystem.
@@ -50,7 +50,7 @@ See [Creating a New Subsystem](new_project.md#creating-a-new-subsystem){target=_
 	   - Port 1 and Port 2 refer to Forward control and Reverse control ports on the PCM.
 	   - Like all ports we use, we will store this in the RobotMap.
 
-!!! summary ""
+!!! abstract ""
     **2)** Create your DoubleSolenoid named pitchSolenoid now using the same technique used to create a talon but replacing Talon with DoubleSolenoid. (For single solenoids just use Solenoid).
 
 ??? Example
@@ -104,10 +104,10 @@ See [Creating a New Subsystem](new_project.md#creating-a-new-subsystem){target=_
 
 ### Creating Pitch Up/Down Methods
 
-!!! summary ""
+!!! abstract ""
     **1)** Create a public void method called pitchUp.
 
-!!! summary ""   
+!!! abstract ""   
     **2)** Inside type:
 
     ```java
@@ -118,7 +118,7 @@ See [Creating a New Subsystem](new_project.md#creating-a-new-subsystem){target=_
       !!! note
 	if you wanted multiple solenoids to deploy at the same time also have them do .set(Value.kForward);
 
-!!! summary ""   
+!!! abstract ""   
     **3)** Do the same for the **pitchDown** method but change **kForward** to **kReverse**.
 
 ??? Example
@@ -144,18 +144,18 @@ See [Creating a New Subsystem](new_project.md#creating-a-new-subsystem){target=_
    - **InstantCommands** work the same as regular commands but hide everything except for initialize(). (InstantCommand extends Command)
    - Internally, they set isFinished to return always true so execute never runs.
 
-!!! summary ""   
+!!! abstract ""   
     **1)** Create a new **InstantCommand** called **ShooterUp**
 
     - Alternatively: Create a regular **Command** and set **isFinished** to **true**
 
-!!! summary ""
+!!! abstract ""
     **2)** In the constructor adds requires(Robot.m_shooter)
 
-!!! summary ""
+!!! abstract ""
     **3)** In initialize() add our newly created method **pitchUp** method 
 
-!!! summary ""
+!!! abstract ""
     **4)** Repeat steps for **ShooterDown** command but change **pitchUp* to **pitchDown**
 
 ??? Example
@@ -229,13 +229,13 @@ See [Creating a New Subsystem](new_project.md#creating-a-new-subsystem){target=_
 - Now that we have created our ShooterUp and ShooterDown commands we need a way to run them. 
 - Lets map them to buttons on our controller!
 
-!!! summary ""
+!!! abstract ""
     **1)** Open OI.java
 
-!!! summary ""
+!!! abstract ""
       **2)** Under our created joystick we will create Button variables and assign them to a button on our joystick 
 
-!!! summary ""
+!!! abstract ""
       **3)** Type: 
 
     ```java
@@ -244,7 +244,7 @@ See [Creating a New Subsystem](new_project.md#creating-a-new-subsystem){target=_
 
 	 - This creates a new Button named D1 (D representing driverController and 1 representing the button number) and sets it as a JoystickButton on the controller ‘driverController’ and button value 1 (this can be found in the Driverstation software). 
 
-!!! summary ""
+!!! abstract ""
 	 **4)** Do this for the rest of the buttons on your controller.
 
 ??? Example
@@ -282,10 +282,10 @@ See [Creating a New Subsystem](new_project.md#creating-a-new-subsystem){target=_
 
 - Now that we have created the buttons in the code we can map certain commands to them. 
 
-!!! summary ""
+!!! abstract ""
     **1)** Create a constructor for OI 
 
-!!! summary ""
+!!! abstract ""
      **2)** In the constructor type: 
 
     ```java
@@ -295,7 +295,7 @@ See [Creating a New Subsystem](new_project.md#creating-a-new-subsystem){target=_
        - This means **when** the button D1 is **pressed** it runs the ShooterUp command and deploys our pneumatic piston. 
        - There are other types of activations for buttons besides **whenPressed** like: **whenRelease, whileHeld, etc**. 
 
-!!! summary ""
+!!! abstract ""
     **3)** Create a whenPressed button for ShooterDown as well
 
 ??? Example