Merge branch 'eread/fix-build-warnings' into 'master'

Fix documentation build errors

See merge request gitlab-org/gitlab!59950

doc/development/snowplow/index.md

@@ -114,13 +114,13 @@ The current method provides several attributes that are sent on each click event
 
 | category* | label            | action                | property** | value |
 |-------------|------------------|-----------------------|----------|:-----:|
-| [root:index] | main_navigation            | click_navigation_link | `[link_label]`   | - |
-| [groups:boards:show] | toggle_swimlanes | click_toggle_button | - | `[is_active]` |
-| [projects:registry:index] | registry_delete | click_button | - | - |
-| [projects:registry:index] | registry_delete | confirm_deletion | - | - |
-| [projects:blob:show] | congratulate_first_pipeline | click_button | `[human_access]` | - |
-| [projects:clusters:new] | chart_options | generate_link | `[chart_link]` | - |
-| [projects:clusters:new] | chart_options | click_add_label_button | `[label_id]` | - |
+| `[root:index]` | `main_navigation`            | `click_navigation_link` | `[link_label]`   | - |
+| `[groups:boards:show]` | `toggle_swimlanes` | `click_toggle_button` | - | `[is_active]` |
+| `[projects:registry:index]` | `registry_delete` | `click_button` | - | - |
+| `[projects:registry:index]` | `registry_delete` | `confirm_deletion` | - | - |
+| `[projects:blob:show]` | `congratulate_first_pipeline` | `click_button` | `[human_access]` | - |
+| `[projects:clusters:new]` | `chart_options` | `generate_link` | `[chart_link]` | - |
+| `[projects:clusters:new]` | `chart_options` | `click_add_label_button` | `[label_id]` | - |
 
 _* It's ok to omit the category, and use the default._<br>
 _** Property is usually the best place for variable strings._

doc/development/usage_ping/index.md

@@ -913,9 +913,9 @@ On GitLab.com, the Product Intelligence team regularly monitors Usage Ping. They
 
 To set up Usage Ping locally, you must:
 
-1. [Set up local repositories]#(set-up-local-repositories)
-1. [Test local setup](#test-local-setup)
-1. (Optional) [Test Prometheus-based usage ping](#test-prometheus-based-usage-ping)
+1. [Set up local repositories](#set-up-local-repositories).
+1. [Test local setup](#test-local-setup).
+1. (Optional) [Test Prometheus-based usage ping](#test-prometheus-based-usage-ping).
 
 #### Set up local repositories
 

doc/user/project/issues/managing_issues.md

@@ -74,8 +74,9 @@ To visit the issue tracker for all projects in your group:
 1. Go to the group dashboard.
 1. In the left sidebar, select **Issues**.
 1. In the top-right, select the **Select project to create issue** button.
-1. Select the project you'd like to create an issue for. The button now appears as **New issue in <selected project>**.
-1. Select **New issue in <selected project>**.
+1. Select the project you'd like to create an issue for. The button now reflects the selected
+   project.
+1. Select the button to create an issue in the selected project.
 
 ![Select project to create issue](img/select_project_from_group_level_issue_tracker_v13_11.png)