SONAR-12905 Update paths in the docs for new projects UI

15 files changed, 30 insertions, 30 deletions

diff --git a/server/sonar-docs/src/pages/analysis/analysis-parameters.md b/server/sonar-docs/src/pages/analysis/analysis-parameters.md
index 9800271a562..b8bb944e1d7 100644
--- a/server/sonar-docs/src/pages/analysis/analysis-parameters.md
+++ b/server/sonar-docs/src/pages/analysis/analysis-parameters.md
@@ -8,7 +8,7 @@ Project analysis settings can be configured in multiple places. Here is the hier
 <!-- sonarqube -->
 * Global properties, defined in the UI, apply to all projects (From the top bar, go to **[Administration > Configuration > General Settings](/#sonarqube-admin#/admin/settings)**)
 <!-- /sonarqube -->
-* Project properties, defined in the UI, override global property values (At a project level, go to **Administration > General Settings**)
+* Project properties, defined in the UI, override global property values (At a project level, go to **Project Settings > General Settings**)
 * Project analysis parameters, defined in a project analysis configuration file or an analyzer configuration file, override the ones defined in the UI
 * Analysis / Command line parameters, defined when launching an analysis (with `-D` on the command line), override project analysis parameters
 
@@ -25,7 +25,7 @@ For language-specific parameters related to external issue reports, see [Externa
 ### Server
 Key | Description | Default
 ---|----|---
-`sonar.host.url`| the server URL | <!-- sonarqube -->http://localhost:9000<!-- /sonarqube --><!-- sonarcloud -->https://sonarcloud.io<!-- /sonarcloud -->
+`sonar.host.url`| the server URL | http://localhost:9000
 
 ### Project Configuration
 Key | Description | Default
diff --git a/server/sonar-docs/src/pages/analysis/background-tasks.md b/server/sonar-docs/src/pages/analysis/background-tasks.md
index 63c1af4b9d1..9a2e99ff848 100644
--- a/server/sonar-docs/src/pages/analysis/background-tasks.md
+++ b/server/sonar-docs/src/pages/analysis/background-tasks.md
@@ -14,7 +14,7 @@ Analysis is not complete until the relevant Background Task has been completed.
 
 At the Project level, when there is a pending Analysis Report waiting to be consumed, you have a "Pending" notification in the header, next to the date of the most recent completed analysis.
 
-Global Administrators can view the current queue at **[Administration > Projects > Background Tasks](/#sonarqube-admin#/admin/background_tasks)**. Project administrators can see the tasks for a project at **Administration > Background Tasks**.
+Global Administrators can view the current queue at **[Administration > Projects > Background Tasks](/#sonarqube-admin#/admin/background_tasks)**. Project administrators can see the tasks for a project at **Project Settings > Background Tasks**.
 
 ## How do I know when analysis report processing fails?
 Background tasks usually succeed, but sometimes unusual circumstances cause processing to fail. Examples include:
diff --git a/server/sonar-docs/src/pages/analysis/pr-decoration.md b/server/sonar-docs/src/pages/analysis/pr-decoration.md
index e23bca9fa3e..0e89b22c981 100644
--- a/server/sonar-docs/src/pages/analysis/pr-decoration.md
+++ b/server/sonar-docs/src/pages/analysis/pr-decoration.md
@@ -50,7 +50,7 @@ Click your ALM provider below to expand the instructions on decorating your Pull
 |
 | ### Setting your project settings
 |
-| Go to **Administration > General Settings > Pull Request Decoration**, select your **Configuration Name**, and set your **Repository identifier**.
+| Go to **Project Settings > General Settings > Pull Request Decoration**, select your **Configuration Name**, and set your **Repository identifier**.
 
 [[collapse]]
 | ## Bitbucket Server
@@ -71,7 +71,7 @@ Click your ALM provider below to expand the instructions on decorating your Pull
 |
 | ### Setting your project settings
 |
-| Go to **Administration > General Settings > Pull Request Decoration**, select your **Configuration name**, and set your **Project Key** and **Repo Slug**.
+| Go to **Project Settings > General Settings > Pull Request Decoration**, select your **Configuration name**, and set your **Project Key** and **Repo Slug**.
 
 [[collapse]]
 | ## Azure DevOps Server
@@ -90,7 +90,7 @@ Click your ALM provider below to expand the instructions on decorating your Pull
 |
 | ### Setting your project settings
 |
-| Go to **Administration > General Settings > Pull Request Decoration** and select your **Configuration name**.
+| Go to **Project Settings > General Settings > Pull Request Decoration** and select your **Configuration name**.
 
 [[collapse]]
 | ## GitLab Self-Managed and GitLab.com
@@ -111,7 +111,7 @@ Click your ALM provider below to expand the instructions on decorating your Pull
 |
 | ### Setting your project settings
 |
-| Go to **Administration > General Settings > Pull Request Decoration** and select your **Configuration name**.
+| Go to **Project Settings > General Settings > Pull Request Decoration** and select your **Configuration name**.
 
 ## Multiple ALM instances
 
diff --git a/server/sonar-docs/src/pages/analysis/scm-integration.md b/server/sonar-docs/src/pages/analysis/scm-integration.md
index e2ddf58b21f..7e41ad5698d 100644
--- a/server/sonar-docs/src/pages/analysis/scm-integration.md
+++ b/server/sonar-docs/src/pages/analysis/scm-integration.md
@@ -11,7 +11,7 @@ Collecting SCM data during code analysis can unlock a number of SonarQube featur
 
 SCM integration requires support for your individual SCM provider. Git and SVN are supported by default. <!-- sonarqube -->For other SCM providers, see the Marketplace.<!-- /sonarqube -->
 
-If need be, you can toggle it off at global/project level via administration settings.
+If need be, you can toggle it off at global level via administration settings and at a project level via project settings.
 
 ## Git
 [Git](http://www.git-scm.com/) integration is supported out of the box with a pure Java implementation so there's no need to have Git command line tool installed on the machine where analysis is performed.
diff --git a/server/sonar-docs/src/pages/branches/branches-faq.md b/server/sonar-docs/src/pages/branches/branches-faq.md
index 7af486490e0..ee8ce8ebfae 100644
--- a/server/sonar-docs/src/pages/branches/branches-faq.md
+++ b/server/sonar-docs/src/pages/branches/branches-faq.md
@@ -6,10 +6,10 @@ url: /branches/branches-faq/
 _Branch analysis is available as part of [Developer Edition](https://redirect.sonarsource.com/editions/developer.html) and [above](https://www.sonarsource.com/plans-and-pricing/)._
 
 ## How long are branches retained?  
-Branches will be deleted automatically when they are inactive according to your settings at [Administration > Configuration > General Settings > Housekeeping > Number of days before deleting inactive branches](/#sonarqube-admin#/admin/settings?category=housekeeping) except for branches you have set to be kept when inactive. These branches are kept until you delete them manually at the project level at **Administration > Branches & Pull Requests**. See the [Branches Analysis](/branches/overview/) for more information on keeping inactive branches.
+Branches will be deleted automatically when they are inactive according to your settings at [Administration > Configuration > General Settings > Housekeeping > Number of days before deleting inactive branches](/#sonarqube-admin#/admin/settings?category=housekeeping) except for branches you have set to be kept when inactive. These branches are kept until you delete them manually at the project level at **Project Settings > Branches & Pull Requests**. See the [Branches Analysis](/branches/overview/) for more information on keeping inactive branches.
 
 ## Does my project need to be stored in an SCM like Git or SVN?  
-No, you don't need to be connected to a SCM. However, SCM data still enhances the SonarQube exprerience (including issue auto-assignment and issue backdating), and you will be well prepared to take advantage of [Pull Request Analysis](/analysis/pull-request/)!
+No, you don't need to be connected to a SCM. However, SCM data still enhances the SonarQube experience (including issue auto-assignment and issue backdating), and you will be well prepared to take advantage of [Pull Request Analysis](/analysis/pull-request/)!
 
 ## What if I mark an Issue "Won't Fix" or "False-Positive" in a branch?
 It will be replicated as such when creating a Pull Request and merging the Pull Request into the master branch.
diff --git a/server/sonar-docs/src/pages/branches/overview.md b/server/sonar-docs/src/pages/branches/overview.md
index 4e46f21939d..b010a801512 100644
--- a/server/sonar-docs/src/pages/branches/overview.md
+++ b/server/sonar-docs/src/pages/branches/overview.md
@@ -75,6 +75,6 @@ For example, adding the pattern `release/.*` would keep any branches named relea
 
 ### Managing inactive branches at a project level
 
-You can set a branch to **Keep when inactive** at the project level from from the **Branches** tab at **Administration > Branches and Pull Requests**. Here, you can also turn off protection for a branch so it will be deleted when it's inactive for the number of days that has been specified in the global settings at **Administration > General Settings > Housekeeping > Number of days before deleting inactive branches**. 
+You can set a branch to **Keep when inactive** at the project level from from the **Branches** tab at **Project Settings > Branches and Pull Requests**. Here, you can also turn off protection for a branch so it will be deleted when it's inactive for the number of days that has been specified in the global settings at **Administration > General Settings > Housekeeping > Number of days before deleting inactive branches**. 
 
 **Note:** The main branch is always protected from automatic deletion, even if it's inactive. This can't be changed.
diff --git a/server/sonar-docs/src/pages/instance-administration/custom-measures.md b/server/sonar-docs/src/pages/instance-administration/custom-measures.md
index 8867f060670..e92f9475b30 100644
--- a/server/sonar-docs/src/pages/instance-administration/custom-measures.md
+++ b/server/sonar-docs/src/pages/instance-administration/custom-measures.md
@@ -9,7 +9,7 @@ SonarQube collects a maximum of measures in an automated manner but there are so
 As with measures that are collected automatically, manual measures are the values collected in each analsis for manual metrics. Therefore, the first thing to do is create the metric you want to save your measure against. In order to do so, log in as a system administrator and go to **[Administration > Configuration > Custom Metrics](/#sonarqube-admin#/admin/custom_metrics)**, where the interface will guide you in creating the Metric you need. 
 
 ## Managing Custom Measures
-Custom measures can be entered at project level. To add a measure, sign in as a project administrator, navigate to the desired project and choose **Administration > Custom Measures**, where you will find a table with the latest measure value entered for each metric. 
+Custom measures can be entered at project level. To add a measure, sign in as a project administrator, navigate to the desired project and choose **Project Settings > Custom Measures**, where you will find a table with the latest measure value entered for each metric. 
 
 Values entered in this interface are "Pending", and will not be visible outside this administrative interface until the next analysis. 
 
diff --git a/server/sonar-docs/src/pages/instance-administration/project-move.md b/server/sonar-docs/src/pages/instance-administration/project-move.md
index 9b03c16eada..d968c95c38e 100644
--- a/server/sonar-docs/src/pages/instance-administration/project-move.md
+++ b/server/sonar-docs/src/pages/instance-administration/project-move.md
@@ -25,7 +25,7 @@ In order to be able to export and then load your Project's data, the two SonarQu
 ## How To Export
 On the source instance:
 * reanalyze the project one last time to make sure it is populated with data corresponding to your current SonarQube installation
-* navigate to the project and at the project level, choose **Administration > Import / Export**
+* navigate to the project and at the project level, choose **Project Settings > Import / Export**
 * click on the **Export** button to generate a zip file containing the settings and history of your Project (but not the source code). Note that if you need to change the Project's key, you must to do it before performing the export.
 
 A zip file containing all project data ex is generated in _$SONAR_SOURCE_HOME/data/governance/project_dumps/export/_ named _<project_key>.zip_
@@ -36,7 +36,7 @@ On the target instance:
 * With a user having the "Administer System" and "Create Projects" permissions, go to [**Administration > Projects > Management**](/#sonarqube-admin#/admin/projects_management/) and [provision the project](/project-administration/project-existence/) using the same key the project had in the source instance.
 * Configure the Project's permissions, and the Quality Profiles and Quality Gate associated to the Project
 * Put the generated zip file into the directory *$SONAR\_TARGET\_HOME/data/governance/project_dumps/import*
-* Go to the Project's Home Page and choose **Administration > Import / Export**
+* Go to the Project's Home Page and choose **Project Settings > Import / Export**
 * Click on the Import button to start importing your data
 * Source code is not included in the zip file. Once the import is finished, trigger an analysis to import source files into the new instance.
 
diff --git a/server/sonar-docs/src/pages/instance-administration/quality-profiles.md b/server/sonar-docs/src/pages/instance-administration/quality-profiles.md
index 13dd74d35ae..6eda2f82e41 100644
--- a/server/sonar-docs/src/pages/instance-administration/quality-profiles.md
+++ b/server/sonar-docs/src/pages/instance-administration/quality-profiles.md
@@ -7,7 +7,7 @@ url: /instance-administration/quality-profiles/
 
 **Quality Profiles** are a core component of {instance}, since they are where you define sets of [**Rules**](/user-guide/rules/) that when violated should raise issues on your codebase (example: Methods should not have a Cognitive Complexity higher than 15). Quality Profiles are defined for individual languages.
 
-To manage Quality Profiles, browse to the the [**Quality Profiles**](/#sonarqube#/profiles) page <!-- sonarcloud --> of your organization<!-- /sonarcloud --> where you'll find Quality Profiles grouped by language.
+To manage Quality Profiles, browse to the the [**Quality Profiles**](/#sonarqube#/profiles) page where you'll find Quality Profiles grouped by language.
 
 Ideally all of your projects will be measured with the same Quality Profiles, but that is not _always_ practical. In some cases, you may find that:
 
diff --git a/server/sonar-docs/src/pages/instance-administration/security.md b/server/sonar-docs/src/pages/instance-administration/security.md
index 94cd85ba131..f6ce77992f2 100644
--- a/server/sonar-docs/src/pages/instance-administration/security.md
+++ b/server/sonar-docs/src/pages/instance-administration/security.md
@@ -100,7 +100,7 @@ To set global permissions, log in as a System administrator and go to **[Adminis
 ** Creating an item does not automatically grant rights to administer it. For that, see _Creators permission_ below.
 
 ### Project Permissions
-Project permissions are available from the project-level Administration menu: **Administration > Permissions**.
+Project permissions are available from the project-level Administration menu: **Project Settings > Permissions**.
 
 Project visibility may be toggled between public or private. Making a project private hides its source code and measures from the `Anyone` group. For both public and private projects, four different permissions can be set:
 
diff --git a/server/sonar-docs/src/pages/project-administration/narrowing-the-focus.md b/server/sonar-docs/src/pages/project-administration/narrowing-the-focus.md
index 96cb28548e0..dc8f137061a 100644
--- a/server/sonar-docs/src/pages/project-administration/narrowing-the-focus.md
+++ b/server/sonar-docs/src/pages/project-administration/narrowing-the-focus.md
@@ -12,7 +12,7 @@ If {instance}'s results aren't relevant, no one will want to use it. That's why
 * exclude files/directories from Duplications detection but analyze all other aspects
 * exclude files/directories from Coverage calculations but analyze all other aspects
 
-You can make these changes globally or at a project level. At both levels, the navigation path is  **Administration > General Settings > Analysis Scope**.
+You can make these changes globally or at a project level. At the global level, the navigation path is  **Administration > General Settings > Analysis Scope**. At the project level, the navigation path is **Project Settings > General Settings > Analysis Scope**
 
 ## Patterns
 
diff --git a/server/sonar-docs/src/pages/project-administration/new-code-period.md b/server/sonar-docs/src/pages/project-administration/new-code-period.md
index 2d710648511..804532d7a3b 100644
--- a/server/sonar-docs/src/pages/project-administration/new-code-period.md
+++ b/server/sonar-docs/src/pages/project-administration/new-code-period.md
@@ -15,7 +15,7 @@ You can set the global New Code Period to the following:
 * **Number of days** – You can specify a number of days for a floating New Code Period. For example, setting **Number of Days** to 30 creates a floating New Code Period beginning 30 days from the current date.
 
 ## Setting a project-level New Code Period
-You can override the global New Code Period by setting a project-level New Code Period from the project page at **Administration > New Code Period**. For [Developer Edition](https://redirect.sonarsource.com/editions/developer.html) and [above](https://www.sonarsource.com/plans-and-pricing/), this will be the default New Code Period for all of the project's branches.
+You can override the global New Code Period by setting a project-level New Code Period from the project page at **Project Settings > New Code Period**. For [Developer Edition](https://redirect.sonarsource.com/editions/developer.html) and [above](https://www.sonarsource.com/plans-and-pricing/), this will be the default New Code Period for all of the project's branches.
 
 You can set a project's New Code Period to the following:
 
diff --git a/server/sonar-docs/src/pages/project-administration/project-settings.md b/server/sonar-docs/src/pages/project-administration/project-settings.md
index 3988ef4bd31..2c28bce1b24 100644
--- a/server/sonar-docs/src/pages/project-administration/project-settings.md
+++ b/server/sonar-docs/src/pages/project-administration/project-settings.md
@@ -9,7 +9,7 @@ Project tags allow you to categorize and group projects for easier selection on
 
 ## Administration Items
 
-Project administration is accessible through the **Administration** menu of each project.  
+Project administration is accessible through the **Project Settings** menu of each project.  
 
 Only project administrators can access project's settings (see [Authorization](/instance-administration/security/)).
 
@@ -19,33 +19,33 @@ A project is automatically added at its first analysis. Note that you can also [
 
 ### Analysis Report Processing
 
-A project-level Background Tasks page is available at **Administration > Background Tasks** to allow project administrators to check their projects' processing. It offers analysis report details and logs.
+A project-level Background Tasks page is available at **Project Settings > Background Tasks** to allow project administrators to check their projects' processing. It offers analysis report details and logs.
 
 ### Deleting a Project
 
 #### Deleting a Single Project
 
-You can delete a project through **Administration > Deletion**.
+You can delete a project through **Project Settings > Deletion**.
 
 #### Deleting Multiple Projects
-You can also delete multiple projects simultaneously from the global **Administration > Projects > Management**.
+You can also delete multiple projects simultaneously from the global **Project Settings > Projects > Management**.
 
 ### Updating the Project Key  
 
-The project key can be updated (without losing the history on the project) at **Administration > Update Key**.
+The project key can be updated (without losing the history on the project) at **Project Settings > Update Key**.
 
 The new key must contain at least one non-digit character. Allowed characters are: 'a' through 'z', 'A' through 'Z', '-' (dash), '\_' (underscore), '.' (dot), ':' (colon) and digits '0' to '9'.
 
 ### Default Issue Assignee
 
-When new issues are created during an analysis, they are assigned to the last committer where the issue was raised. When it is not possible to identify the last committer, issues can be assigned to a default assignee, at ]Administration  > General Settings > Issues](/#sonarqube-admin#/admin/settings).
+When new issues are created during an analysis, they are assigned to the last committer where the issue was raised. When it is not possible to identify the last committer, issues can be assigned to a default assignee, at [Administration  > General Settings > Issues](/#sonarqube-admin#/admin/settings).
 
 ### Setting Quality Gate and Quality Profiles  
 
 Project administrators can select which ...
 
-* Quality profiles (go to **Administration  > Quality Profiles**)
-* Quality gate (go to **Administration  > Quality Gate**)
+* Quality profiles (go to **Project Settings  > Quality Profiles**)
+* Quality gate (go to **Project Settings  > Quality Gate**)
 
 ... to use on their project.
 
@@ -55,4 +55,4 @@ See [Narrowing the Focus](/project-administration/narrowing-the-focus/).
 
 ### Customizing Links
 
-On top of standard links which may only be set as [Analysis Parameters](/analysis/analysis-parameters/), additional custom links can be added through the web interface (under **Administration > Links**). Those links will then be displayed in the [Project Page](/user-guide/project-page/).
+On top of standard links which may only be set as [Analysis Parameters](/analysis/analysis-parameters/), additional custom links can be added through the web interface (under **Project Settings > Links**). Those links will then be displayed in the [Project Page](/user-guide/project-page/).
diff --git a/server/sonar-docs/src/pages/project-administration/webhooks.md b/server/sonar-docs/src/pages/project-administration/webhooks.md
index 64e9a4ef5e2..4556590d9ed 100644
--- a/server/sonar-docs/src/pages/project-administration/webhooks.md
+++ b/server/sonar-docs/src/pages/project-administration/webhooks.md
@@ -13,7 +13,7 @@ The HTTP(S) call:
 
 ## Configuration
 
-You can configure up to 10 webhooks in in **Administration > Webhooks**.
+You can configure up to 10 webhooks at the project level in **Project Settings > Webhooks**.
 
 An additional set of 10 webhooks can be configured at the global level in **Administration > Configuration > Webhooks**.
 
@@ -106,7 +106,7 @@ After you've configured your server to receive payloads, you want to be sure tha
 
 To set your secret in {instance}:
 
-1. From the project or organization where you're securing your webhooks, navigate to the webhooks settings at **Administration > webhooks**
+1. From the project or organization where you're securing your webhooks, navigate to the webhooks settings at **Project Settings > Webhooks**
 1. You can either click **Create** to create a new webhook or click an existing webhook's settings drop-down and click **Update**.
 1. Enter a random string in the **Secret** text box. This is used as the key to generate the HMAC hex digest value in the `X-Sonar-Webhook-HMAC-SHA256` header.
 1. Click **Update**. 
diff --git a/server/sonar-docs/src/pages/user-guide/applications.md b/server/sonar-docs/src/pages/user-guide/applications.md
index 2cecad1a61c..8d71ed4c19c 100644
--- a/server/sonar-docs/src/pages/user-guide/applications.md
+++ b/server/sonar-docs/src/pages/user-guide/applications.md
@@ -27,4 +27,4 @@ Branches are available for Applications. They allow you to aggregate branches fr
 
 **Note:** Avoid adding branches to your application that will be deleted to prevent issues with your Application status.
 
-Once an Application has been set up, anyone with administration rights on the Application can manually create a new branch in the **Administration > Edit Definition** interface. Branches can also be managed from the global **Administration > Configuration > Portfolios** interface. For each Application branch you can choose which project branch should be included, or whether the project should be represented in the branch at all.
+Once an Application has been set up, anyone with administration rights on the Application can manually create a new branch in the **Application Settings > Edit Definition** interface. Branches can also be managed from the global **Administration > Configuration > Portfolios** interface. For each Application branch you can choose which project branch should be included, or whether the project should be represented in the branch at all.