doc: Improve syntax of ellipsis placeholders

docs/troubleshooting-coverage-cli-issues.md

@@ -56,7 +56,7 @@ bash <(curl -Ls https://coverage.codacy.com/get.sh) report -r <coverage report f
 If you're using dotCover to generate coverage reports for your C# projects, you must use the dotCover detailedXML report format as follows:
 
 ```bash
-dotCover.exe cover ... --reportType=DetailedXml
+dotCover.exe cover <...> --reportType=DetailedXml
 ```
 
 ## JsonParseException while uploading coverage data
@@ -70,14 +70,14 @@ There are some ways you can solve this:
 -   **If you're using dotCover to generate coverage reports for your C# projects**, you should [exclude xUnit files](https://www.jetbrains.com/help/dotcover/Running_Coverage_Analysis_from_the_Command_LIne.html#filters_cmd) from the coverage analysis as follows:
 
     ```bash
-    dotCover.exe cover ... /Filters=-:xunit*
+    dotCover.exe cover <...> /Filters=-:xunit*
     ```
 
     By default, dotCover includes xUnit files in the coverage analysis and this results in larger coverage reports. This filter helps ensure that the resulting coverage data does not exceed the size limit accepted by the Codacy API when uploading the results.
 
 ## Connect timed out while uploading coverage data
 
-If you get a `Error doing a post to ... connect timed out` error while uploading your coverage data to Codacy it means that the Codacy Coverage Reporter is timing out while connecting to the Codacy API. This typically happens if you're uploading coverage data for larger repositories.
+If you get a `Error doing a post to <...> connect timed out` error while uploading your coverage data to Codacy it means that the Codacy Coverage Reporter is timing out while connecting to the Codacy API. This typically happens if you're uploading coverage data for larger repositories.
 
 To increase the default timeout while connecting to the Codacy API, use the flag `--http-timeout` to set a value larger than 10000 miliseconds. For example, to set the timeout to 30 seconds: