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

summaryrefslogtreecommitdiffhomepage
path: root/docs/release-notes.md
diff options
context:
space:
mode:
authorJulien Brianceau2021-04-07 20:43:50 +0200
committerGitHub2021-04-07 20:43:50 +0200
commite8cdfdca87ebacd993befdd08ea6aa7e8068ef3d (patch)
tree9342e9569feb9178b600d6b95cb1f7d7ed380861 /docs/release-notes.md
parenta5abec9cb5d7a26b94d3da24fd239c28ac2dbf91 (diff)
downloadcatch3-e8cdfdca87ebacd993befdd08ea6aa7e8068ef3d.tar.gz
Fix typos in the code base (#2206)
Note that only documentation and comments are impacted by this change.
Diffstat (limited to 'docs/release-notes.md')
-rw-r--r--docs/release-notes.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/release-notes.md b/docs/release-notes.md
index a3893589..034df174 100644
--- a/docs/release-notes.md
+++ b/docs/release-notes.md
@@ -74,7 +74,7 @@ new design.
* Will Catch2 again distribute single-header version in the future?
* No. But we do provide sqlite-style amalgamated distribution option. This means that you can download just 1 .cpp file and 1 header and place them next to your own sources. However, doing this has downsides similar to using the `catch_all.hpp` header.
* Why the big breaking change caused by replacing `catch.hpp` with `catch_all.hpp`?
- * The convenience header `catch_all.hpp` exists for two reasons. One of them is to provide a way for quick migration from Catch2, the second one is to provide a simple way to test things with Catch2. Using it for migration has one drawback in that it is **big**. This means that including it _will_ cause significant compile time drag, and so using it to migrate should be a concious decision by the user, not something they can just stumble into unknowingly.
+ * The convenience header `catch_all.hpp` exists for two reasons. One of them is to provide a way for quick migration from Catch2, the second one is to provide a simple way to test things with Catch2. Using it for migration has one drawback in that it is **big**. This means that including it _will_ cause significant compile time drag, and so using it to migrate should be a conscious decision by the user, not something they can just stumble into unknowingly.
### (Potentially) Breaking changes