Merge pull request #302 from mathiasgrimm/fix-docs

.gitignore

@@ -0,0 +1 @@
+.idea

optimizing-tests.md

@@ -13,7 +13,7 @@ Finally, it's often useful to focus solely on your test suite's failures. To do
 
 ## Parallel Testing
 
-> Parallel testing in Pest 2 now runs up to 80% faster. This impressive result was only possible thanks to a complete rebuild of the parallel test core system. The new core incorporates advanced techniques for process reuse between test case runs.
+> In Pest 2, Parallel testing achieved a significant milestone, running up to 80% faster than before. This remarkable improvement was the result of a complete rebuild of the parallel test core system, which introduced advanced techniques for process reuse between test case runs. While Pest 3 bring further innovations, this upgrade in Pest 2 marked a turning point for parallel testing performance.
 
 By default, Pest executes your tests sequentially within a single process. However, you can significantly decrease the time needed to run your tests by utilizing the `--parallel` option to run tests concurrently across multiple processes.
 

support-policy.md

@@ -19,7 +19,7 @@ Pest adheres to semantic versioning principles, where the version number `x.y.z`
 - When adding new non-breaking features or improvements, the `y` number is incremented (e.g., 3.10.2 to 3.12.0).
 - When introducing breaking changes, the `x` number is incremented (e.g., 3.10.2 to 4.0.0).
 
-As maintainers of testing frameworks, we take the matter of breaking changes very seriously. Therefore, we always attempt to deliver incredible and robust new features without causing any disruption to the community's test suites. This is precisely why upgrading from Pest 1 to Pest 2 merely required updating your composer.json file, and we assure you that the process will be just as seamless when Pest v3 is released.
+As maintainers of testing frameworks, we take breaking changes very seriously. Our goal is to deliver robust, cutting-edge features without disrupting the community's test suites. This commitment is why upgrading from Pest 1 to Pest 2 was as simple as updating your composer.json file. Similarly, the transition to Pest 3 has been designed to be just as seamless, ensuring an effortless upgrade experience for our users.
 
 ----
 

upgrade-guide.md

@@ -82,7 +82,7 @@ We make an effort to document every potential breaking change, but some of these
 
 > Likelihood Of Impact: High
 
-Pest 2 now requires PHP 8.1.0 or greater. To start migrating from Pest 1 to Pest 2, update the `pestphp/pest` dependency to `^2.0` in your application's `composer.json` file.
+Pest 2 requires PHP 8.1.0 or greater. To start migrating from Pest 1 to Pest 2, update the `pestphp/pest` dependency to `^2.0` in your application's `composer.json` file.
 
 ```diff
 -    "pestphp/pest": "^1.22",