From: Christine Curry <89850583+christine-curry-sonarsource@users.noreply.github.com>
Date: Tue, 14 Jun 2022 13:29:39 +0000 (+0100)
Subject: SONAR-16487 Update Webhooks and Rules docs - fix terminology (#6103)
X-Git-Tag: 9.6.0.59041~366
X-Git-Url: https://source.dussan.org/?a=commitdiff_plain;h=55e999d240d2b93c71f3802f72a3d35bae7f1794;p=sonarqube.git

SONAR-16487 Update Webhooks and Rules docs - fix terminology (#6103)

Terminology Fix
---

diff --git a/server/sonar-docs/src/pages/project-administration/webhooks.md b/server/sonar-docs/src/pages/project-administration/webhooks.md
index 4556590d9ed..339210aff5c 100644
--- a/server/sonar-docs/src/pages/project-administration/webhooks.md
+++ b/server/sonar-docs/src/pages/project-administration/webhooks.md
@@ -100,7 +100,7 @@ The Payload is a JSON document which includes:
 
 ## Securing your webhooks
 
-After you've configured your server to receive payloads, you want to be sure that the payloads you receive are initiated by {instance} and not by hackers. You can do this by validating a hash signature that ensures that requests originate from {instance}. 
+After you've configured your server to receive payloads, you want to be sure that the payloads you receive are initiated by {instance} and not by attackers. You can do this by validating a hash signature that ensures that requests originate from {instance}. 
 
 ### Setting your secret
 
diff --git a/server/sonar-docs/src/pages/user-guide/rules.md b/server/sonar-docs/src/pages/user-guide/rules.md
index 2167c0b556c..dd0acdd7669 100644
--- a/server/sonar-docs/src/pages/user-guide/rules.md
+++ b/server/sonar-docs/src/pages/user-guide/rules.md
@@ -90,7 +90,7 @@ The {instance} Quality Model divides rules into four categories: Bugs, Vulnerabi
 If the answer is "yes", then it's a Bug rule.  
 If not...
 
-**Is the rule about code that could be exploited by a hacker?**  
+**Is the rule about code that could be exploited by an attacker?**  
 If so, then it's a Vulnerability rule.  
 If not...
 
@@ -128,7 +128,7 @@ Likelihood: **What's the probability that the Worst Thing will happen?**
 ### Vulnerabilities
 Impact: **Could the exploitation of the Worst Thing result in significant damage to your assets or your users?**
 
-Likelihood: **What is the probability that a hacker will be able to exploit the Worst Thing?**
+Likelihood: **What is the probability that an attacker will be able to exploit the Worst Thing?**
 
 ### Security Hotspots
 Security Hotspots are not assigned severities as it is unknown whether there is truly an underlying vulnerability until they are reviewed.