Read-only mirrors. Development, issues and pull requests are on GitHub.

summaryrefslogtreecommitdiffhomepage
path: root/docs/limitations.md
diff options
context:
space:
mode:
authortocic2022-09-09 17:00:39 +0300
committerGitHub2022-09-09 16:00:39 +0200
commitdea1a6abd92b5892956fa474540ab4424a8ca1c3 (patch)
tree8e07cbd23706b57ed9357c681e9122777caae2ae /docs/limitations.md
parent32eae0ecce470639344b121186fb76a240de04b9 (diff)
downloadcatch3-dea1a6abd92b5892956fa474540ab4424a8ca1c3.tar.gz
Fix typos in docs (#2514)
Diffstat (limited to 'docs/limitations.md')
-rw-r--r--docs/limitations.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/limitations.md b/docs/limitations.md
index 55c54738..80471865 100644
--- a/docs/limitations.md
+++ b/docs/limitations.md
@@ -99,7 +99,7 @@ Catch does not support running tests in isolated (forked) processes. While this
Catch2 keeps test execution in one process strictly serial, and there
are no plans to change this. If you find yourself with a test suite
-that takes too long to run and yo uwant to make it parallel, you have
+that takes too long to run and you want to make it parallel, you have
to run multiple processes side by side.
There are 2 basic ways to do that,
@@ -171,7 +171,7 @@ TEST_CASE("b") {
}
```
-If you are seeing a problem like this, i.e. a weird test paths that trigger only under Clang with `libc++`, or only under very specific version of `libstdc++`, it is very likely you are seeing this. The only known workaround is to use a fixed version of your standard library.
+If you are seeing a problem like this, i.e. weird test paths that trigger only under Clang with `libc++`, or only under very specific version of `libstdc++`, it is very likely you are seeing this. The only known workaround is to use a fixed version of your standard library.
### libstdc++, `_GLIBCXX_DEBUG` macro and random ordering of tests