Merge pull request #1942 from brizental/fix-del-req-path

docs/user/SUMMARY.md

@@ -19,7 +19,7 @@
     - [Testing custom pings](user/pings/testing-custom-pings.md)
     - [Pings sent by Glean](user/pings/sent-by-glean.md)
         - [Baseline Ping](user/pings/baseline.md)
-        - [Deletion Request Ping](user/pings/deletion_request.md)
+        - [Deletion Request Ping](user/pings/deletion-request.md)
         - [Events Ping](user/pings/events.md)
         - [Metrics Ping](user/pings/metrics.md)
         - [Schedules and timings overview](user/pings/ping-schedules-and-timings.md)

docs/user/reference/general/initializing.md

@@ -21,7 +21,7 @@ The following steps are required for applications using the Glean SDK, but not l
 > `Glean.initialize` must **always** be called with real values.
 > Always pass the user preference, e.g. `Glean.initialize(upload=userSettings.telemetry_enabled)` or the equivalent for your application.
 > Never call `Glean.initialize(upload=true)` if `true` is a placeholder value that later gets reset by `Glean.setUploadEnabled(false)`.
-> Depending on the provided placeholder value, this might trigger the generation of new client ids or the submission of bogus [`deletion-request` pings](../../user/pings/deletion_request.md).
+> Depending on the provided placeholder value, this might trigger the generation of new client ids or the submission of bogus [`deletion-request` pings](../../user/pings/deletion-request.md).
 
 {{#include ../../../shared/tab_header.md}}
 

docs/user/reference/general/toggling-upload-status.md

@@ -10,7 +10,7 @@ provide some form of user interface to allow for toggling the upload status.
 
 When upload is disabled, the Glean SDK will perform the following tasks:
 
-1. Submit a [`deletion-request`](../../user/pings/deletion_request.md) ping.
+1. Submit a [`deletion-request`](../../user/pings/deletion-request.md) ping.
 2. Cancel scheduled ping uploads.
 3. Clear metrics and pings data from the client, except for the
   [`first_run_date` and `first_run_hour`](../../user/pings/index.html#the-client_info-section) metrics.

docs/user/user/pings/deletion_request.md → docs/user/user/pings/deletion-request.md

@@ -32,7 +32,7 @@ As such it attempts to send itself at the moment the user opts out of data colle
 
 | SDK | Kotlin | Swift | Python | Rust | JavaScript | Firefox Desktop |
 |-:|:-:|:-:|:-:|:-:|:-:|:-:|
-| [`deletion-request` ping](deletion_request.md) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
+| [`deletion-request` ping](deletion-request.md) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
 
 ## Scheduling
 

docs/user/user/pings/sent-by-glean.md

@@ -3,7 +3,7 @@
 If data collection is enabled, the Glean SDKs provide a set of built-in pings that are assembled out of the box without any developer intervention.  The following is a list of these built-in pings:
 
 - [`baseline` ping](baseline.md): A small ping sent every time the application goes to foreground and background. Going to foreground also includes when the application starts.
-- [`deletion-request` ping](deletion_request.md): Sent when the user disables telemetry in order to request a deletion of their data.
+- [`deletion-request` ping](deletion-request.md): Sent when the user disables telemetry in order to request a deletion of their data.
 - [`events` ping](events.md): The default ping for events. Sent every time the application goes to background or a certain number of events is reached.
 - [`metrics` ping](metrics.md): The default ping for metrics. Sent approximately daily.
 
@@ -13,7 +13,7 @@ There is also a [high-level overview](ping-schedules-and-timings.html) of how th
 
 ### Available pings per platform
 
-| SDK | [`baseline`](baseline.md) | [`deletion-request`](deletion_request.md) | [`events`](events.md) | [`metrics`](metrics.md) |
+| SDK | [`baseline`](baseline.md) | [`deletion-request`](deletion-request.md) | [`events`](events.md) | [`metrics`](metrics.md) |
 |-:|:-:|:-:|:-:|:-:|
 | Kotlin | ✅ | ✅ | ✅ | ✅ |
 | Swift | ✅ | ✅ | ✅ | ✅ |