Merge branch 'selhorn-related-topics-update' into 'master'

Renamed related links to related topics

See merge request gitlab-org/gitlab!75674

doc/api/status_checks.md

@@ -145,6 +145,6 @@ PUT /projects/:id/external_status_checks/:check_id
 | `external_url`         | string           | no       | URL of external status check resource          |
 | `protected_branch_ids` | `array<Integer>` | no       | IDs of protected branches to scope the rule by |
 
-## Related links
+## Related topics
 
 - [External status checks](../user/project/merge_requests/status_checks.md).

doc/api/v3_to_v4.md

@@ -11,7 +11,7 @@ The GitLab API v3 was [removed](https://gitlab.com/gitlab-org/gitlab-foss/-/issu
 
 For information about the current version of the GitLab API, read the [API documentation](index.md).
 
-## Related links
+## Related topics
 
 - [GitLab v3 API documentation](https://gitlab.com/gitlab-org/gitlab-foss/-/blob/8-16-stable/doc/api/index.md)
 - [Migration guide](https://gitlab.com/gitlab-org/gitlab-foss/-/blob/11-0-stable/doc/api/v3_to_v4.md) from

doc/integration/datadog.md

@@ -46,6 +46,6 @@ project, group, or instance level:
 When the integration sends data, you can view it in the [CI Visibility](https://app.datadoghq.com/ci)
 section of your Datadog account.
 
-## Related links
+## Related topics
 
 - [Datadog's CI Visibility](https://docs.datadoghq.com/continuous_integration/) documentation.

doc/topics/git/cherry_picking.md

@@ -74,7 +74,7 @@ into a different branch (`stable`):
    git cherry-pick <SHA>
    ```
 
-## Related links
+## Related topics
 
 - Cherry-pick commits with [the Commits API](../../api/commits.md#cherry-pick-a-commit)
 - Git documentation [for cherry-picks](https://git-scm.com/docs/git-cherry-pick)

doc/user/project/issues/confidential_issues.md

@@ -88,7 +88,7 @@ sees in the project's search results respectively.
 |:---------------------------------------------------------------------------------------|:---------------------------------------------------------------------------------|
 | ![Confidential issues search by maintainer](img/confidential_issues_search_master.png) | ![Confidential issues search by guest](img/confidential_issues_search_guest.png) |
 
-## Related links
+## Related topics
 
 - [Merge requests for confidential issues](../merge_requests/confidential.md)
 - [Make an epic confidential](../../group/epics/manage_epics.md#make-an-epic-confidential)

doc/user/project/merge_requests/approvals/index.md

@@ -105,7 +105,7 @@ Without the approvals, the work cannot merge. Required approvals enable multiple
 - [Require approval from a security team](../../../application_security/index.md#security-approvals-in-merge-requests)
   before merging code that could introduce a vulnerability. **(ULTIMATE)**
 
-## Related links
+## Related topics
 
 - [Merge request approvals API](../../../../api/merge_request_approvals.md)
 - [Instance-level approval rules](../../../admin_area/merge_requests_approvals.md) for self-managed installations

doc/user/project/merge_requests/approvals/settings.md

@@ -157,7 +157,7 @@ You can also enforce merge request approval settings:
 If the settings are inherited by a group or project, they cannot be changed in the group or project
 that inherited them.
 
-## Related links
+## Related topics
 
 - [Instance-level merge request approval settings](../../../admin_area/merge_requests_approvals.md)
 - [Compliance report](../../../compliance/compliance_report/index.md)

doc/user/project/merge_requests/cherry_pick_changes.md

@@ -79,7 +79,7 @@ merge request is from a fork:
 1. (Optional) Select **Start a new merge request** if you're ready to create a merge request.
 1. Click **Cherry-pick**.
 
-## Related links
+## Related topics
 
 - The [Commits API](../../../api/commits.md) enables you to add custom messages
   to changes you cherry-pick through the API.

doc/user/project/merge_requests/confidential.md

@@ -70,7 +70,7 @@ Open a merge request
 - You are satisfied the problem is resolved in your private fork.
 - You are ready to make the confidential commits public.
 
-## Related links
+## Related topics
 
 - [Confidential issues](../issues/confidential_issues.md)
 - [Make an epic confidential](../../group/epics/manage_epics.md#make-an-epic-confidential)

doc/user/project/merge_requests/reviews/suggestions.md

@@ -144,6 +144,6 @@ to your branch to address your reviewers' requests.
 WARNING:
 Suggestions applied from multiple authors creates a commit authored by the user applying the suggestions.
 
-## Related links
+## Related topics
 
 - [Suggestions API](../../../../api/suggestions.md)

doc/user/project/merge_requests/status_checks.md

@@ -181,6 +181,6 @@ You should:
 - Check the [GitLab status page](https://status.gitlab.com/) if the problem persists,
   to see if there is a wider outage.
 
-## Related links
+## Related topics
 
 - [External status checks API](../../../api/status_checks.md)

doc/user/project/repository/index.md

@@ -248,9 +248,19 @@ When you [rename a user](../../profile/index.md#change-your-username),
 - The redirects are available as long as the original path is not claimed by
   another group, user, or project.
 
-## Related links
+## Related topics
 
-- [GitLab Workflow VS Code extension](vscode.md)
+- [GitLab Workflow VS Code extension](vscode.md).
+- To lock files and prevent change conflicts, use [file locking](../file_lock.md).
+- [Repository API](../../../api/repositories.md).
+- [Find files](file_finder.md) in a repository.
+- [Branches](branches/index.md).
+- [File templates](web_editor.md#template-dropdowns).
+- [Create a directory](web_editor.md#create-a-directory).
+- [Start a merge request](web_editor.md#tips).
+- [Find file history](git_history.md).
+- [Identify changes by line (Git blame)](git_blame.md).
+- [Use Jupyter notebooks with GitLab](jupyter_notebooks/index.md).
 
 ## Troubleshooting
 
@@ -287,16 +297,3 @@ The same approach should also allow misidentified file types to be fixed.
    ```
 
   `*.txt` files have an entry in the heuristics file. This example prevents parsing of these files.
-
-## Related topics
-
-- To lock files and prevent change conflicts, use [file locking](../file_lock.md).
-- [Repository API](../../../api/repositories.md).
-- [Find files](file_finder.md) in a repository.
-- [Branches](branches/index.md).
-- [File templates](web_editor.md#template-dropdowns).
-- [Create a directory](web_editor.md#create-a-directory).
-- [Start a merge request](web_editor.md#tips).
-- [Find file history](git_history.md).
-- [Identify changes by line (Git blame)](git_blame.md).
-- [Use Jupyter notebooks with GitLab](jupyter_notebooks/index.md).

doc/user/project/time_tracking.md

@@ -123,7 +123,7 @@ To do so:
 
 With this option enabled, `75h` is displayed instead of `1w 4d 3h`.
 
-## Related links
+## Related topics
 
 - [Time tracking solutions page](https://about.gitlab.com/solutions/time-tracking/)
 - Time tracking GraphQL references: