diff --git a/content/departments/data-analytics/how-to-airgap-disable-telemetry.md b/content/departments/data-analytics/how-to-airgap-disable-telemetry.md
index 425fa32f02ce..93917370d967 100644
--- a/content/departments/data-analytics/how-to-airgap-disable-telemetry.md
+++ b/content/departments/data-analytics/how-to-airgap-disable-telemetry.md
@@ -13,7 +13,7 @@ For recent versions of Sourcegraph, disabling either form of usage data collecti
 
 1. First, the customer must receive a [license key that has the appropriate tag(s) that permit "air gapped" usage](../technical-success/ce/process/license_key). Currently, the options that permit portions of this are "Allow air gapped", "Allow disable telemetry export", and any enterprise plans that explicitly permit "air gapped" usage.
 
-  - When this license key tag is applied to the customer instance, event-level telemetry exports (#2 in the [list above](#types-of-usage-data-we-collect)) will be automatically stopped.
+- When this license key tag is applied to the customer instance, event-level telemetry exports (#2 in the [list above](#types-of-usage-data-we-collect)) will be automatically stopped.
 
 2. Second, the customer may actually "air gap" their instance at this point. If they do so (e.g., via networking rules that disallow connections to Sourcegraph.com and other Sourcegraph-managed URLs), then by default all forms of usage data collection will be stopped.