Update helpdesk docs

docs/competition/team-support/helpdesk.md

@@ -20,7 +20,7 @@ Helpdesk is the teams' primary source of support. Volunteers are expected to adv
 * Radio
 * Spare robot flags for teams to borrow to try for size (must not leave helpdesk)
 * Spare robot flag pipe fittings to give to teams
-* Saturday evening battery/charger loan form
+* Battery / charger loan form
 
 ## Volunteer Requirements
 
@@ -36,19 +36,21 @@ Almost all of Helpdesk's operations are covered by the following procedures.
 
 Whenever a team comes to Helpdesk with an issue that cannot be solved instantly, create a [ticket](./ticket-system.md). This ensures that no problems get dropped while they are being investigated. When the issue is resolved the ticket will be closed.
 
-### Handling of requests for robot safety checks
+### Robot safety checks
 
 The robots require safety checking before they are allowed to compete in the competition. Teams will not be given their hi-viz vest until their robot has passed the safety check procedure. Helpdesk volunteers should perform a safety check according to the [safety checklist](https://docs.google.com/document/d/1psLhgLw21m1u2BwGJHi6IEMYQTLhcjWmQdhJ_6tLQUE/edit) and record the result.
 
-### Handling of general robot development requests
+Regulations checks will be done by other volunteers visiting a team in their pit. Helpdesk volunteers do not need to do regulations checks, but may need to answer questions.
+
+### General robot development queries
 
 Many teams will come to Helpdesk requesting help with the development of their robot or, more likely, help using the Student Robotics kit and associated software. As mentioned earlier, Helpdesk volunteers are not expected to tell teams what to do, but rather offer advice. Helpdesk volunteers should strive to answer questions about the use of the kit and software.
 
 Some queries may require a volunteer to visit the team in their pit to observe behaviour in situ. This must only be done by a Helpdesk volunteer if it will leave no fewer than two volunteers actively manning Helpdesk.
 
 In some rare situations it may be necessary to request the assistance of a person with more in-depth knowledge of the kit to help solve an issue. Escalate the issue to the head helpdesker.
 
-### Handling suspected damaged kit requests
+### Suspected damaged kit
 
 If a team comes to Helpdesk with a suspicion of some of the Student Robotics kit being damaged then the following procedure should be followed:
 
@@ -58,25 +60,27 @@ If a team comes to Helpdesk with a suspicion of some of the Student Robotics kit
  1. Request that the team tests the device in question with a very simple code project that only attempts to control that one device.
  1. If all previous steps indicate that the device is probably faulty then continue with the kit swap procedure.
 
-### Swapping out kit
+#### Swapping out kit
 
 After determining that a piece of kit is most likely faulty it must be swapped with a working spare. Helpdesk has a supply of spare kit. To swap a piece of kit please fill in a [Kit Swap Form](https://docs.google.com/document/d/1X4ewwhkTFKfCzQjlIUS-90ZhcFHzashRhz_kXnUlxjE/edit?usp=sharing) and follow the instructions on there. Since there is a limited quantity of spare kit, all attempts must be made to verify that the issue being observed is not caused by something else.
 
 ### Swapping out batteries
 
 See [Battery charging](./battery-charging.md#swapping-a-teams-battery-helpdesk)
 
-### Handling requests for batteries/chargers/bags on Saturday evening
+### Requests for batteries / chargers / bags on Saturday evening
 
 See [Overnight battery loan](./overnight-battery-loan.md).
 
-### Handling requests for flag fittings
+### Flag fittings
 
 Teams may request a pipe connector to use on their robot for the purpose of attaching the robot flags. As we have a limited supply, make sure that you only let each team only take one, so that they can't keep coming back for more.
 
 Also, please show teams how to remove the fittings, as they are very strong and need to be released in the correct way (Press down on the center ring)
 
-### Handling of team name changes
+Also on helpdesk is an example flag teams can use to test their mounts. These example flags should not leave helpdesk.
+
+### Team name changes
 
 Teams are allowed to request that the name on the scoreboard is changed. This is an action that needs to be performed by a volunteer that is trained to use the SRComp software or GitHub repository.
 
@@ -85,13 +89,13 @@ Changes of name should be reviewed by the team supervisor before being actioned,
 !!! note
     The name is the name of their "team" not the name of their "robot".
 
-### Handling of teams leaving early
+### Teams leaving early
 
 If a team wishes to leave early, they must [return their kit](./kit-return.md) to helpdesk.
 
 If a team wants to leave before the knockouts begin, contact the Event Coordinator.
 
-### Frequently Asked Questions
+## Frequently Asked Questions
 
 Based on issues handled in previous years, the following may be helpful: