fix: fix grammar issues with formatting (#22808)

docs/docs/telemetry.md

@@ -32,13 +32,13 @@ We use these metrics to better understand the usage patterns. These metrics will
 
 Specifically, we collect the following information for _all_ telemetry events:
 
-- Timestamp of the occurrence
-- Command invoked (e.g. `build` or `develop`)
-- Gatsby machine ID. This is generated with UUID and stored in global gatsby config at ~/.config/gatsby/config.json.
-- Unique session ID. This is generated on each run with UUID.
-- One-way hash of the current working directory or a hash of the git remote
-- General OS level information (operating system, version, CPU architecture, and whether the command is run inside a CI)
-- Current Gatsby version
+- Timestamp of the occurrence.
+- Command invoked (e.g. `build` or `develop`).
+- Gatsby machine ID: This is generated with UUID and stored in global gatsby config at ` ~/.config/gatsby/config.json`.
+- Unique session ID: This is generated on each run with UUID.
+- One-way hash of the current working directory or a hash of the git remote.
+- General OS level information (operating system, version, CPU architecture, and whether the command is run inside a CI).
+- Current Gatsby version.
 
 The access to the raw data is highly controlled, and we cannot identify individual users from the dataset. It is anonymized and untraceable back to the user.