Fix after review

Author: guillaume-dequenne

README.md

@@ -79,13 +79,13 @@ By default, the scanner will expect the `pyproject.toml` file to be present in t
 However, its path can be provided manually through the `toml.path` ([SCANPY-40](https://sonarsource.atlassian.net/jira/software/c/projects/PYSCAN/issues/PYSCAN-40)) CLI argument as well as through the `sonar.projectHome` argument. For instance:
 
 ```
-pysonar -Dtoml.path="path/to/pyproject.toml"
+pysonar --toml.path "path/to/pyproject.toml"
 ```
 
 Or:
 
 ```
-pysonar -Dsonar.projectHome="path/to/projectHome"
+pysonar --sonar-project-home "path/to/projectHome"
 ```
 
 

tests/its/utils/pysonar-scanner-debug.py tests/its/utils/pysonar-debug.pytests/its/utils/pysonar-scanner-debug.py renamed to tests/its/utils/pysonar-debug.py

@@ -19,11 +19,11 @@
 #
 """
 This module is the entry point for debugging the pysonar scanner in the its.
-The pysonar-scanner-debug is started with the working directory set to the root of the project, so that python
+The pysonar-debug is started with the working directory set to the root of the project, so that python
 (and pydebug by extension) can find the pysonar-scanner-debug module. However, since the scanner should run in the
  analyzed project, the working directory is changed to the root of the analyzed project before running the scanner.
 
-The pysonar-scanner-debug expects the PYSONAR_SCANNER_DEBUG_WORKDIR environment variable to be set to the directory
+The pysonar-debug expects the PYSONAR_SCANNER_DEBUG_WORKDIR environment variable to be set to the directory
 where the scanner should be run. This is set to the directory containing the sources to be analyzed.
 """