Merge branch 'wc-cr-gc-warn' into 'master'

Docs: Move Container Registry to a more prominent location

See merge request gitlab-org/gitlab!28348

doc/administration/packages/container_registry.md

@@ -646,6 +646,13 @@ NOTE: **Note:**
 The garbage collection tools are only available when you've installed GitLab
 via an Omnibus package or the cloud native chart.
 
+DANGER: **Danger:**
+By running the built-in garbage collection command, it will cause downtime to
+the Container Registry. Running this command on an instance in an HA environment
+while one of your other instances is still writing to the Registry storage,
+will remove referenced manifests. To avoid that, make sure Registry is set to
+[read-only mode](#performing-garbage-collection-without-downtime) before proceeding.
+
 Container Registry can use considerable amounts of disk space. To clear up
 some unused layers, the registry includes a garbage collect command.
 
@@ -695,13 +702,6 @@ built-in command:
   specify its path.
 - After the garbage collection is done, the registry should start up automatically.
 
-DANGER: **Danger:**
-By running the built-in garbage collection command, it will cause downtime to
-the Container Registry. Running this command on an instance in an HA environment
-while one of your other instances is still writing to the Registry storage,
-will remove referenced manifests. To avoid that, make sure Registry is set to
-[read-only mode](#performing-garbage-collection-without-downtime) before proceeding.
-
 If you did not change the default location of the configuration file, run:
 
 ```sh