DOCS update commercial message

20 files changed, 26 insertions, 43 deletions

diff --git a/server/sonar-docs/src/pages/analysis/gitlab-cicd.md b/server/sonar-docs/src/pages/analysis/gitlab-cicd.md
index 824f908a7d2..5a188ae0855 100644
--- a/server/sonar-docs/src/pages/analysis/gitlab-cicd.md
+++ b/server/sonar-docs/src/pages/analysis/gitlab-cicd.md
@@ -2,7 +2,7 @@
 title: GitLab CI/CD
 url: /analysis/gitlab-cicd/
 ---
-_Merge Request analysis is available as part of [Developer Edition](https://redirect.sonarsource.com/editions/developer.html) and [above](https://www.sonarsource.com/plans-and-pricing/)._
+_Merge Request analysis is available starting in [Developer Edition](https://redirect.sonarsource.com/editions/developer.html)._
 
 SonarScanners running in GitLab CI/CD jobs can automatically detect branches or Merge Requests being built so you don't need to specifically pass them as parameters to the scanner.
 
diff --git a/server/sonar-docs/src/pages/analysis/jenkins.md b/server/sonar-docs/src/pages/analysis/jenkins.md
index c71155d9337..e99994fef77 100644
--- a/server/sonar-docs/src/pages/analysis/jenkins.md
+++ b/server/sonar-docs/src/pages/analysis/jenkins.md
@@ -3,7 +3,7 @@ title: Jenkins
 url: /analysis/jenkins/
 ---
 
-_Pull Request analysis is available as part of [Developer Edition](https://redirect.sonarsource.com/editions/developer.html) and [above](https://www.sonarsource.com/plans-and-pricing/)._
+_Pull Request analysis is available starting in [Developer Edition](https://redirect.sonarsource.com/editions/developer.html)._
 
 SonarScanners running in Jenkins can automatically detect branches and Merge or Pull Requests in certain jobs. You don't need to explicitly pass the branch or Pull Request details.
 
@@ -66,7 +66,7 @@ With Community Edition, you can only analyze a single branch. For more informati
 
 ## Configuring Multibranch Pipeline jobs 
  
-With [Developer Edition](https://redirect.sonarsource.com/editions/developer.html) and [above](https://www.sonarsource.com/plans-and-pricing/), you can analyze multiple branches and Pull Requests. The automatic configuration of branches and Pull Requests relies on environment variables available in Multibranch Pipeline jobs. These are set based on information exported by Jenkins plugins. 
+Starting in [Developer Edition](https://redirect.sonarsource.com/editions/developer.html), you can analyze multiple branches and Pull Requests. The automatic configuration of branches and Pull Requests relies on environment variables available in Multibranch Pipeline jobs. These are set based on information exported by Jenkins plugins. 
 
 For configuration examples, see the [SonarScanner for Jenkins](/analysis/scan/sonarscanner-for-jenkins/) documentation.
 
diff --git a/server/sonar-docs/src/pages/analysis/languages/abap.md b/server/sonar-docs/src/pages/analysis/languages/abap.md
index 75f18831770..9ee9a980649 100644
--- a/server/sonar-docs/src/pages/analysis/languages/abap.md
+++ b/server/sonar-docs/src/pages/analysis/languages/abap.md
@@ -3,11 +3,7 @@ title: ABAP
 url: /analysis/languages/abap/
 ---
 
-<!-- sonarqube -->
-
-_ABAP is available as part of [Developer Edition](https://redirect.sonarsource.com/editions/developer.html) and [above](https://redirect.sonarsource.com/editions/editions.html)._
-
-<!-- /sonarqube -->
+_ABAP is available starting in [Developer Edition](https://redirect.sonarsource.com/editions/developer.html)._
 
 <!-- static -->
 <!-- update_center:abap -->
diff --git a/server/sonar-docs/src/pages/analysis/languages/apex.md b/server/sonar-docs/src/pages/analysis/languages/apex.md
index 4cdde037b75..76ef858ab4b 100644
--- a/server/sonar-docs/src/pages/analysis/languages/apex.md
+++ b/server/sonar-docs/src/pages/analysis/languages/apex.md
@@ -5,7 +5,7 @@ url: /analysis/languages/apex/
 
 <!-- sonarqube -->
 
-_Apex analysis is available as part of the [Enterprise Edition](https://redirect.sonarsource.com/editions/enterprise.html) and [above](https://redirect.sonarsource.com/editions/editions.html)._
+_Apex analysis is available starting in [Enterprise Edition](https://redirect.sonarsource.com/editions/enterprise.html)._
 
 <!-- /sonarqube -->
 
diff --git a/server/sonar-docs/src/pages/analysis/languages/cfamily.md b/server/sonar-docs/src/pages/analysis/languages/cfamily.md
index 26f4145e930..45f8ed64b35 100644
--- a/server/sonar-docs/src/pages/analysis/languages/cfamily.md
+++ b/server/sonar-docs/src/pages/analysis/languages/cfamily.md
@@ -3,9 +3,7 @@ title: C/C++/Objective-C
 url: /analysis/languages/cfamily/
 ---
 
-<!-- sonarqube -->
-_C/C++/Objective-C analysis is available as part of [Developer Edition](https://redirect.sonarsource.com/editions/developer.html) and [above](https://redirect.sonarsource.com/editions/editions.html)._
-<!-- /sonarqube -->
+_C/C++/Objective-C analysis is available starting with [Developer Edition](https://redirect.sonarsource.com/editions/developer.html)._
 
 <!-- static -->
 <!-- update_center:cpp -->
diff --git a/server/sonar-docs/src/pages/analysis/languages/cobol.md b/server/sonar-docs/src/pages/analysis/languages/cobol.md
index 39789137e04..3f511c3eaf8 100644
--- a/server/sonar-docs/src/pages/analysis/languages/cobol.md
+++ b/server/sonar-docs/src/pages/analysis/languages/cobol.md
@@ -3,11 +3,7 @@ title: COBOL
 url: /analysis/languages/cobol/
 ---
 
-<!-- sonarqube -->
-
-_Cobol analysis is available as part of the [Enterprise Edition](https://redirect.sonarsource.com/editions/enterprise.html) and [above](https://redirect.sonarsource.com/editions/editions.html)._
-
-<!-- /sonarqube -->
+_Cobol analysis is available starting in [Enterprise Edition](https://redirect.sonarsource.com/editions/enterprise.html)._
 
 <!-- static -->
 <!-- update_center:cobol -->
diff --git a/server/sonar-docs/src/pages/analysis/languages/pli.md b/server/sonar-docs/src/pages/analysis/languages/pli.md
index 2a0e6f09e3f..8b8accf67f9 100644
--- a/server/sonar-docs/src/pages/analysis/languages/pli.md
+++ b/server/sonar-docs/src/pages/analysis/languages/pli.md
@@ -3,7 +3,7 @@ title: PLI
 url: /analysis/languages/pli/
 ---
 
-_PL/I is available as part of [Enterprise Edition](https://redirect.sonarsource.com/editions/enterprise.html) and [above](https://redirect.sonarsource.com/editions/editions.html)._
+_PL/I is available starting in [Enterprise Edition](https://redirect.sonarsource.com/editions/enterprise.html)._
 
 <!-- static -->
 <!-- update_center:pli -->
diff --git a/server/sonar-docs/src/pages/analysis/languages/rpg.md b/server/sonar-docs/src/pages/analysis/languages/rpg.md
index 78d1cfbef51..6d4adf17de8 100644
--- a/server/sonar-docs/src/pages/analysis/languages/rpg.md
+++ b/server/sonar-docs/src/pages/analysis/languages/rpg.md
@@ -3,7 +3,7 @@ title: RPG
 url: /analysis/languages/rpg/
 ---
 
-_RPG is available as part of [Enterprise Edition](https://redirect.sonarsource.com/editions/enterprise.html) and [above](https://redirect.sonarsource.com/editions/editions.html)._
+_RPG is available starting in [Enterprise Edition](https://redirect.sonarsource.com/editions/enterprise.html)._
 
 <!-- static -->
 <!-- update_center:rpg -->
diff --git a/server/sonar-docs/src/pages/analysis/languages/vb6.md b/server/sonar-docs/src/pages/analysis/languages/vb6.md
index 911a5e9b659..19f89ff5435 100644
--- a/server/sonar-docs/src/pages/analysis/languages/vb6.md
+++ b/server/sonar-docs/src/pages/analysis/languages/vb6.md
@@ -3,11 +3,7 @@ title: VB6
 url: /analysis/languages/vb6/
 ---
 
-<!-- sonarqube -->
-
-_VB6 analysis is available as part of the [Enterprise Edition](https://redirect.sonarsource.com/editions/enterprise.html) and [above](https://redirect.sonarsource.com/editions/editions.html)._
-
-<!-- /sonarqube -->
+_VB6 analysis is available starting in [Enterprise Edition](https://redirect.sonarsource.com/editions/enterprise.html)._
 
 <!-- static -->
 <!-- update_center:vb -->
diff --git a/server/sonar-docs/src/pages/analysis/pr-decoration.md b/server/sonar-docs/src/pages/analysis/pr-decoration.md
index 8a1e86eb7da..37a35171121 100644
--- a/server/sonar-docs/src/pages/analysis/pr-decoration.md
+++ b/server/sonar-docs/src/pages/analysis/pr-decoration.md
@@ -3,7 +3,7 @@ title: Decorating Pull Requests
 url: /analysis/pr-decoration/
 ---
 
-_Pull Request decoration is available as part of [Developer Edition](https://redirect.sonarsource.com/editions/developer.html) and [above](https://www.sonarsource.com/plans-and-pricing/)._
+_Pull Request decoration is available starting in [Developer Edition](https://redirect.sonarsource.com/editions/developer.html)._
 
 You can add SonarQube analysis and a Quality Gate to your Pull Requests (PR) in your ALM provider's interface.
 
diff --git a/server/sonar-docs/src/pages/analysis/pull-request.md b/server/sonar-docs/src/pages/analysis/pull-request.md
index 7520d1c73b8..7158d0af463 100644
--- a/server/sonar-docs/src/pages/analysis/pull-request.md
+++ b/server/sonar-docs/src/pages/analysis/pull-request.md
@@ -3,7 +3,7 @@ title: Overview
 url: /analysis/pull-request/
 ---
 
-_Pull Request analysis is available as part of [Developer Edition](https://redirect.sonarsource.com/editions/developer.html) and [above](https://www.sonarsource.com/plans-and-pricing/)._
+_Pull Request analysis is available starting in [Developer Edition](https://redirect.sonarsource.com/editions/developer.html)._
 
 You can see your Pull Requests in SonarQube from the Branches and Pull Requests dropdown menu of your project.
 
diff --git a/server/sonar-docs/src/pages/analysis/scan/sonarscanner-for-azure-devops.md b/server/sonar-docs/src/pages/analysis/scan/sonarscanner-for-azure-devops.md
index da23a9fda77..058935cedac 100644
--- a/server/sonar-docs/src/pages/analysis/scan/sonarscanner-for-azure-devops.md
+++ b/server/sonar-docs/src/pages/analysis/scan/sonarscanner-for-azure-devops.md
@@ -149,7 +149,7 @@ When creating a build definition you can filter the list of available tasks by t
 
 ## Branch and Pull Request analysis
 
-_Branch and Pull Request analysis are available as part of [Developer Edition](https://redirect.sonarsource.com/editions/developer.html) and [above](https://www.sonarsource.com/plans-and-pricing/)_
+_Branch and Pull Request analysis are available starting in [Developer Edition](https://redirect.sonarsource.com/editions/developer.html)._
 
 ### Branches
 When a build is run on a branch of your project, the extension automatically configures the analysis to be pushed to the relevant project branch in {instance}. The same build definition can apply to all your branches, whatever type of Git repository you are analyzing,
diff --git a/server/sonar-docs/src/pages/branches/branches-faq.md b/server/sonar-docs/src/pages/branches/branches-faq.md
index ee8ce8ebfae..6ce80bf71d5 100644
--- a/server/sonar-docs/src/pages/branches/branches-faq.md
+++ b/server/sonar-docs/src/pages/branches/branches-faq.md
@@ -3,7 +3,7 @@ title: Branch FAQ
 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/)._
+_Branch analysis is available starting in [Developer Edition](https://redirect.sonarsource.com/editions/developer.html)._
 
 ## 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 **Project Settings > Branches & Pull Requests**. See the [Branches Analysis](/branches/overview/) for more information on keeping inactive branches.
diff --git a/server/sonar-docs/src/pages/branches/overview.md b/server/sonar-docs/src/pages/branches/overview.md
index b010a801512..85f7304b3f6 100644
--- a/server/sonar-docs/src/pages/branches/overview.md
+++ b/server/sonar-docs/src/pages/branches/overview.md
@@ -3,7 +3,7 @@ title: Branch Analysis
 url: /branches/overview/
 ---
 
-_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/)._
+_Branch analysis is available starting in [Developer Edition](https://redirect.sonarsource.com/editions/developer.html)._
 
 ## Overview
 
diff --git a/server/sonar-docs/src/pages/instance-administration/delegated-auth.md b/server/sonar-docs/src/pages/instance-administration/delegated-auth.md
index 49317096e27..3c43fa85dac 100644
--- a/server/sonar-docs/src/pages/instance-administration/delegated-auth.md
+++ b/server/sonar-docs/src/pages/instance-administration/delegated-auth.md
@@ -34,7 +34,7 @@ All the parameters required to activate and configure this feature are available
 Using Http header authentication is an easy way integrate your SonarQube deployment with an in-house SSO implementation.
 
 ## GitHub Authentication
-You can delegate authentication to GitHub Enterprise and GitHub.com using a dedicated GitHub OAuth application. Alternately, if you're using the pull request decoration provided as part of [Developer Edition](https://redirect.sonarsource.com/editions/developer.html) and [above](https://www.sonarsource.com/plans-and-pricing/) you can harness the [GitHub application needed for PR decoration](/analysis/pr-decoration/) to also provide authentication.
+You can delegate authentication to GitHub Enterprise and GitHub.com using a dedicated GitHub OAuth application. Alternately, if you're using the pull request decoration provided starting in [Developer Edition](https://redirect.sonarsource.com/editions/developer.html), you can harness the [GitHub application needed for PR decoration](/analysis/pr-decoration/) to also provide authentication.
 
 ### Dedicated GitHub OAuth application
 1. You'll need to first create a GitHub OAuth application. Click [here](https://developer.github.com/apps/building-oauth-apps/creating-an-oauth-app/) for general instructions:
diff --git a/server/sonar-docs/src/pages/instance-administration/license-manager.md b/server/sonar-docs/src/pages/instance-administration/license-manager.md
index 98b0dd043bb..c43e7584ed8 100644
--- a/server/sonar-docs/src/pages/instance-administration/license-manager.md
+++ b/server/sonar-docs/src/pages/instance-administration/license-manager.md
@@ -4,7 +4,7 @@ url: /instance-administration/license-manager/
 ---
 
 ## License Manager
-_With [Developer Edition](https://redirect.sonarsource.com/editions/developer.html) and [above](https://www.sonarsource.com/plans-and-pricing/), you can access the License Manager at **Administration > Configuration> License Manager**._
+_Starting in [Developer Edition](https://redirect.sonarsource.com/editions/developer.html), you can access the License Manager at **Administration > Configuration> License Manager**._
 
 You can use the License Manager to retrieve your server ID (required for obtaining a License Key) and configure your SonarSource-provided License key.
 
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 804532d7a3b..8cd9090e407 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 **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 override the global New Code Period by setting a project-level New Code Period from the project page at **Project Settings > New Code Period**. Starting in [Developer Edition](https://redirect.sonarsource.com/editions/developer.html), 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:
 
@@ -23,10 +23,10 @@ You can set a project's New Code Period to the following:
 * **Number of days** – 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.
 * **Specific analysis** – Choose a previous analysis as your New Code Period. The New Code Period will show any changes made since that analysis. 
 
-   **Note:** For Community Edition, you can set the New Code Period to a specific past analysis at the project-level because Community Edition doesn't support multiple branches. [Developer Edition](https://redirect.sonarsource.com/editions/developer.html) and [above](https://www.sonarsource.com/plans-and-pricing/) let you set the New Code Period to a specific analysis at the branch level. Each branch can be set to one of the branch's specific past analyses. See the following section for information on setting a branch-level New Code Period. 
+   **Note:** For Community Edition, you can set the New Code Period to a specific past analysis at the project-level because Community Edition doesn't support multiple branches. Starting in [Developer Edition](https://redirect.sonarsource.com/editions/developer.html), you can set the New Code Period to a specific analysis at the branch level. Each branch can be set to one of the branch's specific past analyses. See the following section for information on setting a branch-level New Code Period. 
 
 ### Setting a branch-level New Code Period
-_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/)._  
+_Branch analysis is available starting in [Developer Edition](https://redirect.sonarsource.com/editions/developer.html)._  
 For projects with multiple branches, you can set a New Code Period for each branch from the **Actions** column of the branches table on the project's **New Code Period** settings page.
 
 You can set a branch's New Code Period to the following:
diff --git a/server/sonar-docs/src/pages/user-guide/clean-as-you-code.md b/server/sonar-docs/src/pages/user-guide/clean-as-you-code.md
index 69b285eb5d7..6b0e617ed68 100644
--- a/server/sonar-docs/src/pages/user-guide/clean-as-you-code.md
+++ b/server/sonar-docs/src/pages/user-guide/clean-as-you-code.md
@@ -11,7 +11,7 @@ Clean as You Code is an approach to Code Quality that eliminates a lot of the ch
 
 With Clean as You Code, your focus is always on New Code (code that has been added or changed in your New Code Period) and making sure the code you write today is clean and safe. 
 
-The New Code Period can be set at different levels (global, project, and with [Developer Edition](https://redirect.sonarsource.com/editions/developer.html) and [above](https://www.sonarsource.com/plans-and-pricing/) at the branch level). Depending on the level at which your New Code Period is set, you can change the starting point of your New Code Period to fit your situation.
+The New Code Period can be set at different levels (global, project, and starting in [Developer Edition](https://redirect.sonarsource.com/editions/developer.html)  at the branch level). Depending on the level at which your New Code Period is set, you can change the starting point of your New Code Period to fit your situation.
 
 For more information on the New Code Period and setting it, check out [Setting Your New Code Period](/project-administration/new-code-period/).
 
diff --git a/server/sonar-docs/src/pages/user-guide/security-reports.md b/server/sonar-docs/src/pages/user-guide/security-reports.md
index 46127c9502d..40831853f82 100644
--- a/server/sonar-docs/src/pages/user-guide/security-reports.md
+++ b/server/sonar-docs/src/pages/user-guide/security-reports.md
@@ -3,7 +3,7 @@ title: Security Reports
 url: /user-guide/security-reports/
 ---
 
-*Security Reports are available as part of the [Enterprise Edition](https://redirect.sonarsource.com/editions/enterprise.html) and [above](https://www.sonarsource.com/plans-and-pricing/).*
+*Security Reports are available starting in [Enterprise Edition](https://redirect.sonarsource.com/editions/enterprise.html).*
 
 ## What do Security Reports show?
 Security Reports quickly give you the big picture on your application's security, with breakdowns of just where you stand in regard to each of the [OWASP Top 10](https://www.owasp.org/index.php/Top_10-2017_Top_10), and [SANS Top 25](https://www.sans.org/top25-software-errors) categories, and [CWE](https://cwe.mitre.org/)-specific details.
diff --git a/server/sonar-docs/src/pages/user-guide/sonarlint-notifications.md b/server/sonar-docs/src/pages/user-guide/sonarlint-notifications.md
index a2726aaf9e4..8660b19a4ae 100644
--- a/server/sonar-docs/src/pages/user-guide/sonarlint-notifications.md
+++ b/server/sonar-docs/src/pages/user-guide/sonarlint-notifications.md
@@ -2,11 +2,10 @@
 title: SonarLint Smart Notifications
 url: /user-guide/sonarlint-notifications/
 ---
-<!-- sonarqube -->
-_SonarLint Smart Notifications is available as part of the [Developer Edition](https://redirect.sonarsource.com/editions/developer.html) and [above](https://www.sonarsource.com/plans-and-pricing/)._
-<!-- /sonarqube -->
 
-Smart notifications allow developers using Connected Mode in SonarLint to receive in-IDE notifications from {instance} when:
+_SonarLint Smart Notifications are available starting in [Developer Edition](https://redirect.sonarsource.com/editions/developer.html)._
+
+Smart notifications allow developers using Connected Mode in SonarLint to receive in-IDE notifications from SonarQube when:
 
 * the Quality Gate status (failed / success) of a project /solution _open in the IDE_ changes
 * a {instance} analysis raises new issues _introduced by this developer in a project /solution open in the IDE_
@@ -14,6 +13,4 @@ Smart notifications allow developers using Connected Mode in SonarLint to receiv
 ## Activate/deactivate Notifications
 The activation or deactivation of notifications must be done individually, by each developer directly in SonarLint (on the IDE side).
 
-<!-- sonarqube -->
-Receiving notifications is configurable on the SonarLint side on a {instance} server-by-server basis.
-<!-- /sonarqube -->
+Receiving notifications is configurable on the SonarLint side on a SonarQube server-by-server basis.
\ No newline at end of file