diff options
| author | Chris Thrasher | 2025-04-26 18:46:49 -0600 |
|---|---|---|
| committer | Chris Thrasher | 2025-04-26 22:46:42 -0600 |
| commit | 4c93a595a1d9ecc8aacb7c99f6dbf0f1f2d475fa (patch) | |
| tree | 56d96b6673ea8efa8d88e8735c196446c774be4a /docs | |
| parent | e8f4b60e62b326221ed128a76a864a4f6d76fbf0 (diff) | |
| download | catch3-4c93a595a1d9ecc8aacb7c99f6dbf0f1f2d475fa.tar.gz | |
Fix typos
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/command-line.md | 2 | ||||
| -rw-r--r-- | docs/generators.md | 4 | ||||
| -rw-r--r-- | docs/release-notes.md | 4 | ||||
| -rw-r--r-- | docs/test-fixtures.md | 2 |
4 files changed, 6 insertions, 6 deletions
diff --git a/docs/command-line.md b/docs/command-line.md index 7e69bf12..18c4eeaf 100644 --- a/docs/command-line.md +++ b/docs/command-line.md @@ -123,7 +123,7 @@ specs. You can: This allows test cases that are tagged with **either** "[some-tag]" **or** "[other-tag]". A test case with both will obviously also pass the filter. - Note that commas take precendence over simple concatenation. This means + Note that commas take precedence over simple concatenation. This means that `[a][b],[c]` accepts tests that are tagged with either both "[a]" and "[b]", or tests that are tagged with just "[c]". 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. diff --git a/docs/release-notes.md b/docs/release-notes.md index a393a52f..fd0559bd 100644 --- a/docs/release-notes.md +++ b/docs/release-notes.md @@ -93,7 +93,7 @@ * Removed redundant `CTEST_FILE` param when creating the indirection file for `PRE_TEST` discovery mode (#2936) * Rewrote the test discovery logic to use output from the JSON reporter * This means that `catch_discover_tests` now requires CMake 3.19 or newer - * Added `ADD_TAGS_AS_LABELS` option. If specified, each CTest test will be labeled with corrensponding Catch2's test tag + * Added `ADD_TAGS_AS_LABELS` option. If specified, each CTest test will be labeled with corresponding Catch2's test tag * Bumped up the minimum required CMake version to build Catch2 to 3.16 * Meson build now provides option to avoid installing Catch2 * Bazel build is moved to Bzlmod. @@ -175,7 +175,7 @@ ### Improvements * Reintroduced support for GCC 5 and 6 (#2836) * As with VS2017, if they start causing trouble again, they will be dropped again. -* Added workaround for targetting newest MacOS (Sonoma) using GCC (#2837, #2839) +* Added workaround for targeting newest MacOS (Sonoma) using GCC (#2837, #2839) * `CATCH_CONFIG_DEFAULT_REPORTER` can now be an arbitrary reporter spec * Previously it could only be a plain reporter name, so it was impossible to compile in custom arguments to the reporter. * Improved performance of generating 64bit random integers by 20+% diff --git a/docs/test-fixtures.md b/docs/test-fixtures.md index 653b50e0..72a0df95 100644 --- a/docs/test-fixtures.md +++ b/docs/test-fixtures.md @@ -130,7 +130,7 @@ TEST_CASE_PERSISTENT_FIXTURE( MyFixture, "Tests with MyFixture" ) { } ``` -This example demonstates two possible use-cases of this fixture type: +This example demonstrates two possible use-cases of this fixture type: 1. Improve test run times by reducing the amount of expensive and redundant setup and tear-down required. 2. Reusing results from the previous partial run, in the current |