anchor.diff:  . Follow the instructions and download CubeMX.
   
   . Extract files from `.zip` file using a preferred method.
  -For example `unzip file.zip -d Destination_folder`.
  +For example, use `unzip file.zip -d Destination_folder`.
   
   . Navigate to the directory the files were extracted to.
   
  -. Run *SetupSTM32CubeMX-VERSION.linux* `./SetupSTM32CubeMX-{var}.linux` where  {var} is the version of CubeMx that is being installed.
  +. Run *SetupSTM32CubeMX-VERSION.linux* using `./SetupSTM32CubeMX-{var}.linux` where  {var} is the version of CubeMx that is being installed.
   
   . Follow the instructions in the Installation Wizard.
   
  
positive.code: 
  . Go to UCSolarCarTeam repo > Recruit Resources, and clone.
  
  . Navigate to STM32F4Discovery-Resources and run the auto installer `sudo ./install.sh`. 
  This will should download STLink, gcc4mbed, and CubeMX2Makefile and add them all to the path.
  
  . Check to make sure all of them were added by using a preferred text editor.
  For example, `nano ~/.profile`.
  If any of them are missing add them to the path.
  
  .. Add them by copying  `export PATH=$PATH:/opt/CubeMX2Makefile`, `export PATH=$PATH:/opt/stlink`, or `export PATH=$PATH:/opt/gcc4mbed`  in `.profile`.
  
  .. Save, exit, and source `source ~/.profile`.
  
  . http://www.st.com/en/development-tools/stm32cubemx.html[Go to the download page of the official ST website by clicking this link^].
  
  
negative.code: 
  . Click OK and download any dependencies that are needed, then click OK again.
  
  . Make pin assignments then go to Project > Generate Code, and then save project.
  
  
  == Generating a Makefile and Compiling
  . Create the makefile using  `/usr/local/bin/CubeMX2Makefile /path/to/project/folder`.
  
  . Go to the directory that the Makefile was made then compile using `make`.
  
  . Navigate to the build directory and there should be a `<project>.bin` file. Where `<project>` is the project name. 
  
  == Flashing
  Flashing is how the `.bin` that was made is put onto the board. This is how the processor on the board is able to carry out the instructions that were generated from the code.
  
  To flash the board use `/usr/local/bin/st-flash write /path/to/project/build/<project>.bin 0x8000000`.
  
  If a board isn't connected, and it ran successfully, the output should be: 
  ----
  st-flash 1.3.0-dev
  DATE/TIME WARN /opt/stlink/src/usb.c: Couldn't find any ST-Link/V2 devices
  