diff options
| author | Christine Curry <89850583+christine-curry-sonarsource@users.noreply.github.com> | 2022-06-14 14:29:39 +0100 |
|---|---|---|
| committer | sonartech <sonartech@sonarsource.com> | 2022-06-14 20:02:51 +0000 |
| commit | 55e999d240d2b93c71f3802f72a3d35bae7f1794 (patch) | |
| tree | 534549fb3575ddafa6e9b0dccc2070190924ccb8 /server/sonar-docs | |
| parent | 921cf12efecec4e87848ee2dcfff948f0e7f3980 (diff) | |
| download | sonarqube-55e999d240d2b93c71f3802f72a3d35bae7f1794.tar.gz sonarqube-55e999d240d2b93c71f3802f72a3d35bae7f1794.zip | |
SONAR-16487 Update Webhooks and Rules docs - fix terminology (#6103)
Terminology Fix
Diffstat (limited to 'server/sonar-docs')
| -rw-r--r-- | server/sonar-docs/src/pages/project-administration/webhooks.md | 2 | ||||
| -rw-r--r-- | server/sonar-docs/src/pages/user-guide/rules.md | 4 |
2 files changed, 3 insertions, 3 deletions
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. |