Merge branch 'eread/ssot-for-compliance-features' into 'master'

Combine lists of compliance features together, and cross link

See merge request gitlab-org/gitlab!78019

doc/administration/compliance.md

@@ -54,6 +54,8 @@ identify if problems exist and then drill down into the specifics of those issue
 - [**Audit events**](audit_events.md) (for instances, groups, and projects): To maintain the integrity of your code,
   audit events give administrators the ability to view any modifications made within the GitLab
   server in an advanced audit events system, so you can control, analyze, and track every change.
+- [**Audit reports**](audit_reports.md) (for instances, groups, and projects): Create and access reports based on the
+  audit events that have occurred. Use pre-built GitLab reports or the API to build your own.
 - [**Auditor users**](auditor_users.md) (for instances): Auditor users are users who are given read-only access to all
   projects, groups, and other resources on the GitLab instance.
 - [**Compliance report**](../user/compliance/compliance_report/index.md) (for groups): Quickly get visibility into the
@@ -73,6 +75,8 @@ These features can also help with compliance requirements:
 - [**Generate reports on permission levels of users**](../user/admin_area/index.md#user-permission-export) (for
   instances): Administrators can generate a report listing all users' access permissions for groups and projects in the
   instance.
+- [**License compliance**](../user/compliance/license_compliance/index.md) (for projects): Search dependencies for their
+  licenses. This lets you determine if the licenses of your project's dependencies are compatible with your project's license.
 - [**Lock project membership to group**](../user/group/index.md#prevent-members-from-being-added-to-projects-in-a-group) (for
   groups): Group owners can prevent new members from being added to projects within a group.
 - [**LDAP group sync**](auth/ldap/ldap_synchronization.md#group-sync) (for instances): Gives administrators the ability

doc/user/compliance/index.md

@@ -7,15 +7,6 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 # Compliance **(ULTIMATE)**
 
-The compliance tools provided by GitLab let you keep an eye on various aspects of your project. The
-following compliance tools are available:
-
-- [Compliance report](compliance_report/index.md): View recent merge request activity across
-  all projects in a group. This lets you see if merge requests were approved, and by whom.
-- [License Compliance](license_compliance/index.md): Search your project's dependencies for their
-  licenses. This lets you determine if the licenses of your project's dependencies are compatible
-  with your project's license.
-- [Compliance framework labels](../project/settings/index.md#compliance-frameworks): Label your projects that have unique compliance requirements.
-- [Compliance pipelines](../project/settings/index.md#compliance-pipeline-configuration): Ensure that needed compliance jobs are always run for compliance-labeled projects.
-- [Audit Events](../../administration/audit_events.md): Get visibility into individual actions that have taken place in your GitLab instance, group, or project.
-- [Audit Reports](../../administration/audit_reports.md): Create and access reports based on the audit events that have occurred. Use pre-built GitLab reports or the API to build your own.
+The compliance tools provided by GitLab help you keep an eye on various aspects of your project. For more information
+on GitLab compliance features for projects, groups, and instances, see
+[Compliance features](../../administration/compliance.md).

doc/user/compliance/license_compliance/index.md

@@ -5,7 +5,7 @@ group: Composition Analysis
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
 ---
 
-# License Compliance **(ULTIMATE)**
+# License compliance **(ULTIMATE)**
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/5483) in GitLab 11.0.