summaryrefslogtreecommitdiff
path: root/Modules/CMakePackageConfigHelpers.cmake
diff options
context:
space:
mode:
authorJosef Angstenberger <code@jtxa.de>2021-05-06 22:40:26 +0200
committerJosef Angstenberger <code@jtxa.de>2021-05-07 17:00:16 +0200
commit15cc39ed7f90331401f53530e4b2d03f8573f0d1 (patch)
tree5068214d0283e4981878c0c7b5b2f57047ca3423 /Modules/CMakePackageConfigHelpers.cmake
parentf015c36c5a051d73434d56ba54c12001590756a2 (diff)
downloadcmake-15cc39ed7f90331401f53530e4b2d03f8573f0d1.tar.gz
Modules: Fix typos and spelling in documentation
Diffstat (limited to 'Modules/CMakePackageConfigHelpers.cmake')
-rw-r--r--Modules/CMakePackageConfigHelpers.cmake4
1 files changed, 2 insertions, 2 deletions
diff --git a/Modules/CMakePackageConfigHelpers.cmake b/Modules/CMakePackageConfigHelpers.cmake
index ad719ef5af..5813956ee4 100644
--- a/Modules/CMakePackageConfigHelpers.cmake
+++ b/Modules/CMakePackageConfigHelpers.cmake
@@ -143,12 +143,12 @@ The ``COMPATIBILITY`` mode ``AnyNewerVersion`` means that the installed
package version will be considered compatible if it is newer or exactly the
same as the requested version. This mode should be used for packages which
are fully backward compatible, also across major versions.
-If ``SameMajorVersion`` is used instead, then the behaviour differs from
+If ``SameMajorVersion`` is used instead, then the behavior differs from
``AnyNewerVersion`` in that the major version number must be the same as
requested, e.g. version 2.0 will not be considered compatible if 1.0 is
requested. This mode should be used for packages which guarantee backward
compatibility within the same major version.
-If ``SameMinorVersion`` is used, the behaviour is the same as
+If ``SameMinorVersion`` is used, the behavior is the same as
``SameMajorVersion``, but both major and minor version must be the same as
requested, e.g version 0.2 will not be compatible if 0.1 is requested.
If ``ExactVersion`` is used, then the package is only considered compatible if