Fix radio status logging docs

Not under the outputs table, so calling it an output isn't really accurate
Mechanical-Advantage · Dec 7, 2024 · 8be8645 · 8be8645
1 parent ee0b61b
commit 8be8645
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/docs/data-flow/built-in-logging.md b/docs/docs/data-flow/built-in-logging.md
@@ -48,7 +48,7 @@ Output from native code is not included when running in simulation.
 
 ### Radio Status
 
-Status data from the VH-109 radio is automatically logged every ~5 seconds as an output. This includes useful information about the connection status, bandwidth usage, etc. These fields are available under the `RadioStatus` table.
+Status data from the VH-109 radio is automatically logged every ~5 seconds. This includes useful information about the connection status, bandwidth usage, etc. These fields are available under the `RadioStatus` table.
 
 ![Radio data](img/radio-1.png)
 

diff --git a/docs/docs/whats-new/index.md b/docs/docs/whats-new/index.md
@@ -101,7 +101,7 @@ The state of any alerts created through WPILib's [persistent alerts](https://doc
 
 ### 📡 Radio Logging
 
-Status data from the VH-109 radio is automatically logged as an output. This includes useful information about the connection status, bandwidth usage, etc. Check the [documentation](/data-flow/built-in-logging#radio-status) for details.
+Status data from the VH-109 radio is automatically logged. This includes useful information about the connection status, bandwidth usage, etc. Check the [documentation](/data-flow/built-in-logging#radio-status) for details.
 
 ![Radio data](../data-flow/img/radio-1.png)