diff --git a/docs/vendor/telemetry-air-gap.mdx b/docs/vendor/telemetry-air-gap.mdx
index 838d34ba22..3d45b1feab 100644
--- a/docs/vendor/telemetry-air-gap.mdx
+++ b/docs/vendor/telemetry-air-gap.mdx
@@ -1,13 +1,9 @@
 import AirGapTelemetry from "../partials/instance-insights/_airgap-telemetry.mdx"
 
-# Collecting Telemetry for Air Gap Instances (Beta)
+# Collecting Telemetry for Air Gap Instances
 
 This topic describes how to collect telemetry for instances in air gap environments.
 
-:::note
-Air gap telemetry is in beta. The functionality, requirements, and limitations of air gap telemetry are subject to change.
-:::
-
 ## Overview
 
 Air gap instances run in environments without outbound internet access. This limitation prevents these instances from periodically sending telemetry to the Replicated Vendor Portal through the Replicated SDK or Replicated KOTS. For more information about how the Vendor Portal collects telemetry from online (internet-connected) instances, see [About Instance and Event Data](/vendor/instance-insights-event-data#about-reporting).
diff --git a/static/images/airgap-upload-telemetry.png b/static/images/airgap-upload-telemetry.png
index 17599a286a..b0589b92bf 100644
Binary files a/static/images/airgap-upload-telemetry.png and b/static/images/airgap-upload-telemetry.png differ