Changed user/admin to administration path

Related to: https://gitlab.com/gitlab-org/gitlab/-/issues/384335

Author: Suzanne Selhorn

doc/jihu_edition.md

@@ -44,7 +44,7 @@ back to the login screen. Use the default account's username `root` to log in.
 For detailed instructions, see [installation and configuration](installation/index.md#installation-and-configuration).
 
 Additionally, you can navigate to the GitLab administration panel of your server and
-[upload your JiHu Edition license file](https://docs.gitlab.com/ee/user/admin_area/license.html#uploading-your-license).
+[upload your JiHu Edition license file](https://docs.gitlab.com/ee/administration/license.html#uploading-your-license).
 
 ## Update GitLab Enterprise Edition to JiHu Edition
 

doc/roles/index.md

@@ -185,7 +185,7 @@ information, see the
 
 Spamcheck roles are used to setup and configure Spamcheck services. For additional
 information, see the
-[Spamcheck documentation](https://docs.gitlab.com/ee/user/admin_area/reporting/spamcheck.html)
+[Spamcheck documentation](https://docs.gitlab.com/ee/administration/reporting/spamcheck.html)
 
 - **spamcheck_role** (`gitlab-ee`)
 

doc/settings/configuration.md

@@ -26,7 +26,7 @@ for more details about the use of DNS in a self-managed GitLab instance.
 To change the external URL:
 
 1. Optional. Before you change the external URL, determine if you have previously
-   defined a [custom **Home page URL** or **After sign-out path**](https://docs.gitlab.com/ee/user/admin_area/settings/sign_in_restrictions.html#sign-in-information).
+   defined a [custom **Home page URL** or **After sign-out path**](https://docs.gitlab.com/ee/administration/settings/sign_in_restrictions.html#sign-in-information).
    Both of these settings might cause unintentional redirecting after configuring
    a new external URL. If you have defined any URLs, remove them completely.
 

doc/settings/nginx.md

@@ -693,7 +693,7 @@ sudo gitlab-ctl hup nginx
 
 If you see `Request Entity Too Large` in the [NGINX logs](https://docs.gitlab.com/ee/administration/logs/index.html#nginx-logs),
 you will need to increase the [Client Max Body Size](http://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size).
-You may encounter this error if you have increased the [Max import size](https://docs.gitlab.com/ee/user/admin_area/settings/account_and_limit_settings.html#max-import-size).
+You may encounter this error if you have increased the [Max import size](https://docs.gitlab.com/ee/administration/settings/account_and_limit_settings.html#max-import-size).
 In a Kubernetes-based GitLab installation, this setting is
 [named differently](https://docs.gitlab.com/charts/charts/gitlab/webservice/#proxybodysize).
 

doc/settings/ssl/index.md

@@ -365,7 +365,7 @@ The external load balancer may need access to a GitLab endpoint
 that returns a `200` status code (for installations requiring login, the root
 page returns a `302` redirect to the login page). In that case, it's
 recommended to leverage a
-[health check endpoint](https://docs.gitlab.com/ee/user/admin_area/monitoring/health_check.html).
+[health check endpoint](https://docs.gitlab.com/ee/administration/monitoring/health_check.html).
 
 Other bundled components, like the Container Registry, GitLab Pages, or Mattermost,
 use a similar strategy for proxied SSL. Set the particular component's `*_external_url` with `https://` and

doc/update/gitlab_11_changes.md

@@ -64,7 +64,7 @@ been removed:
 
 ### 11.2
 
-Rack Attack is disabled by default. To continue using Rack Attack, you must [enable it manually](https://docs.gitlab.com/ee/user/admin_area/settings/protected_paths.html).
+Rack Attack is disabled by default. To continue using Rack Attack, you must [enable it manually](https://docs.gitlab.com/ee/administration/settings/protected_paths.html).
 
 ### 11.3
 

files/gitlab-cookbooks/package/libraries/deprecations.rb

@@ -330,7 +330,7 @@ def list(existing_config = nil)
             config_keys: %w(gitlab gitlab_rails gitlab_default_can_create_group),
             deprecation: '15.5',
             removal: '16.0',
-            note: "Starting with GitLab 15.5, this setting cannot be controlled via the configuration file anymore. Follow the steps at https://docs.gitlab.com/ee/user/admin_area/settings/account_and_limit_settings.html#prevent-new-users-from-creating-top-level-groups, to configure this setting via the Admin UI or the API"
+            note: "Starting with GitLab 15.5, this setting cannot be controlled via the configuration file anymore. Follow the steps at https://docs.gitlab.com/ee/administration/settings/account_and_limit_settings.html#prevent-new-users-from-creating-top-level-groups, to configure this setting via the Admin UI or the API"
           },
           {
             config_keys: %w(gitlab sidekiq queue_selector),