Update docs for 'new code' in SLB

server/sonar-docs/src/pages/branches/index.md

@@ -25,7 +25,7 @@ This corresponds to Pull/Merge Requests or Feature Branches. This kind of branch
 * will disappear quickly
 * will be merged rapidly to prevent integration issues
 * is developed for a given version, so the version does not change,
-  and there is no New Code period concept as such; it's all new code
+  and there is no way to set the New Code period; everything that has been changed in the branch is new code
 * tracks all the new issues related to the code that changed on it.
 
 ![conceptual illustration of short-lived branches.](/images/short-lived-branch-concept.png)

server/sonar-docs/src/pages/branches/short-lived-branches.md

@@ -37,6 +37,6 @@ Branch settings and quality profiles default to those set for the master branch,
 
 ## Known Limitations
 
-* Only the number of bugs, code smells, vulnerabilities and files are computed. As a consequence, you have no way to get a Quality Gate status as such on short-lived branch.
+* Only the issue-focused, hard-coded quality gate is available on a short-lived branch.
 * You cannot connect SonarLint to a short-lived branch.
 * Analysis of a short-lived branch based on another short-lived branch is not supported.