Update f1tenth-sim-racing-rules.md

docs/competitions/f1tenth-sim-racing-rules.md

@@ -160,8 +160,7 @@ Each team is expected to submit a containerized version of their autonomous raci
 </p>
 
 !!! note
-    We expect that upon running your submitted container, all the necessary nodes should start up (the `autodrive_devkit` API we have included as well as your team's racing stack). Once we hit the `Connection Button` on the `Menu Panel` of AutoDRIVE Simulator, the simulated vehicle should start running. Please refer to the [competition rules](https://autodrive-ecosystem.github.io/competitions/f1tenth-sim-racing-rules), where it talks about the [submission requirements](https://autodrive-ecosystem.github.io/competitions/f1tenth-sim-racing-rules/#31-submission-requirements) and [submission process](https://autodrive-ecosystem.github.io/competitions/f1tenth-sim-racing-rules/#32-submission-process).
-Please make sure that you include all the necessary commands (for sourcing workspaces, setting environment variables, launching nodes, etc.) within the `entrypoint` script (`autodrive_devkit.sh` file) provided within the `autodrive_f1tenth_api` container. Please do **NOT** use `~/.bashrc` or other means to automate the algorithm execution! Competition organizers should be able to start additional bash session(s) within your submitted container (without your codebase executing every time a new bash session is initialized) for data recording and inspection purposes.
+    We expect that upon running your submitted container, all the necessary nodes should start up (the `autodrive_devkit` API we have included as well as your team's racing stack). Once we hit the `Connection Button` on the `Menu Panel` of AutoDRIVE Simulator, the simulated vehicle should start running. Please make sure that you include all the necessary commands (for sourcing workspaces, setting environment variables, launching nodes, etc.) within the `entrypoint` script (`autodrive_devkit.sh` file) provided within the `autodrive_f1tenth_api` container. Please do **NOT** use `~/.bashrc` or other means to automate the algorithm execution! Competition organizers should be able to start additional bash session(s) within your submitted container (without your codebase executing every time a new bash session is initialized) for data recording and inspection purposes.
 
 ### 3.1. Submission Requirements