message: docs(contributing): Correct certain commands in our contributing guide
diff: @@ -345,16 +345,29 @@ Not every JavaScript package has an available flow-typed definition. In this cas
  ### Opentrons API
  -Be sure to check out the [API `README`][api-readme] for additional instructions. To run the Opentrons API in development mode:
  +Be sure to check out the [API `README`][api-readme] for additional instructions.
  +
  +### Robot Server
  +
  +To run the Opentrons HTTP API in development mode:
  ```shell
  # run API with virtual robot
  -make -C api dev ENABLE_VIRTUAL_SMOOTHIE=true
  +make -C robot-server dev OT_ROBOT_SERVER_simulator_configuration_file_path=simulators/test.json
  # run API with robot's motor driver connected via USB to UART cable
  -make -C api dev
  +make -C robot-server dev
  ```
  -To put the API on a test robot, if it's on balena do:
  +Generally to test your code on the robot, you will want to push the whole mono-repo to the robot
  +in case there are large differences between your robot's server version and the code you are using
  +from github. You can do this via:
  +
  +```shell
  +# Use this command From the top level opentrons folder
  +make push host=${some_other_ip_address}
  +```
  +
  +To put the robot server on a test robot, if it's on buildroot do:
  ```shell
  # push the current contents of the api directory to robot for testing
  @@ -387,7 +400,7 @@ If `make term` complains about not having a key, you may need to install a publi
  ```shell
  ssh-keygen # note the path you save the key to
  -make -C api install-key br_ssh_pubkey=/path/to/pubkey
  +make -C robot-server install-key br_ssh_pubkey=/path/to/pubkey host=${some_other_ip_address}
  ```
  and subsequently, when you do `make term`, add the `br_ssh_key=/path/to/key` option:
  @@ -422,7 +435,7 @@ Buildroot robots use [systemd-journald][] for log management. This is a single l
  ### State Management
  -#### Balena
  +#### Balena (Deprecated after Robot Server Version 3.11.0)
  You can't really restart anything from inside a shell on balena, since it all runs in a docker container. Instead, you can do `restart` and restart the docker container, but this will disconnect you. Stop ongoing processes by doing `ps`, finding the pid, and then doing `kill (pid)`. This can be useful to temporarily run one of the servers directly, to see what it prints out on the command line. Note that when you do this the environment won't be quite the same as what the server sees when it is run directly by balena due to the implementation details of `docker run`, `tini`, and our start scripts.
  