Fix vale and style issues in Service Ping docs

doc/.vale/gitlab/Acronyms.yml

@@ -70,6 +70,7 @@ exceptions:
   - HDD
   - HEAD
   - HIPAA
+  - HLL
   - HTML
   - HTTP
   - HTTPS

doc/development/query_performance.md

@@ -21,7 +21,7 @@ When you are optimizing your SQL queries, there are two dimensions to pay attent
 | Queries in a migration | `100ms` | This is different than the total [migration time](migration_style_guide.md#how-long-a-migration-should-take). |
 | Concurrent operations in a migration | `5min` | Concurrent operations do not block the database, but they block the GitLab update. This includes operations such as `add_concurrent_index` and `add_concurrent_foreign_key`. |
 | Background migrations | `1s` |  |
-| Service Ping | `1s` | See the [Service Ping docs](service_ping/index.md#developing-and-testing-service-ping) for more details. |
+| Service Ping | `1s` | See the [Service Ping docs](service_ping/index.md#develop-and-test-service-ping) for more details. |
 
 - When analyzing your query's performance, pay attention to if the time you are seeing is on a [cold or warm cache](#cold-and-warm-cache). These guidelines apply for both cache types.
 - When working with batched queries, change the range and batch size to see how it effects the query timing and caching.

doc/development/service_ping/review_guidelines.md

@@ -51,7 +51,7 @@ are regular backend changes.
 #### The Product Intelligence **reviewer** should
 
 - Perform a first-pass review on the merge request and suggest improvements to the author.
-- Check the [metrics location](index.md#1-naming-and-placing-the-metrics) in
+- Check the [metrics location](index.md#1-name-and-place-the-metric) in
   the Service Ping JSON payload.
 - Suggest that the author checks the [naming suggestion](index.md#how-to-get-a-metric-name-suggestion) while
   generating the metric's YAML definition.