Rename code quality score "Needs Improvement" to "Poor" (#62252)

Co-authored-by: carogalvin <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Anne-Marie <102995847+am-stead@users.noreply.github.com>

Author: 3 people

assets/images/help/code-quality/all-findings-overview-repo.png

@@ -30,7 +30,7 @@ category:
 
 The score distribution chart provides a visual overview of the code health of your organization. Each bubble represents a collection of repositories with the same maintainability and reliability scores.
 * The **position** of each bubble demonstrates the overall health of those repositories. Higher bubbles represent higher maintainability scores, while bubbles further to the right represent higher reliability scores.
-* The **color and border pattern** of a bubble indicate the severity of the lower score for those repositories. For example, a bubble with a "Needs improvement" score in either category will always be red with a dashed border.
+* The **color and border pattern** of a bubble indicate the severity of the lower score for those repositories. For example, a bubble with a "Poor" score in either category will always be red with a dashed border.
 * The **size** of each bubble represents the number of repositories with that particular score combination.
 
 To view the maintainability score, reliability score, and number of repositories represented by a particular bubble, hover over the bubble.

content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/explore-code-quality.md

@@ -45,7 +45,7 @@ These ratings are used to summarize the overall reliability and maintainability
 | **Excellent**        | Codebase demonstrates best practices for reliability and maintainability. | No code quality findings detected                              |
 | **Good**             | Codebase has low-severity issues or minor improvements are suggested. | ≥1 "Note" level finding       |
 | **Fair**             | Codebase has moderate-severity issues that may impact quality, but are not critical. | ≥1 "Warning" level finding              |
-| **Needs Improvement**| Codebase has high-severity issues, including bugs or major maintainability risks. | ≥1 "Error" level finding                |
+| **Poor**             | Codebase has high-severity issues, including bugs or major maintainability risks. | ≥1 "Error" level finding                |
 
 ## Code coverage
 

content/code-security/reference/code-quality/metrics-and-ratings.md

@@ -49,7 +49,7 @@ Use the dashboard **filters** to focus on the highest-severity results first ("E
 
 To improve your repository's maintainability or reliability rating, you must resolve (fix or dismiss) all findings with the highest severity level for that metric.
 
-For example, to improve your repository's "Reliability" metric from **Needs improvement** to **Fair**, you would need to address and resolve all **error-level findings** that impact reliability. If you have one or more error-level findings, your rating cannot be higher than "Needs improvement". See [AUTOTITLE](/code-security/code-quality/reference/metrics-and-ratings).
+For example, to improve your repository's "Reliability" metric from **Poor** to **Fair**, you would need to address and resolve all **error-level findings** that impact reliability. If you have one or more error-level findings, your rating cannot be higher than "Poor". See [AUTOTITLE](/code-security/code-quality/reference/metrics-and-ratings).
 
 ## 3. Investigate a group of findings and understand context