SONAR-17022 SonarQube Branch Analysis clarification (#6285)

diff --git a/server/sonar-docs/src/pages/analysis/analysis-parameters.md b/server/sonar-docs/src/pages/analysis/analysis-parameters.md
index a88ba5da6dd3ce610f69663da49a067e2b66e6b8..0ade8caf24ab4b0e20749316e15f2aa9725d2d57 100644 (file)
--- a/server/sonar-docs/src/pages/analysis/analysis-parameters.md
+++ b/server/sonar-docs/src/pages/analysis/analysis-parameters.md
@@ -77,7 +77,7 @@ Key | Description | Default
 `sonar.scm.revision`| Overrides the revision, for instance the Git sha1, displayed in analysis results. By default value is provided by the CI environment or guessed by the checked-out sources.| 
 `sonar.buildString`| The string passed with this property will be stored with the analysis and available in the results of `api/project_analyses/search`, thus allowing you to later identify a specific analysis and obtain its ID for use with `api/project_analyses/set_baseline`. | |
 `sonar.analysis.[yourKey]`| This property stub allows you to insert custom key/value pairs into the analysis context, which will also be passed forward to [webhooks](/project-administration/webhooks/). | |
-`sonar.newCode.referenceBranch`| Defines the new code period for this branch to use the given branch as a reference branch, overriding the server's setting. See [New Code Period](/project-administration/new-code-period/). 
+`sonar.newCode.referenceBranch`| Set the New Code Period reference branch for the branch under analysis. This parameter overrides project-level settings for the branch under analysis, and is only applied on the first analysis of the branch. See [New Code Period](/project-administration/new-code-period/). 
 
 ### Duplications
 Key | Description | Default