From 1b0625f51c43453f52027c3d63c6259e855b41ba Mon Sep 17 00:00:00 2001
From: Peeter Piegaze
 <61758048+peeter-piegaze-sonarsource@users.noreply.github.com>
Date: Mon, 23 May 2022 17:06:58 +0200
Subject: Minor fixes (#5945)

---
 .../src/pages/analysis/test-coverage/test-coverage-parameters.md      | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'server/sonar-docs/src/pages/analysis/test-coverage/test-coverage-parameters.md')

diff --git a/server/sonar-docs/src/pages/analysis/test-coverage/test-coverage-parameters.md b/server/sonar-docs/src/pages/analysis/test-coverage/test-coverage-parameters.md
index 90f00b07f61..d5b857dacd6 100644
--- a/server/sonar-docs/src/pages/analysis/test-coverage/test-coverage-parameters.md
+++ b/server/sonar-docs/src/pages/analysis/test-coverage/test-coverage-parameters.md
@@ -7,8 +7,8 @@ _Test coverage reports_ describe the percentage of your code that has been teste
 
 This differs from _test execution reports_, which describe which tests within your test suite have been run during a build. For details, see [Test Execution Parameters](/analysis/test-coverage/test-execution-parameters/).
 
-Test execution reports are not generated by SonarQube itself.
-Much like tests coverage reports, test execution reports must be generated by an external tool and then imported into SonarQube by specifying a parameter telling the scanner where to look for the report.
+Test coverage reports are not generated by SonarQube itself.
+They must be generated by an external tool and then imported into SonarQube by specifying a parameter telling the scanner where to look for the report.
 The data is then displayed in your SonarQube analysis.
 
 Below, you will find language- and tool-specific analysis parameters for importing test coverage reports.
-- 
cgit v1.2.3