Apply suggestions from code review

Co-authored-by: Riccardo <riccardo.odone@gmail.com>

Author: ArturT

docusaurus/docs/jest/cookbook.md

@@ -46,15 +46,15 @@ npx knapsack-pro-jest --config=jest.config.e2e.js
 
 Each CI node executes multiple batches of tests in Knapsack Pro [Queue Mode](../overview/index.mdx#queue-mode-dynamic-split), and each batch starts a new Jest process. By default, a coverage report generated by each batch overwrites the previous one, which can lead to incomplete coverage data.
 
-To avoid this, you can configure Knapsack Pro to generate a separate coverage report for each batch by setting the environment variable:
+To avoid this, you can configure Knapsack Pro to generate a separate coverage report for each batch by setting the following environment variable:
 
 ```bash
 export KNAPSACK_PRO_COVERAGE_DIRECTORY=coverage
 
 npx knapsack-pro-jest --coverage
 ```
 
-This ensures each batch creates a unique subfolder for its coverage report, preventing overwrites.
+This ensures each batch creates a unique subfolder for its coverage report, preventing overwrites:
 
 ```
 coverage
@@ -86,7 +86,7 @@ coverage
         └── lcov.info
 ```
 
-To merge the reports you may consider [this script](https://github.com/jestjs/jest/issues/2418#issuecomment-478932514).
+You can merge the reports with [this script](https://github.com/jestjs/jest/issues/2418#issuecomment-478932514).
 
 ## Generate XML reports
 

docusaurus/docs/jest/troubleshooting.md

@@ -51,4 +51,4 @@ Make sure [`KNAPSACK_PRO_TEST_FILE_PATTERN`](reference.md#knapsack_pro_test_file
 
 ## Missing Jest coverage data
 
-Please see the [Jest coverage configuration](cookbook.md#generate-code-coverage-reports).
+See [how to configure code coverage](cookbook.md#generate-code-coverage-reports).