diff --git a/docs/assertions.md b/docs/assertions.md index ece4e106..509abf8a 100644 --- a/docs/assertions.md +++ b/docs/assertions.md @@ -9,7 +9,7 @@ Most test frameworks have a large collection of assertion macros to capture all possible conditional forms (```_EQUALS```, ```_NOTEQUALS```, ```_GREATER_THAN``` etc). -Catch is different. Because it decomposes natural C-style conditional expressions most of these forms are reduced to one or two that you will use all the time. That said there are a rich set of auxilliary macros as well. We'll describe all of these here. +Catch is different. Because it decomposes natural C-style conditional expressions most of these forms are reduced to one or two that you will use all the time. That said there are a rich set of auxiliary macros as well. We'll describe all of these here. Most of these macros come in two forms: diff --git a/docs/command-line.md b/docs/command-line.md index 0c24c3b1..78d83625 100644 --- a/docs/command-line.md +++ b/docs/command-line.md @@ -78,7 +78,7 @@ Wildcards consist of the `*` character at the beginning and/or end of test case Test specs are case insensitive. -If a spec is prefixed with `exclude:` or the `~` character then the pattern matches an exclusion. This means that tests matching the pattern are excluded from the set - even if a prior inclusion spec included them. Subsequent inclusion specs will take precendence, however. +If a spec is prefixed with `exclude:` or the `~` character then the pattern matches an exclusion. This means that tests matching the pattern are excluded from the set - even if a prior inclusion spec included them. Subsequent inclusion specs will take precedence, however. Inclusions and exclusions are evaluated in left-to-right order. Test case examples: @@ -94,7 +94,7 @@ a* ~ab* abc Matches all tests that start with 'a', except those that Names within square brackets are interpreted as tags. -A series of tags form an AND expression wheras a comma-separated sequence forms an OR expression. e.g.: +A series of tags form an AND expression whereas a comma-separated sequence forms an OR expression. e.g.:
[one][two],[three]This matches all tests tagged `[one]` and `[two]`, as well as all tests tagged `[three]` @@ -269,7 +269,7 @@ either before running any tests, after running all tests - or both, depending on When running benchmarks the clock resolution is estimated. Benchmarks are then run for exponentially increasing numbers of iterations until some multiple of the estimated resolution is exceed. By default that multiple is 100, but -it can be overriden here. +it can be overridden here. ## Usage diff --git a/docs/configuration.md b/docs/configuration.md index c2fcc55e..098496d6 100644 --- a/docs/configuration.md +++ b/docs/configuration.md @@ -26,7 +26,7 @@ Although Catch is header only it still, internally, maintains a distinction betw # Reporter / Listener interfaces - CATCH_CONFIG_EXTERNAL_INTERFACES // Brings in neccessary headers for Reporter/Listener implementation + CATCH_CONFIG_EXTERNAL_INTERFACES // Brings in necessary headers for Reporter/Listener implementation Brings in various parts of Catch that are required for user defined Reporters and Listeners. This means that new Reporters and Listeners can be defined in this file as well as in the main file. @@ -79,7 +79,7 @@ This can be useful on certain platforms that do not provide the standard iostrea By default Catch's stringification machinery falls back to a "{?}". To let projects reuse their own existing stringification machinery, this -fallback can be overriden by defining `CATCH_CONFIG_FALLBACK_STRINGIFIER` +fallback can be overridden by defining `CATCH_CONFIG_FALLBACK_STRINGIFIER` to a name of a function that should perform the stringification instead. The provided function must return std::string and must accept any type diff --git a/docs/event-listeners.md b/docs/event-listeners.md index 1ddef0f8..c6625a2e 100644 --- a/docs/event-listeners.md +++ b/docs/event-listeners.md @@ -44,7 +44,7 @@ _Note that you should not use any assertion macros within a Listener!_ ## Events that can be hooked -The following are the methods that can be overriden in the Listener: +The following are the methods that can be overridden in the Listener: ```c++ // The whole test run, starting and ending diff --git a/docs/opensource-users.md b/docs/opensource-users.md index fb46875a..374cb1d2 100644 --- a/docs/opensource-users.md +++ b/docs/opensource-users.md @@ -21,7 +21,7 @@ Listing a project here does not imply endorsement and the plan is to keep these Boost Asio style bindings for ZeroMQ ### [ChakraCore](https://github.com/Microsoft/ChakraCore) -The core part of the Chakra Javascript engine that powers Microsoft Edge +The core part of the Chakra JavaScript engine that powers Microsoft Edge ### [ChaiScript](https://github.com/ChaiScript/ChaiScript) A, header-only, embedded scripting language designed from the ground up to directly target C++ and take advantage of modern C++ development techniques diff --git a/docs/own-main.md b/docs/own-main.md index 18d1b7d3..c74f9f14 100644 --- a/docs/own-main.md +++ b/docs/own-main.md @@ -30,7 +30,7 @@ int main( int argc, char* argv[] ) { ## Amending the config -If you still want Catch to process the command line, but you want to programatically tweak the config, you can do so in one of two ways: +If you still want Catch to process the command line, but you want to programmatically tweak the config, you can do so in one of two ways: ```c++ #define CATCH_CONFIG_RUNNER diff --git a/docs/release-notes.md b/docs/release-notes.md index 76d88be7..dc9f435c 100644 --- a/docs/release-notes.md +++ b/docs/release-notes.md @@ -379,8 +379,8 @@ Cygwin issue with `gettimeofday` - `#define` was not early enough * Cygwin compatibility fixes * Signal handling is no longer compiled by default. * Usage of `gettimeofday` inside Catch should no longer cause compilation errors. -* Improved `-Wparentheses` supression for gcc (#674) - * When compiled with gcc 4.8 or newer, the supression is localized to assertions only +* Improved `-Wparentheses` suppression for gcc (#674) + * When compiled with gcc 4.8 or newer, the suppression is localized to assertions only * Otherwise it is supressed for the whole TU * Fixed test spec parser issue (with escapes in multiple names) @@ -399,7 +399,7 @@ Xml: * C-escape control characters instead of XML encoding them (which requires XML 1.1) * Revert XML output to XML 1.0 * Can provide stylesheet references by extending the XML reporter -* Added description and tags attribites to XML Reporter +* Added description and tags attributes to XML Reporter * Tags are closed and the stream flushed more eagerly to avoid stdout interpolation diff --git a/docs/release-process.md b/docs/release-process.md index 433777b1..9990bab2 100644 --- a/docs/release-process.md +++ b/docs/release-process.md @@ -1,11 +1,11 @@ # How to release -When enough changes have accumulated, it is time to release new version of Catch. This document describes the proces in doing so, that no steps are forgotten. Note that all referenced scripts can be found in the `scripts/` directory. +When enough changes have accumulated, it is time to release new version of Catch. This document describes the process in doing so, that no steps are forgotten. Note that all referenced scripts can be found in the `scripts/` directory. -## Neccessary steps +## Necessary steps -These steps are neccessary and have to be performed before each new release. They serve to make sure that the new release is correct and linked-to from the standard places. +These steps are necessary and have to be performed before each new release. They serve to make sure that the new release is correct and linked-to from the standard places. ### Approval testing @@ -54,7 +54,7 @@ The following steps are optional, and do not have to be performed when releasing ### vcpkg update -Catch is maintaining its own port in Microsoft's package manager [vcpkg](https://github.com/Microsoft/vcpkg). This means that when new version of Catch is released, it should be posted there as well. `updateVcpkgPackage.py` can do a lot of neccessary work for you, it creates a branch and commits neccessary changes. You should review these changes, push and open a PR against vcpkg's upstream. +Catch is maintaining its own port in Microsoft's package manager [vcpkg](https://github.com/Microsoft/vcpkg). This means that when new version of Catch is released, it should be posted there as well. `updateVcpkgPackage.py` can do a lot of necessary work for you, it creates a branch and commits necessary changes. You should review these changes, push and open a PR against vcpkg's upstream. Note that the script assumes you have your fork of vcpkg checked out in a directory next to the directory where you have checked out Catch, like so: ``` diff --git a/include/internal/catch_capture_matchers.cpp b/include/internal/catch_capture_matchers.cpp index 7ef1597d..a67cc797 100644 --- a/include/internal/catch_capture_matchers.cpp +++ b/include/internal/catch_capture_matchers.cpp @@ -13,7 +13,7 @@ namespace Catch { using StringMatcher = Matchers::Impl::MatcherBase