Merge branch 'PhotonVision:main' into jetson-orin

Author: ryanshoff

docs/.styleguide

@@ -12,5 +12,6 @@ modifiableFileExclude {
   \.ico$
   \.rknn$
   \.svg$
+  \.woff2$
   gradlew
 }

docs/source/_static/css/pv-icons.css

@@ -1,16 +1,3 @@
-/*!
- *  Font Awesome 4.7.0 by @davegandy - http://fontawesome.io - @fontawesome
- *  License - http://fontawesome.io/license (Font: SIL OFL 1.1, CSS: MIT License)
- */
-
-@font-face {
-    font-family: FontAwesome;
-    src: url(fonts/fontawesome-webfont.eot?674f50d287a8c48dc19ba404d20fe713);
-    src: url(fonts/fontawesome-webfont.eot?674f50d287a8c48dc19ba404d20fe713?#iefix&v=4.7.0) format("embedded-opentype"), url(fonts/fontawesome-webfont.woff2?af7ae505a9eed503f8b8e6982036873e) format("woff2"), url(fonts/fontawesome-webfont.woff?fee66e712a8a08eef5805a46892932ad) format("woff"), url(fonts/fontawesome-webfont.ttf?b06871f281fee6b241d60582ae9369b9) format("truetype"), url(fonts/fontawesome-webfont.svg?912ec66d7572ff821749319396470bde#fontawesomeregular) format("svg");
-    font-weight: 400;
-    font-style:normal
-}
-
 .code-block-caption>.headerlink, dl dt>.headerlink, h1>.headerlink, h2>.headerlink, h3>.headerlink, h4>.headerlink, h5>.headerlink, h6>.headerlink, p.caption>.headerlink, table>caption>.headerlink {
     font-family: FontAwesome;
     font-size: 0.75em;

docs/source/_static/css/v4-font-face.min.css

@@ -79,6 +79,7 @@
 
 
 def setup(app):
+    app.add_css_file("css/v4-font-face.min.css")
     app.add_css_file("css/pv-icons.css")
 
 

docs/source/_static/webfonts/fa-brands-400.woff2

@@ -15,7 +15,7 @@ SSH into the Raspberry Pi (using Windows command line, or a tool like [Putty](ht
 :::{attention}
 The version of WPILibPi for the Romi is 2023.2.1, which is not compatible with the current version of PhotonVision. **If you are using WPILibPi 2023.2.1 on your Romi, you must install PhotonVision v2023.4.2 or earlier!**
 
-To install a compatible version of PhotonVision, enter these commands in the SSH terminal connected to the Raspberry Pi. This will download and run the install script, which will intall PhotonVision on your Raspberry Pi and configure it to run at startup.
+To install a compatible version of PhotonVision, enter these commands in the SSH terminal connected to the Raspberry Pi. This will download and run the install script, which will install PhotonVision on your Raspberry Pi and configure it to run at startup.
 
 ```bash
 $ wget https://git.io/JJrEP -O install.sh

docs/source/_static/webfonts/fa-regular-400.woff2

@@ -50,7 +50,7 @@ When a new camera (ie, one we can't match by-path to a deserialized CameraConfig
 
 ## Startup:
 
-- GIVEN An emtpy set of deserialized Camera Configurations
+- GIVEN An empty set of deserialized Camera Configurations
 <br>WHEN PhotonVision starts
 <br>THEN no VisionModules will be started
 
@@ -72,12 +72,12 @@ When a new camera (ie, one we can't match by-path to a deserialized CameraConfig
 
 ## Camera (re)enumeration:
 
-- GIVEN a NEW USB CAMERA is avaliable for enumeration
+- GIVEN a NEW USB CAMERA is available for enumeration
 <br>WHEN a USB camera is discovered by VisionSourceManager
 <br>AND the USB camera's VIDEO DEVICE PATH is not in the set of DESERIALIZED CAMERA CONFIGURATIONS
 <br>THEN a UNIQUE NAME will be assigned to the camera info
 
-- GIVEN a NEW USB CAMERA is avaliable for enumeration
+- GIVEN a NEW USB CAMERA is available for enumeration
 <br>WHEN a USB camera is discovered by VisionSourceManager
 <br>AND the USB camera's VIDEO DEVICE PATH is in the set of DESERIALIZED CAMERA CONFIGURATIONS
 <br>THEN a UNIQUE NAME equal to the matching DESERIALIZED CAMERA CONFIGURATION will be assigned to the camera info
@@ -86,13 +86,13 @@ When a new camera (ie, one we can't match by-path to a deserialized CameraConfig
 ## Creating from a new camera
 
 - Given: A UNIQUE NAME from a NEW USB CAMERA
-<br>WHEN I request a new VisionModule is created for this NEW USB CAMREA
+<br>WHEN I request a new VisionModule is created for this NEW USB CAMERA
 <br>AND the camera has a VALID USB PATH
 <br>AND the camera's VALID USB PATH is not in use by any CURRENTLY ACTIVE CAMERAS
 <br>THEN a NEW VisionModule will be started for the NEW USB CAMERA using the VALID USB PATH
 
 - Given: A UNIQUE NAME from a NEW USB CAMERA
-<br>WHEN I request a new VisionModule is created for this NEW USB CAMREA
+<br>WHEN I request a new VisionModule is created for this NEW USB CAMERA
 <br>AND the camera does not have a VALID USB PATH
 <br>AND the camera's VIDEO DEVICE PATH is not in use by any CURRENTLY ACTIVE CAMERAS
 <br>THEN a NEW VisionModule will be started for the NEW USB CAMERA using the VIDEO DEVICE PATH