SONAR-13643 Remove references to 'plugin' or 'analyzer'

server/sonar-docs/src/pages/analysis/languages/cobol.md

@@ -249,7 +249,7 @@ To get started, clone the sample plugin project and follow the steps below:
 - Add your newly created jar into the `$SONARQUBE_HOME/extensions/plugins` directory
 - Restart the SonarQube server
 
-If you now look at the COBOL quality profiles, you will find the new coding rule (“Sample check”). Don’t forget to activate it. Run an analysis of a COBOL project, and you will find that an issue was logged at line 5 on every file.
+If you now look at the COBOL Quality Profiles, you will find the new coding rule (“Sample check”). Don’t forget to activate it. Run an analysis of a COBOL project, and you will find that an issue was logged at line 5 on every file.
 
 ### Subscribing to a NodeType
 

server/sonar-docs/src/pages/analysis/languages/php.md

@@ -14,7 +14,7 @@ Discover and update the PHP-specific [properties](/analysis/analysis-parameters/
 
 ## Analyze php.ini Files
 
-The PHP analyzer can analyze `php.ini` files with some specific rules (if these rules are activated in your quality profile). `php.ini` files must be part of the project you are analyzing, meaning the `php.ini` files have to be inside the directories listed in `sonar.sources`. 
+The PHP analyzer can analyze `php.ini` files with some specific rules (if these rules are activated in your Quality Profile). `php.ini` files must be part of the project you are analyzing, meaning the `php.ini` files have to be inside the directories listed in `sonar.sources`. 
 Rules targeting `php.ini` files can be quickly identified through the ["php-ini"](https://rules.sonarsource.com/php/tag/php-ini) tag set on them.
 
 <!-- sonarqube -->

server/sonar-docs/src/pages/analysis/scan/sonarscanner-for-msbuild.md

@@ -89,7 +89,7 @@ Notes:
 
 ## Analysis steps
 ### Begin
-The begin step is executed when you add the `begin` command line argument. It hooks into the MSBuild pipeline, downloads SonarQube quality profiles and settings and prepares your project for the analysis.
+The begin step is executed when you add the `begin` command line argument. It hooks into the MSBuild pipeline, downloads SonarQube Quality Profiles and settings and prepares your project for the analysis.
 
 Command Line Parameters:
 
@@ -107,7 +107,7 @@ For detailed information about all available parameters, see [Analysis Parameter
 
 [[warning]]
 | The "begin" step will modify your build like this:
-| * the active `CodeAnalysisRuleSet` will be updated to match the SonarQube quality profile
+| * the active `CodeAnalysisRuleSet` will be updated to match the SonarQube Quality Profile
 | * `WarningsAsErrors` will be turned off
 |
 | If your build process cannot tolerate these changes we recommend creating a second build job for SonarQube analysis.

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

@@ -15,7 +15,7 @@ This is the default branch and typically corresponds to what's being developed f
 
 ### Settings and Quality Profiles on Branches
 
-Branch settings and quality profiles are the same as those set for the master branch, and by design, it's not possible to configure other values. The New Code Period is the only exception to this as it can be set on a branch-by-branch basis. 
+Branch settings and Quality Profiles are the same as those set for the master branch, and by design, it's not possible to configure other values. The New Code Period is the only exception to this as it can be set on a branch-by-branch basis. 
 
 ### New Code
 

server/sonar-docs/src/pages/instance-administration/notifications.md

@@ -10,7 +10,7 @@ To set the frequency with which the notification queue is processed, set `the so
 Only users who subscribe themselves will get notifications. With only one exception, there is no admin functionality to proactively subscribe another user. If you believe a user should be receiving notifications, then it's time to practice the gentle art of persuasion.
 
 ### The exception
-Notifications will automatically (without user opt-in) be sent to users with Quality Profile Administration rights when built-in quality profiles are updated. These updates can only happen via an upgrade of the relevant analyzer. This type of notification is on by default, and can be toggled globally in **[Administration > General Settings > General](/#sonarqube-admin#/admin/settings/)**.
+Notifications will automatically (without user opt-in) be sent to users with Quality Profile Administration rights when built-in Quality Profiles are updated. These updates can only happen via an upgrade of the relevant analyzer. This type of notification is on by default, and can be toggled globally in **[Administration > General Settings > General](/#sonarqube-admin#/admin/settings/)**.
 
 ## Email Configuration
 To configure the email server, go to **[Administration > General Settings > Email](/#sonarqube-admin#/admin/settings)**.

server/sonar-docs/src/pages/instance-administration/security.md

@@ -132,7 +132,7 @@ Two groups have a special meaning:
 To set global permissions, log in as a System administrator and go to **[Administration > Security > Global Permissions](/#sonarqube-admin#/admin/permissions)**. 
 
 * **Administer System**: All administration functions for the instance: global configuration.
-* **Administer Quality Profiles**: Any action on quality profiles.
+* **Administer Quality Profiles**: Any action on Quality Profiles.
 * **Administer Quality Gates**: Any action on quality gates
 * **Execute Analysis**: Execute analyses (project, view, report, developer), and to get all settings required to perform the analysis, even the secured ones like the scm account password, and so on.
 * **Create Projects**: Initialize the structure of a new project before its first analysis. This permission is also required when doing the very first analysis of a project that has not already been created via the GUI. * **

server/sonar-docs/src/pages/project-administration/managing-project-history.md

@@ -8,7 +8,7 @@ One of the most powerful features of {instance} is that it shows you not just yo
 Typically these aren't things you need to even think about; {instance} just handles them for you. But occasionally you may need to remove a bad snapshot from a project's history or change the housekeeping algorithms.
 
 ## Managing History
-Occasionally, you may need to manually delete a project snapshot, whether because the wrong quality profile was used, or because there was a problem with analysis, and so on. Note that the most recent snapshot (labeled "Last snapshot") can never be deleted.
+Occasionally, you may need to manually delete a project snapshot, whether because the wrong Quality Profile was used, or because there was a problem with analysis, and so on. Note that the most recent snapshot (labeled "Last snapshot") can never be deleted.
 
 [[warning]]
 |**About deleting snapshots**<br/><br/>

server/sonar-docs/src/pages/project-administration/project-existence.md

@@ -6,11 +6,11 @@ url: /project-administration/project-existence/
 Typically, projects are created during their first analysis and never deleted (because old software never dies). For atypical situations, there is the page at **[Administration > Projects > Management](/#sonarqube-admin#/admin/projects_management/)**, which allows you to manage project existence.
 
 ## How do I provision a project before its first analysis?
-Provisioning a project allows you to declare and configure it (define permissions, set quality profiles, etc.) before running the first analysis. To be able to provision projects, you have to be logged in and be granted the Provision Projects permission.
+Provisioning a project allows you to declare and configure it (define permissions, set Quality Profiles, etc.) before running the first analysis. To be able to provision projects, you have to be logged in and be granted the Provision Projects permission.
 
 To provision a new project either use the '+' menu in the top menu or if you have global administration privileges, go to **[Administration > Projects > Management](/#sonarqube-admin#/admin/projects_management/)** and click on **Create Project**. The only required information is the key and the name of your project.
 
-Once the project is provisioned, you can configure it (define permissions, set quality profiles, etc.), and when you're finished with the configuration, you can simply run the project's first analysis.
+Once the project is provisioned, you can configure it (define permissions, set Quality Profiles, etc.), and when you're finished with the configuration, you can simply run the project's first analysis.
 
 You can also provision and configure projects using the Web API.
 

server/sonar-docs/src/pages/sonarcloud/organizations/manage-team.md

@@ -5,9 +5,9 @@ url: /organizations/manage-team/
 
 Members can collaborate on the projects in the organizations to which they belong. Depending on their permisssions within the organization, members can:
 * Analyze projects
-* Manage project settings (permissions, visibility, quality profiles, ...)
+* Manage project settings (permissions, visibility, Quality Profiles, ...)
 * Update issues
-* Manage quality gates and quality profiles
+* Manage quality gates and Quality Profiles
 * Administer the organization itself
 
 Members are managed on the "Members" page of the organization. Only organization administrators can manage members. 

server/sonar-docs/src/pages/user-guide/activity-history.md

@@ -11,7 +11,7 @@ Graphs on the activity page help you understand the evolution of up to three mea
 There are four types of events:
 
 * Quality Gate - the status of the [quality gate](/user-guide/quality-gates/) changed.
-* Profile - the [quality profile](/instance-administration/quality-profiles/) used to analyze the project changed - either the profile was edited, or a different profile was used to analyze the project.
+* Profile - the [Quality Profile](/instance-administration/quality-profiles/) used to analyze the project changed - either the profile was edited, or a different profile was used to analyze the project.
 * Version - the project's version changed.
 * Other - an event was manually created on a snapshot. See [Managing History](/project-administration/managing-project-history/)
 

server/sonar-docs/src/pages/user-guide/concepts.md

@@ -21,7 +21,7 @@ url: /user-guide/concepts/
 | Measure                    | The value of a **metric** for a given file or project at a given time. For example, 125 lines of code on class MyClass or density of duplicated lines of 30.5% on project myProject                                                                                                                                                                                                                                  |
 | Metric                     | A type of measurement. Metrics can have varying values, or **measures**, over time. Examples: number of lines of code, complexity, etc. A metric may be either _qualitative_ (gives a quality indication on the component, E.G. density of duplicated lines, line coverage by tests, etc.) or _quantitative_ (does not give a quality indication on the component, E.G. number of lines of code, complexity, etc.) |
 | New Code definition                | A changeset or period that you're keeping a close watch on for the introduction of new problems in the code. Ideally this is since the `previous_version`, but if you don't use a Maven-like versioning scheme you may need to set a time period such as 21 days, since a specific anaylsis, or use a reference branch.                                                                                                            |
-| Quality Profile            | A set of **rules**. Each **snapshot** is based on a single quality profile. See also [Quality Profiles](/instance-administration/quality-profiles/)                                                                                                                                                                                                                                                         | 
+| Quality Profile            | A set of **rules**. Each **snapshot** is based on a single Quality Profile. See also [Quality Profiles](/instance-administration/quality-profiles/)                                                                                                                                                                                                                                                         | 
 | Rule                | A coding standard or practice which should be followed. Not complying with coding rules leads to **Bugs**, **Vulnerabilities**, **Security Hotspots**, and **Code Smells**. Rules can check quality on code files or unit tests.                                                                                                                                                                                                                                 |
 | Remediation Cost           | The estimated time required to fix Vulnerability and Reliability Issues.                                                                                                                                                                                                                                                                                                                                           |
 | Snapshot                   | A set of **measures** and **issues** on a given project at a given time. A snapshot is generated for each analysis.                                                                                                                                                                                                                                                                                          |

server/sonar-docs/src/pages/user-guide/issues.md

@@ -3,7 +3,7 @@ title: Issues
 url: /user-guide/issues/
 ---
 
-While running an analysis, {instance} raises an issue every time a piece of code breaks a coding rule. The set of coding rules is defined through the associated [quality profile](/instance-administration/quality-profiles/) for each language in the project. 
+While running an analysis, {instance} raises an issue every time a piece of code breaks a coding rule. The set of coding rules is defined through the associated [Quality Profile](/instance-administration/quality-profiles/) for each language in the project. 
 
 ### Issue Types
 
@@ -116,7 +116,7 @@ The Confirm, False Positive, Won't Fix, Severity change, and Resolve actions all
 * **Severity change** - This is the middle ground between the first two options. Yes, it's a problem, but it's not as bad a problem as the rule's default severity makes it out to be. Or perhaps it's actually far worse. Either way, you adjust the severity of the issue to bring it in line with what you feel it deserves.  Requires Administer Issues permission on the project.
 * **Resolve** - If you think you've fixed an open issue, you can Resolve it. If you're right, the next analysis will move it to closed status. If you're wrong, its status will go to re-opened.
 
-If you tend to mark a lot of issues False Positive or Won't Fix, it means that some coding rules are not appropriate for your context. So, you can either completely deactivate them in the quality profile or use issue exclusions to narrow the focus of the rules so they are not used on specific parts (or types of object) of your application. Similarly, making a lot of severity changes should prompt you to consider updating the rule severities in your profiles.
+If you tend to mark a lot of issues False Positive or Won't Fix, it means that some coding rules are not appropriate for your context. So, you can either completely deactivate them in the Quality Profile or use issue exclusions to narrow the focus of the rules so they are not used on specific parts (or types of object) of your application. Similarly, making a lot of severity changes should prompt you to consider updating the rule severities in your profiles.
 
 As you edit issues, the related metrics (e.g. New Bugs), will update automatically, as will the Quality Gate status if it's relevant.
 

server/sonar-docs/src/pages/user-guide/rules.md

@@ -34,7 +34,7 @@ By default, when entering the top menu item "Rules", you will see all the availa
 * **Template**: display rule templates that allow to create custom rules (see later on this page).
 * **Quality Profile**: inclusion in or exclusion from a specific profile
 
-If a quality profile is selected, it is also possible to check for its active severity and whether it is inherited or not. See the Quality Profile documentation for more.
+If a Quality Profile is selected, it is also possible to check for its active severity and whether it is inherited or not. See the Quality Profile documentation for more.
 
 ## Rule Details
 

server/sonar-docs/src/pages/user-guide/security-reports.md

@@ -8,7 +8,7 @@ url: /user-guide/security-reports/
 ## 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.
 
-The Security Reports are fed by the analyzers, which rely on the rules activated in your quality profiles to raise security issues. If there are no rules corresponding to a given OWASP category activated in your Quality Profile, you will get no issues linked to that specific category and the rating displayed will be A. That won't mean you are safe for that category, but that you need to activate more rules (assuming some exist).
+The Security Reports are fed by the analyzers, which rely on the rules activated in your Quality Profiles to raise security issues. If there are no rules corresponding to a given OWASP category activated in your Quality Profile, you will get no issues linked to that specific category and the rating displayed will be A. That won't mean you are safe for that category, but that you need to activate more rules (assuming some exist).
 
 ## What's the difference between a Security Hotspot and a Vulnerability?
 

server/sonar-docs/src/tooltips/quality-profiles/built-in-quality-profile.md

@@ -1 +0,0 @@
-Built-in profiles are provided directly by the language analyzers and may be updated with each new analyzer version. They represent best-practice, minimum rule sets.

server/sonar-web/src/main/js/apps/quality-profiles/components/BuiltInQualityProfileBadge.tsx

@@ -19,8 +19,8 @@
  */
 import * as classNames from 'classnames';
 import * as React from 'react';
+import Tooltip from 'sonar-ui-common/components/controls/Tooltip';
 import { translate } from 'sonar-ui-common/helpers/l10n';
-import DocTooltip from '../../../components/docs/DocTooltip';
 
 interface Props {
   className?: string;
@@ -35,14 +35,8 @@ export default function BuiltInQualityProfileBadge({ className, tooltip = true }
   );
 
   if (tooltip) {
-    return (
-      <DocTooltip
-        doc={import(
-          /* webpackMode: "eager" */ 'Docs/tooltips/quality-profiles/built-in-quality-profile.md'
-        )}>
-        {badge}
-      </DocTooltip>
-    );
+    return <Tooltip overlay={translate('quality_profiles.built_in.description')}>{badge}</Tooltip>;
   }
+
   return badge;
 }

server/sonar-web/src/main/js/apps/quality-profiles/components/__tests__/__snapshots__/BuiltInQualityProfileBadge-test.tsx.snap

@@ -1,15 +1,15 @@
 // Jest Snapshot v1, https://goo.gl/fbAQLP
 
 exports[`should render correctly 1`] = `
-<DocTooltip
-  doc={Promise {}}
+<Tooltip
+  overlay="quality_profiles.built_in.description"
 >
   <div
     className="badge badge-info"
   >
     quality_profiles.built_in
   </div>
-</DocTooltip>
+</Tooltip>
 `;
 
 exports[`should render correctly 2`] = `

server/sonar-web/src/main/js/apps/quality-profiles/details/ProfileHeader.tsx

@@ -92,9 +92,7 @@ export default class ProfileHeader extends React.PureComponent<Props> {
 
         {profile.isBuiltIn && (
           <div className="page-description">
-            {translate('quality_profiles.built_in.description.1')}
-            <br />
-            {translate('quality_profiles.built_in.description.2')}
+            {translate('quality_profiles.built_in.description')}
           </div>
         )}
       </header>

sonar-core/src/main/resources/org/sonar/l10n/core.properties

@@ -522,7 +522,7 @@ visibility.private.description.long=Only members of the organization will be abl
 
 coding_rules.page=Rules
 global_permissions.page=Global Permissions
-global_permissions.page.description=Grant and revoke permissions to make changes at the global level. These permissions include editing quality profiles, executing analysis, and performing global system administration.
+global_permissions.page.description=Grant and revoke permissions to make changes at the global level. These permissions include editing Quality Profiles, executing analysis, and performing global system administration.
 organization_permissions.page.description=Grant and revoke organization permissions. Permissions can be granted to groups or individual users.
 roles.page=Project Permissions
 roles.page.description2=Grant and revoke project-level permissions. Permissions can be granted to groups or individual users.
@@ -1347,7 +1347,7 @@ update_key.are_you_sure_to_change_key=Are you sure you want to change key of "{0
 #
 #------------------------------------------------------------------------------
 project_quality_profile.default_profile=Default
-project_quality_profile.successfully_updated={0} quality profile has been successfully updated.
+project_quality_profile.successfully_updated={0} Quality Profile has been successfully updated.
 
 #------------------------------------------------------------------------------
 #
@@ -1419,7 +1419,7 @@ quality_profiles.changelog.DEACTIVATED=Deactivated
 quality_profiles.changelog.UPDATED=Updated
 quality_profiles.changelog.parameter_reset_to_default_value=Parameter {0} reset to default value
 quality_profiles.deleted_profile=The profile {0} doesn't exist anymore
-quality_profiles.projects_for_default=Every project not specifically associated with a quality profile will be associated to this one by default.
+quality_profiles.projects_for_default=Every project not specifically associated with a Quality Profile will be associated to this one by default.
 quality_profile.x_rules={0} rule(s)
 quality_profile.x_active_rules={0} active rules
 quality_profiles.x_overridden_rules={0} overridden rules
@@ -1427,9 +1427,9 @@ quality_profiles.change_parent=Change Parent
 quality_profiles.all_profiles=All Profiles
 quality_profiles.x_profiles={0} profile(s)
 quality_profiles.x_Profiles={0} Profiles
-quality_profiles.projects.select_hint=Click to associate this project with the quality profile
-quality_profiles.projects.deselect_hint=Click to remove association between this project and the quality profile
-quality_profile.empty_comparison=The quality profiles are equal.
+quality_profiles.projects.select_hint=Click to associate this project with the Quality Profile
+quality_profiles.projects.deselect_hint=Click to remove association between this project and the Quality Profile
+quality_profile.empty_comparison=The Quality Profiles are equal.
 quality_profiles.activate_more=Activate More
 quality_profiles.activate_more_rules=Activate More Rules
 quality_profiles.intro1=Quality Profiles are collections of rules to apply during an analysis.
@@ -1440,13 +1440,13 @@ quality_profiles.list.updated=Updated
 quality_profiles.list.used=Used
 quality_profiles.x_updated_on_y={0}, updated on {1}
 quality_profiles.change_projects=Change Projects
-quality_profiles.not_found=The requested quality profile was not found.
+quality_profiles.not_found=The requested Quality Profile was not found.
 quality_profiles.latest_new_rules=Recently Added Rules
 quality_profiles.latest_new_rules.activated={0}, activated on {1} profile(s)
 quality_profiles.latest_new_rules.not_activated={0}, not yet activated
 quality_profiles.deprecated_rules=Deprecated Rules
 quality_profiles.deprecated_rules_description=These deprecated rules will eventually disappear. You should proactively investigate replacing them.
-quality_profiles.deprecated_rules_are_still_activated=Deprecated rules are still activated on {0} quality profile(s):
+quality_profiles.deprecated_rules_are_still_activated=Deprecated rules are still activated on {0} Quality Profile(s):
 quality_profiles.sonarway_missing_rules=Sonar way rules not included
 quality_profiles.sonarway_missing_rules_description=Recommended rules are missing from your profile
 quality_profiles.stagnant_profiles=Stagnant Profiles
@@ -1455,10 +1455,9 @@ quality_profiles.exporters=Exporters
 quality_profiles.updated_=Updated:
 quality_profiles.used_=Used:
 quality_profiles.built_in=Built-in
-quality_profiles.built_in.description.1=This quality profile is provided by a plugin.
-quality_profiles.built_in.description.2=It will automatically be updated when a new version of the supplying plugin changes its definition.
-quality_profiles.extends_built_in=Because it inherits from a built-in quality profile, this quality profile can be automatically updated when a new version of the corresponding plugin is deployed.
-quality_profiles.default_permissions=Users with the global "Manage Quality Profile" permission can manage this quality profile.
+quality_profiles.built_in.description=This is a built-in Quality Profile that might be updated automatically.
+quality_profiles.extends_built_in=Because this Quality Profile inherits from a built-in Quality Profile, it might be updated automatically.
+quality_profiles.default_permissions=Users with the global "Manage Quality Profile" permission can manage this Quality Profile.
 quality_profiles.grant_permissions_to_more_users=Grant permissions to more users
 quality_profiles.grant_permissions_to_user_or_group=Grant permissions to a user or a group
 quality_profiles.additional_user_groups=Additional users / groups:
@@ -1550,7 +1549,7 @@ rules.status.REMOVED=Removed
 # CODING RULES
 #
 #------------------------------------------------------------------------------
-coding_rules.active_in_all_profiles=The rule is already activated on all available quality profiles.
+coding_rules.active_in_all_profiles=The rule is already activated on all available Quality Profiles.
 coding_rules.activate=Activate
 coding_rules.activate_in=Activate In
 coding_rules.activate_in_quality_profile=Activate In Quality Profile
@@ -1615,22 +1614,22 @@ coding_rules.filter_similar_rules=Filter Similar Rules
 coding_rules.filters.activation=Activation
 coding_rules.filters.activation.active=Active
 coding_rules.filters.activation.inactive=Inactive
-coding_rules.filters.activation.help=Activation criterion is available when a quality profile is selected
+coding_rules.filters.activation.help=Activation criterion is available when a Quality Profile is selected
 coding_rules.filters.active_severity=Active Severity
-coding_rules.filters.active_severity.inactive=Active severity criterion is available when a quality profile is selected
+coding_rules.filters.active_severity.inactive=Active severity criterion is available when a Quality Profile is selected
 coding_rules.filters.availableSince=Available Since
 coding_rules.filters.characteristic=Characteristic
 coding_rules.filters.description=Description
 coding_rules.filters.quality_profile=Quality Profile
 coding_rules.filters.inheritance=Inheritance
-coding_rules.filters.inheritance.inactive=Inheritance criterion is available when an inherited quality profile is selected
+coding_rules.filters.inheritance.inactive=Inheritance criterion is available when an inherited Quality Profile is selected
 coding_rules.filters.inheritance.none=Not Inherited
 coding_rules.filters.inheritance.inherited=Inherited
 coding_rules.filters.inheritance.x_inherited_from_y={0} inherited from "{1}"
 coding_rules.filters.inheritance.overrides=Overridden
 coding_rules.filters.key=Key
 coding_rules.filters.language=Language
-coding_rules.filters.language.inactive=Language criterion is only available when no quality profile is selected
+coding_rules.filters.language.inactive=Language criterion is only available when no Quality Profile is selected
 coding_rules.filters.name=Name
 coding_rules.filters.repository=Repository
 coding_rules.filters.severity=Severity
@@ -2221,9 +2220,9 @@ metric.package_tangle_index.description=Package tangle index
 metric.package_tangle_index.name=Package Tangle Index
 metric.portability.description=Portability
 metric.portability.name=Portability
-metric.profile.description=Selected quality profile
+metric.profile.description=Selected Quality Profile
 metric.profile.name=Profile
-metric.profile_version.description=Selected quality profile version
+metric.profile_version.description=Selected Quality Profile version
 metric.profile_version.name=Profile Version
 metric.projects.description=Number of projects
 metric.projects.name=Projects
@@ -2235,7 +2234,7 @@ metric.public_undocumented_api.description=Public undocumented classes, function
 metric.public_undocumented_api.name=Public Undocumented API
 metric.quality_gate_details.description=The project detailed status with regard to its quality gate
 metric.quality_gate_details.name=Quality Gate Details
-metric.quality_profiles.description=Details of quality profiles used during analysis
+metric.quality_profiles.description=Details of Quality Profiles used during analysis
 metric.quality_profiles.name=Profiles
 metric.reliability.description=Reliability
 metric.reliability.name=Reliability
@@ -2348,7 +2347,7 @@ global_permissions.admin.sonarcloud=Administer Organization
 global_permissions.admin.desc=Ability to perform all administration functions for the instance.
 global_permissions.admin.desc.sonarcloud=Ability to perform all administration functions for the organization.
 global_permissions.profileadmin=Quality Profiles
-global_permissions.profileadmin.desc=Ability to perform any action on quality profiles.
+global_permissions.profileadmin.desc=Ability to perform any action on Quality Profiles.
 global_permissions.gateadmin=Quality Gates
 global_permissions.gateadmin.desc=Ability to perform any action on quality gates.
 global_permissions.scan=Execute Analysis
@@ -2372,7 +2371,7 @@ global_permissions.portfoliocreator.desc=Ability to create a portfolio.
 organizations_permissions.admin=Administer Organization
 organizations_permissions.admin.desc=Ability to perform all administration functions for the organization.
 organizations_permissions.profileadmin=Administer Quality Profiles
-organizations_permissions.profileadmin.desc=Ability to perform any action on quality profiles.
+organizations_permissions.profileadmin.desc=Ability to perform any action on Quality Profiles.
 organizations_permissions.gateadmin=Administer Quality Gates
 organizations_permissions.gateadmin.desc=Ability to perform any action on quality gates.
 organizations_permissions.scan=Execute Analysis
@@ -2816,7 +2815,7 @@ overview.domain.size=Size
 overview.complexity_tooltip.function={0} functions have complexity around {1}
 overview.complexity_tooltip.file={0} files have complexity around {1}
 
-overview.deprecated_profile=This quality profile uses {0} deprecated rules and should be updated.
+overview.deprecated_profile=This Quality Profile uses {0} deprecated rules and should be updated.
 overview.deleted_profile={0} has been deleted since the last analysis.
 
 overview.badges.get_badge.TRK=Get project badges
@@ -2953,7 +2952,7 @@ about_page.read_more=Read More
 about_page.read_documentation=Read documentation
 
 about_page.languages=Multi-Language
-about_page.languages.text=20+ programming languages are supported by SonarQube thanks to our in-house code analyzers, including:
+about_page.languages.text=20+ programming languages are supported by SonarQube, including:
 
 about_page.quality_model=Quality Model
 about_page.quality_model.bugs=track code that is demonstrably wrong or highly likely to yield unexpected behavior.
@@ -2971,7 +2970,7 @@ about_page.quality_gates=Enforce Quality Gate
 about_page.quality_gates.text=Your project's Quality Gate is the set of conditions the project must meet before it can be released into production. The Quality Gate is designed to ensure that the next version's quality will be better than the last.
 
 about_page.standards=Follow Standards
-about_page.standards.text=Code analyzers offer rules that support industry standards. Configure your Quality Profile with standard-related rules to ensure adherence.
+about_page.standards.text=SonarQube offers rules that support industry standards. Configure your Quality Profile with standard-related rules to ensure adherence.
 
 about_page.scanners=Run Analysis With A SonarQube Scanner
 about_page.scanners.text=For a good user experience, choose the scanner that matches your environment best. If you don't know which one suits you best, SonarQube Scanner CLI is the way to go.