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

summaryrefslogtreecommitdiffhomepage
path: root/docs/generators.md
diff options
context:
space:
mode:
authorChris Thrasher2025-04-26 18:46:49 -0600
committerChris Thrasher2025-04-26 22:46:42 -0600
commit4c93a595a1d9ecc8aacb7c99f6dbf0f1f2d475fa (patch)
tree56d96b6673ea8efa8d88e8735c196446c774be4a /docs/generators.md
parente8f4b60e62b326221ed128a76a864a4f6d76fbf0 (diff)
downloadcatch3-4c93a595a1d9ecc8aacb7c99f6dbf0f1f2d475fa.tar.gz
Fix typos
Diffstat (limited to 'docs/generators.md')
-rw-r--r--docs/generators.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/generators.md b/docs/generators.md
index 4e0d99b8..41e01241 100644
--- a/docs/generators.md
+++ b/docs/generators.md
@@ -219,8 +219,8 @@ For floating point generators, the situation is much more complex.
Generally Catch2 only promises reproducibility (or even just correctness!)
on platforms that obey the IEEE-754 standard. Furthermore, reproducibility
only applies between binaries that perform floating point math in the
-same way, e.g. if you compile a binary targetting the x87 FPU and another
-one targetting SSE2 for floating point math, their results will vary.
+same way, e.g. if you compile a binary targeting the x87 FPU and another
+one targeting SSE2 for floating point math, their results will vary.
Similarly, binaries compiled with compiler flags that relax the IEEE-754
adherence, e.g. `-ffast-math`, might provide different results than those
compiled for strict IEEE-754 adherence.