REST API - Edit and rewrap authentication content

What does this MR do?

Edit and rewrap REST API authentication documentation.

Related issues

• Improve content design of top-level REST API do... (#480087 - closed)
• technical-writing#1075

Author's checklist

• Optional. Consider taking the GitLab Technical Writing Fundamentals course.
• Follow the:
  • Documentation process.
  • Documentation guidelines.
  • Style Guide.
• If you're adding a new page, add the product availability details under the H1 topic title.
• If you are a GitLab team member, request a review based on:
  • The documentation page's metadata.
  • The associated Technical Writer.

If you are a GitLab team member and only adding documentation, do not add any of the following labels:

• ~"frontend"
• ~"backend"
• ~"type::bug"
• ~"database"

These labels cause the MR to be added to code verification QA issues.

Reviewer's checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.

• If the content requires it, ensure the information is reviewed by a subject matter expert.
• Technical writer review items:
  • Ensure docs metadata is present and up-to-date.
  • Ensure the appropriate labels are added to this MR.
  • Ensure a release milestone is set.
  • If relevant to this MR, ensure content topic type principles are in use, including:
    • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
    • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
    • Any task steps should be written as a numbered list.
    • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
• Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.

changed milestone to %17.5

added docs-only docsimprovement documentation maintenancerefactor typemaintenance labels

assigned to @rdickenson

added devopsfoundations groupimport and integrate labels

added sectioncore platform label

added Technical Roadmap label and removed sectioncore platform label

added sectioncore platform label

removed Technical Roadmap label

added Technical Writing label

	1 Message
📖	This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge.

Documentation review

The following files require a review from a technical writer:

• doc/api/rest/index.md (Link to current live version)

The review does not need to block merging this merge request. See the:

• Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
• The Technical Writer assigned for that stage and group.
• Documentation workflows for information on when to assign a merge request for review.

If needed, you can retry the 🔁 danger-review job that generated this comment.

Generated by 🚫 Danger

added 1 commit

• 0417fe6a - Fix Markdown formatting

Compare with previous version

requested review from @sselhorn

@sselhorn Could you please review this MR, and merge it if you approve?

Note: With one very minor exception, this MR consists solely of rewrapping content to a maximum 100-character line length.

added 169 commits

• 0417fe6a...ae775944 - 168 commits from branch master
• 72164e80 - Merge branch 'master' into 'rd-rest-api-edit-authentication'

Compare with previous version

enabled automatic add to merge train when checks pass

Thanks @rdickenson Merged! 🚀

aborted automatic add to merge train because the source branch was updated. Learn more.

added 1 commit

• 136873ff - Fixed broken link

Compare with previous version

enabled automatic add to merge train when checks pass

started a merge train