Stage 1 Proofread

[karlolson5]

Where: https://frcsoftware.org/learning-course/stage1/stage1a/getting-started/

Old:

FRCSoftware focuses two types of vendors: REV and CTRE. [photos] REV uses NEOs and SparkMAXs. CTRE uses Krakens.

Proposed new:

FRCSoftware focuses two vendors: REV and CTRE. [photos] REV uses NEOs (motors) and SparkMAXs. CTRE uses Krakens.

Where: https://frcsoftware.org/learning-course/stage1/stage1a/kitbot-drivetrain/

Old:

The import statement for TalonFX and SparkMax look like ...

Proposed new:

The import statements for TalonFX and SparkMax look like ...

Old:

When creating a motor controller object, the physical motor controller’s CAN ID and the CAN Bus ID are given.

Proposed new:

When creating a motor controller object, the physical motor controller’s CAN Bus ID and CAN ID are given.

Old:

Using the combination of CAN Bus and CAN ID Systemcore can give commands to the correct motor controller.

Proposed new:

Using the combination of CAN Bus and CAN ID, Systemcore can give commands to the correct motor controller.

Old:

For this exercise the motor controllers will have the IDs:

• leftLeader: CAN Bus 0, CAN ID 0
• leftFollower: CAN Bus 0, CAN ID 1
• rightLeader: CAN Bus 0, CAN ID 2
• rightFollower: CAN Bus 0, CAN ID 3

Proposed new:

For this exercise the motor controllers will have the IDs:

• leftLeader: CAN Bus CAN_S0, CAN ID 0
• leftFollower: CAN Bus CAN_S0, CAN ID 1
• rightLeader: CAN Bus CAN_S0, CAN ID 2
• rightFollower: CAN Bus CAN_S0, CAN ID 3

Old:

CTRE uses a CANBus that is constructed with a CANPort enum to specify which of Systemcore's CANBuses the device is connected too. This enum is a field in the CANPort` class and only CAN_S0 through CAN_S4 will ever be used since Systemcore only has five CAN Busses.

Proposed new:

CTRE uses a CANBus that is constructed with a CANPort enum to specify which of Systemcore's CANBuses the device is connected too. This enum is a field in the CANPort class and only CAN_S0 through CAN_S4 will ever be used since Systemcore only has five CAN Busses.

Old:

the invert setting will be true for REV code and Clockwise_Positive for CTRE code ... CounterClockwise_Positive

Proposed new:

the invert setting will be true for REV code and InvertedValue.Clockwise_Positive for CTRE code ... InvertedValue.CounterClockwise_Positive

Where: https://frcsoftware.org/learning-course/stage1/stage1a/simple-auto/

Old:

less time to perform different actions The code for the auto

Proposed new:

less time to perform different actions. The code for the auto

Where: https://frcsoftware.org/learning-course/stage1/stage1a/kitbot-additional-motors/

Old:

The IntakeLauncher motor will be on CAN Bus 0 with a CAN Id of 4 while the Feeder motor will be on CAN Bus 0 with a CAN Id of 5.

Proposed new:

The IntakeLauncher motor will be on CAN Bus CAN_S0 with a CAN Id of 4 while the Feeder motor will be on CAN Bus CAN_S0 with a CAN Id of 5.

Where: https://frcsoftware.org/learning-course/stage1/stage1b/command-based-overview/

Old:

It defines behaviors/actions(tumbling

Proposed new:

It defines behaviors/actions (tumbling

Where: https://frcsoftware.org/learning-course/stage1/stage1b/commands-and-mechanisms/

Old:

The java compiler

Proposed new:

The Java compiler

Where: https://frcsoftware.org/learning-course/stage1/stage1b/triggers/#how-triggers-are-defined

Old:

sources/Triggers, at their core

Proposed new:

Triggers, at their core

Where: https://frcsoftware.org/learning-course/stage1/stage1b/triggers/#controller-based-sourcestriggers

Old:

Controller-based sources/Triggers

Proposed new:

Controller-based Triggers

Where: https://frcsoftware.org/learning-course/stage1/stage1b/suppliers-in-command-based/

Old:

Notice, however, that the expression to the left of the () -> statement is a boolean instead

Proposed new:

Notice, however, that the expression after the () -> statement is a boolean instead