Merge branch 'docs-quick-actions-update' into 'master'

General style updates for Quick Actions page

See merge request gitlab-org/gitlab!56134

doc/user/group/epics/manage_epics.md

@@ -246,7 +246,7 @@ To move an issue to another epic:
 
 If you have the necessary [permissions](../../permissions.md) to close an issue and create an
 epic in the immediate parent group, you can promote an issue to an epic with the `/promote`
-[quick action](../../project/quick_actions.md#quick-actions-for-issues-merge-requests-and-epics).
+[quick action](../../project/quick_actions.md#issues-merge-requests-and-epics).
 Only issues from projects that are in groups can be promoted. When you attempt to promote a confidential
 issue, a warning is displayed. Promoting a confidential issue to an epic makes all information
 related to the issue public as epics are public to group members.

doc/user/project/issues/associate_zoom_meeting.md

@@ -17,7 +17,7 @@ team members can join swiftly without requesting a link.
 ## Adding a Zoom meeting to an issue
 
 To associate a Zoom meeting with an issue, you can use GitLab
-[quick actions](../quick_actions.md#quick-actions-for-issues-merge-requests-and-epics).
+[quick actions](../quick_actions.md#issues-merge-requests-and-epics).
 
 In an issue, leave a comment using the `/zoom` quick action followed by a valid Zoom link:
 

doc/user/project/issues/managing_issues.md

@@ -298,7 +298,7 @@ To promote an issue to an epic:
 1. In an issue, select the vertical ellipsis (**{ellipsis_v}**) button.
 1. Select **Promote to epic**.
 
-Alternatively, you can use the `/promote` [quick action](../quick_actions.md#quick-actions-for-issues-merge-requests-and-epics).
+Alternatively, you can use the `/promote` [quick action](../quick_actions.md#issues-merge-requests-and-epics).
 
 Read more about promoting an issue to an epic on the [Manage epics page](../../group/epics/manage_epics.md#promote-an-issue-to-an-epic).
 
@@ -313,5 +313,5 @@ To add an issue to an [iteration](../../group/iterations/index.md):
 1. Click an iteration you'd like to associate this issue with.
 
 You can also use the `/iteration`
-[quick action](../quick_actions.md#quick-actions-for-issues-merge-requests-and-epics)
+[quick action](../quick_actions.md#issues-merge-requests-and-epics)
 in a comment or description field.

doc/user/project/merge_requests/drafts.md

@@ -27,7 +27,7 @@ There are several ways to flag a merge request as a draft:
   the beginning of the merge request's title, or click **Start the title with Draft:**
   below the **Title** field.
 - **Commenting in an existing merge request**: Add the `/draft`
-  [quick action](../quick_actions.md#quick-actions-for-issues-merge-requests-and-epics)
+  [quick action](../quick_actions.md#issues-merge-requests-and-epics)
   in a comment. This quick action is a toggle, and can be repeated to change the status
   again. This quick action discards any other text in the comment.
 - **Creating a commit**: Add `draft:`, `Draft:`, `fixup!`, or `Fixup!` to the
@@ -53,7 +53,7 @@ When a merge request is ready to be merged, you can remove the `Draft` flag in s
   from the beginning of the title, or click **Remove the Draft: prefix from the title**
   below the **Title** field.
 - **Commenting in an existing merge request**: Add the `/draft`
-  [quick action](../quick_actions.md#quick-actions-for-issues-merge-requests-and-epics)
+  [quick action](../quick_actions.md#issues-merge-requests-and-epics)
   in a comment in the merge request. This quick action is a toggle, and can be repeated
   to change the status back. This quick action discards any other text in the comment.
 

doc/user/project/merge_requests/getting_started.md

@@ -110,7 +110,7 @@ dropdown menu.
 It is also possible to manage multiple assignees:
 
 - When creating a merge request.
-- Using [quick actions](../quick_actions.md#quick-actions-for-issues-merge-requests-and-epics).
+- Using [quick actions](../quick_actions.md#issues-merge-requests-and-epics).
 
 ### Reviewer