Update releasing-fleet (#34937)

docs/Contributing/workflows/releasing-fleet.md

@@ -158,7 +158,8 @@ The following version of Fleet's agent (`fleetd`) support the latest changes to
 <UPDATE VERSIONS AND LINKS BELOW>
 1. [orbit-v1.x.x](https://github.com/fleetdm/fleet/releases/tag/orbit-v1.x.x)
 2. `fleet-desktop-v1.x.x` (included with Orbit)
-3. [fleetd-chrome-v1.x.x](https://github.com/fleetdm/fleet/releases/tag/fleetd-chrome-v1.x.x)
+3. `osquery-x.x.x`
+4. [fleetd-chrome-v1.x.x](https://github.com/fleetdm/fleet/releases/tag/fleetd-chrome-v1.x.x)
 
 > While newer versions of `fleetd` still function with older versions of the Fleet server (and vice versa), Fleet does not actively test these scenarios and some newer features won't be available.
 

orbit/cmd/fleetd_tables/README.md

@@ -1,7 +1,8 @@
 # Fleet osquery extensions without fleetd
 
-If you are interested in getting some of the `fleetd` tables but cannot run `fleetd` natively then its possible
-to utilize this "fleetd_tables" extension with standalone `osqueryd`.
+Fleet adds tables in addition to those available in osquery.
+
+If you're deploying plain osquery, the best practice is to build and deploy this fleetd_tables osquery extension each time you upgrade Fleet.
 
 ### Building the extension