Merge topic 'doc-help-spelling'

20d90a9482 Help: Some spelling corrections for commands.

Acked-by: Kitware Robot <[email protected]>
Merge-request: !1994

Help/command/FIND_XXX.txt

@@ -80,7 +80,7 @@ If ``NO_DEFAULT_PATH`` is not specified, the search process is as follows:
    current package being found.  Specifically look in the ``PackageName_ROOT``
    CMake and environment variables.  The package root variables are maintained
    as a stack so if called from nested find modules, root paths from the
-   parent's find module will be searchd after paths from the current module,
+   parent's find module will be searched after paths from the current module,
    i.e. ``CurrentPackage_ROOT``, ``ENV{CurrentPackage_ROOT}``,
    ``ParentPackage_ROOT``, ``ENV{ParentPacakge_ROOT}``, etc.
    This can be skipped if ``NO_PACKAGE_ROOT_PATH`` is passed.

Help/command/cmake_host_system_information.rst

@@ -27,13 +27,13 @@ Key                           Description
 ``IS_64BIT``                  One if processor is 64Bit
 ``HAS_FPU``                   One if processor has floating point unit
 ``HAS_MMX``                   One if processor supports MMX instructions
-``HAS_MMX_PLUS``              One if porcessor supports Ext. MMX instructions
-``HAS_SSE``                   One if porcessor supports SSE instructions
-``HAS_SSE2``                  One if porcessor supports SSE2 instructions
-``HAS_SSE_FP``                One if porcessor supports SSE FP instructions
-``HAS_SSE_MMX``               One if porcessor supports SSE MMX instructions
-``HAS_AMD_3DNOW``             One if porcessor supports 3DNow instructions
-``HAS_AMD_3DNOW_PLUS``        One if porcessor supports 3DNow+ instructions
+``HAS_MMX_PLUS``              One if processor supports Ext. MMX instructions
+``HAS_SSE``                   One if processor supports SSE instructions
+``HAS_SSE2``                  One if processor supports SSE2 instructions
+``HAS_SSE_FP``                One if processor supports SSE FP instructions
+``HAS_SSE_MMX``               One if processor supports SSE MMX instructions
+``HAS_AMD_3DNOW``             One if processor supports 3DNow instructions
+``HAS_AMD_3DNOW_PLUS``        One if processor supports 3DNow+ instructions
 ``HAS_IA64``                  One if IA64 processor emulating x86
 ``HAS_SERIAL_NUMBER``         One if processor has serial number
 ``PROCESSOR_SERIAL_NUMBER``   Processor serial number

Help/command/ctest_submit.rst

@@ -68,7 +68,7 @@ Submit to CDash Upload API
                [QUIET])
 
 This second signature is used to upload files to CDash via the CDash
-file upload API. The api first sends a request to upload to CDash along
+file upload API. The API first sends a request to upload to CDash along
 with a content hash of the file. If CDash does not already have the file,
 then it is uploaded. Along with the file, a CDash type string is specified
 to tell CDash which handler to use to process the data.

Help/command/get_filename_component.rst

@@ -45,7 +45,7 @@ to the given base directory ``<BASE_DIR>``.  If no base directory is
 provided, the default base directory will be
 :variable:`CMAKE_CURRENT_SOURCE_DIR`.
 
-Paths are returned with forward slashes and have no trailing slahes.  If the
+Paths are returned with forward slashes and have no trailing slashes.  If the
 optional ``CACHE`` argument is specified, the result variable is added to the
 cache.
 

Help/command/get_source_file_property.rst

@@ -11,7 +11,7 @@ Get a property from a source file.  The value of the property is
 stored in the variable ``VAR``.  If the source property is not found, the
 behavior depends on whether it has been defined to be an ``INHERITED`` property
 or not (see :command:`define_property`).  Non-inherited properties will set
-``VAR`` to "NOTFOUND", whereas inheritied properties will search the relevent
+``VAR`` to "NOTFOUND", whereas inherited properties will search the relevant
 parent scope as described for the :command:`define_property` command and
 if still unable to find the property, ``VAR`` will be set to an empty string.
 

Help/command/get_target_property.rst

@@ -11,8 +11,8 @@ Get a property from a target.  The value of the property is stored in
 the variable ``VAR``.  If the target property is not found, the behavior
 depends on whether it has been defined to be an ``INHERITED`` property
 or not (see :command:`define_property`).  Non-inherited properties will
-set ``VAR`` to "NOTFOUND", whereas inheritied properties will search the
-relevent parent scope as described for the :command:`define_property`
+set ``VAR`` to "NOTFOUND", whereas inherited properties will search the
+relevant parent scope as described for the :command:`define_property`
 command and if still unable to find the property, ``VAR`` will be set to
 an empty string.
 

Help/command/get_test_property.rst

@@ -11,8 +11,8 @@ Get a property from the test.  The value of the property is stored in
 the variable ``VAR``.  If the test property is not found, the behavior
 depends on whether it has been defined to be an ``INHERITED`` property
 or not (see :command:`define_property`).  Non-inherited properties will
-set ``VAR`` to "NOTFOUND", whereas inheritied properties will search the
-relevent parent scope as described for the :command:`define_property`
+set ``VAR`` to "NOTFOUND", whereas inherited properties will search the
+relevant parent scope as described for the :command:`define_property`
 command and if still unable to find the property, ``VAR`` will be set to
 an empty string.
 

Help/command/list.rst

@@ -213,7 +213,7 @@ The ``<SELECTOR>`` may be one of:
 
   list(TRANSFORM <list> <ACTION> AT <index> [<index> ...] ...)
 
-``FOR``: Specify a range with, optionaly, an increment used to iterate over
+``FOR``: Specify a range with, optionally, an increment used to iterate over
 the range. ::
 
   list(TRANSFORM <list> <ACTION> FOR <start> <stop> [<step>] ...)

Help/command/string.rst

@@ -386,7 +386,7 @@ UUID
   string(UUID <output variable> NAMESPACE <namespace> NAME <name>
          TYPE <MD5|SHA1> [UPPER])
 
-Create a univerally unique identifier (aka GUID) as per RFC4122
+Create a universally unique identifier (aka GUID) as per RFC4122
 based on the hash of the combined values of ``<namespace>``
 (which itself has to be a valid UUID) and ``<name>``.
 The hash algorithm can be either ``MD5`` (Version 3 UUID) or