drop in SC where appropriate

diff --git a/server/sonar-docs/src/pages/fixing-the-water-leak.md b/server/sonar-docs/src/pages/fixing-the-water-leak.md
index c56699733f7e5e028019bc7b414a76228aa4da4f..95eb6e0d9044e07a90f76d4c709bcbfd7bf63702 100644 (file)
--- a/server/sonar-docs/src/pages/fixing-the-water-leak.md
+++ b/server/sonar-docs/src/pages/fixing-the-water-leak.md
@@ -8,7 +8,7 @@ Imagine you come home one day to find a puddle of water on the kitchen floor. As
 
 Do you reach for the mop? Or do you try to find the source and fix it? The choice is obvious, right? You find the source of the leak!
 
-So why do anything different with code quality? When you analyze an application with SonarQube and realize that it has a lot of technical debt, the knee-jerk reaction is generally to start remediating – either that or put together a remediation plan. This is like mopping the floor once a day while ignoring the source of the water.
+So why do anything different with code quality? When you analyze an application with <!-- sonarqube -->SonarQube<!-- /sonarqube --><!-- sonarcloud -->SonarCloud<!-- /sonarcloud --> and realize that it has a lot of technical debt, the knee-jerk reaction is generally to start remediating – either that or put together a remediation plan. This is like mopping the floor once a day while ignoring the source of the water.
 
 Typically in this traditional approach, just before release a periodic code quality audit result in findings the developers should act on before releasing. This approach might work in the short term, especially with strong management backing, but it consistently fails in the mid to long run, because:
 
@@ -29,7 +29,7 @@ As a bonus, the code that gets changed the most has the highest maintainability,
 
 ## How to do it
 
-SonarQube offers two main tools to help you find your leaks:
+<!-- sonarqube -->SonarQube<!-- /sonarqube --><!-- sonarcloud -->SonarCloud<!-- /sonarcloud --> offers two main tools to help you find your leaks:
 
 * Leak Period metrics show the variance in your measures between the current code and a specific point you choose in its history, typically the `previous_version`
 * New Code is primarily detected based on SCM "blame" data (starting from the first analysis within your Leak Period), with fallback mechanisms when needed. See SCM integration for more details.