Find and replace across all docs to update Admin area
to **Admin** area.

Changelog: added

Co-authored-by: Brendan Lynch <blynch@gitlab.com>

Another piece of information that can be removed now that the
feature is gone.

Remove FFs wiki_front_matter and wiki_front_matter_title.

Changelog: added

Co-authored-by: Amy Qualls <aqualls@gitlab.com>

Per request from Support

Co-authored-by: Marcin Sedlak-Jakubowski <msedlakjakubowski@gitlab.com>

Changelog: added

https://gitlab.com/gitlab-org/gitlab/-/issues/451211

Co-authored-by: Jonathan Glassman <jglassman@gitlab.com>

Merge branch 'security-import-export-based-on-user' into 'master'

See merge request gitlab-org/security/gitlab!4211

Changelog: security

What's here is a false choice - you can't set this value temporarily.
Adjust the docs to reflect the actual truth.

Co-authored-by: Suzanne Selhorn <sselhorn@gitlab.com>

MR: gitlab.com/gitlab-org/gitlab/-/merge_requests/159690

Reshape this information into a set of ordered steps, and do some
light rewriting for sentence style. Also, indentation.

Blend together the information to make a more cohesive single
subheading that contains all of the information in the order
customers need it in.

The FF has been enabled by default since 16.11
Removing the flag as we have seen no issues
reported by users.

Changelog: other

Now that 'audit events' is sentence-cased in the UI, let's make the
docs and other ancillary assets match.

Co-authored-by: Phillip Wells <pwells@gitlab.com>

We should mention on this page that GitLab Duo can be useful here.

Changelog: changed

Because our standards are "prerequisites" and
not to use known issues

Changelog: changed

When a Resource (Group or Project) Access Token is created for, the
following occurrs:

- a User is created (a bot)
- a PAT is created for the bot (known as a Group or Project Access Token)
- a Member record is created to associate the bot and the resource

Previously, the membership would expire when the token expired. When
the Membership expired, the `RemoveExpiredMembersWorker` would destroy
the Member and bot User records. Expired tokens would no longer have
any association with the resource, making auditing and security reviews
more challenging.

Now, when the Feature Flag
`retain_resource_access_token_user_after_revoke` is enabled for a
Resource, new Resource Access Tokens will have Member records that do
not expire. When the token expires, the Member and User records are
retained. (In a different MR these inactive tokens are displayed in
Group and Project Settings).

This is part of https://gitlab.com/gitlab-org/gitlab/-/issues/462217