Add link to known issues on I2C HW page (#1751)

Fix links to I2C alternatives on Known Issues

Author: sciencewhiz

source/docs/hardware/sensors/serial-buses.rst

@@ -33,6 +33,8 @@ To communicate to peripheral devices over I2C, each pin should be wired to its c
 
 The I2C bus can also be used through the `MXP expansion port`_. The I2C bus on the MXP is independent. For example, a device on the main bus can have the same ID as a device on the MXP bus.
 
+.. warning:: Be sure to familiarize yourself on the following known issue before using the onboard I2C port: :ref:`docs/yearly-overview/known-issues:Onboard I2C Causing System Lockups`
+
 SPI
 ---
 

source/docs/yearly-overview/known-issues.rst

@@ -17,8 +17,8 @@ Onboard I2C Causing System Lockups
 
 Several alternatives exist for accessing the REV color sensor without using the roboRIO I2C port. A similar approach could be used for other I2C sensors.
 
-- Use a `Raspberry Pi Pico <https://github.com/ThadHouse/picocolorsensor/>`. Supports up to 2 REV color sensors, sends data to the roboRIO via serial. The Pi Pico is low cost (less than $10) and readily available.
-- Use a `Raspberry Pi <https://github.com/PeterJohnson/rpi-colorsensor/>`. Supports 1-4 color sensors, sends data to the roboRIO via NetworkTables. Primarily useful for teams already using a Raspberry Pi as a coprocessor.
+- Use a `Raspberry Pi Pico <https://github.com/ThadHouse/picocolorsensor/>`__. Supports up to 2 REV color sensors, sends data to the roboRIO via serial. The Pi Pico is low cost (less than $10) and readily available.
+- Use a `Raspberry Pi <https://github.com/PeterJohnson/rpi-colorsensor/>`__. Supports 1-4 color sensors, sends data to the roboRIO via NetworkTables. Primarily useful for teams already using a Raspberry Pi as a coprocessor.
 
 CAN bus utilization is noisy
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^