From 0c3d6e8e5a4c19c40c9266a8592100c17b205f50 Mon Sep 17 00:00:00 2001 From: Wouter Admiraal Date: Mon, 23 Aug 2021 17:31:24 +0200 Subject: [PATCH] SONAR-12560 Better explain the concept of bugs in documentation --- server/sonar-docs/src/pages/user-guide/issues.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/server/sonar-docs/src/pages/user-guide/issues.md b/server/sonar-docs/src/pages/user-guide/issues.md index ff402c13bcf..7e3b1a9a4e0 100644 --- a/server/sonar-docs/src/pages/user-guide/issues.md +++ b/server/sonar-docs/src/pages/user-guide/issues.md @@ -9,7 +9,7 @@ While running an analysis, SonarQube raises an issue every time a piece of code There are three types of issues: -1. **Bug** – A coding error that will break your code and needs to be fixed immediately. +1. **Bug** – A coding mistake that can lead to an error or unexpected behavior at runtime. 1. **Vulnerability** – A point in your code that's open to attack. 1. **Code Smell** – A maintainability issue that makes your code confusing and difficult to maintain. -- 2.39.5