Moved the table to the top of the topic

Why is this change being made?

This change is meant to make the assigned tech writer quicker to find. When someone clicks the link, they didn't need to view all of this intro text before viewing the table of assignments.

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
  • The when to get approval handbook section explains the workflow in more detail
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • Department: If the update affects your department, share the MR in your department Slack channel
  • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

---

content/handbook/product/ux/technical-writing/_index.md

@@ -116,31 +116,14 @@ Some content on docs.gitlab.com is [not reviewed by TWs](#content-not-reviewed-b
 
 ### Assignments to DevOps Stages and Groups
 
-{{% alert title="Note" color="primary" %}}
-**If you were directed here from a documentation page's metadata:**
-References to stages and groups in documentation metadata don't indicate developer group ownership, but instead help connect people to the assigned stable counterpart technical writer with subject matter awareness.
-If internal groups want to use other metadata parameters to track information in documentation pages, please create an issue in the Technical Writing repository for discussion.
-Additional discussions are in [this issue](https://gitlab.com/gitlab-org/technical-writing/-/issues/547).
-{{% /alert %}}
-
 The designated Technical Writer is the go-to person for their assigned
-[stage groups](/handbook/product/categories/). They collaborate with
+[groups](/handbook/product/categories/). They collaborate with
 other team members to plan new documentation, edit existing documentation,
-review any proposed changes to documentation, suggest changes to the microcopy
-exposed to users, and generally partner with subject matter experts (SMEs) in
+review any proposed changes to documentation, suggest changes to UI microcopy,
+and generally partner with subject matter experts (SMEs) in
 all situations where documentation is required.
 
-When a Technical Writer [is on PTO](#technical-writer-pto), the whole team acts as their backup.
-
-If you've been directed here from metadata in a documentation page
-that has `none` as the stage, refer to the
-[Assignments to other projects and subjects](#assignments-to-other-projects-and-subjects)
-section, referencing the group shown in metadata with the listed Subjects in the table.
-
-{{% alert title="Note" color="primary" %}}
-Not sure who's responsible for a feature? Review feature assignments by [stage](https://about.gitlab.com/features/) or [group](/handbook/product/categories/features/).
-{{% /alert %}}
-
+If the stage is listed as `none`, see if [there is a DRI](#assignments-to-other-projects-and-subjects) or use [roulette](https://gitlab-org.gitlab.io/gitlab-roulette/?sortKey=stats.avg30&order=-1&hourFormat24=true&visible=maintainer%7Cdocs).
 {{% tech-writing %}}
 
 <!--
@@ -152,11 +135,20 @@ Not sure who's responsible for a feature? Review feature assignments by [stage](
 Reference: https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/24952
 -->
 
+{{% alert title="Note" color="primary" %}}
+**If you were directed here from a documentation page's metadata:**
+- The metadata doesn't indicate developer ownership, but is meant to direct you to an appropriate technical writer.
+- If you are a development group and would like metadata in documentation pages, create an issue in [the Technical Writing repository](https://gitlab.com/gitlab-org/technical-writing) for discussion. Additional discussion is in [this issue](https://gitlab.com/gitlab-org/technical-writing/-/issues/547).
+- If the stage is listed as `none`, see if [there is a DRI](#assignments-to-other-projects-and-subjects) or use [roulette](https://gitlab-org.gitlab.io/gitlab-roulette/?sortKey=stats.avg30&order=-1&hourFormat24=true&visible=maintainer%7Cdocs).
+{{% /alert %}}
+
 Technical Writers are encouraged to review and improve documentation of other
 stages but they aren't required to. When contributing to docs they don't own,
 they must respect the assigned TW's ownership and ensure to request their review
 and approval when adding significant changes to their docs.
 
+When a Technical Writer [is on PTO](#technical-writer-pto), the whole team acts as their backup.
+
 ### Assignments to other projects and subjects
 
 For collaboration in other projects and subjects: