aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLang Hames <lhames@gmail.com>2017-08-17 18:00:28 +0000
committerLang Hames <lhames@gmail.com>2017-08-17 18:00:28 +0000
commitd17c970ac74f24d677b74fb36f5b908f6df224b5 (patch)
tree47eba8497a65451a627d914a6d5a7f4e2a0259d8
parent84dc1f35b19d369580f571830fe0686e905fb171 (diff)
[docs] Fix typo and tweak wording of special variable handling in CMake primer.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@311112 91177308-0d34-0410-b5e6-96231b3b80d8
-rw-r--r--docs/CMakePrimer.rst9
1 files changed, 4 insertions, 5 deletions
diff --git a/docs/CMakePrimer.rst b/docs/CMakePrimer.rst
index c29d627ee62..14e8a273690 100644
--- a/docs/CMakePrimer.rst
+++ b/docs/CMakePrimer.rst
@@ -167,10 +167,9 @@ Other Types
Variables that are cached or specified on the command line can have types
associated with them. The variable's type is used by CMake's UI tool to display
-the right input field. The variable's type generally doesn't impact evaluation.
-One of the few examples is PATH variables, which CMake does have some special
-handling for. You can read more about the special handling in `CMake's set
-documentation
+the right input field. A variable's type generally doesn't impact evaluation,
+however CMake does have special handling for some variables such as PATH.
+You can read more about the special handling in `CMake's set documentation
<https://cmake.org/cmake/help/v3.5/command/set.html#set-cache-entry>`_.
Scope
@@ -203,7 +202,7 @@ Control Flow
============
CMake features the same basic control flow constructs you would expect in any
-scripting language, but there are a few quarks because, as with everything in
+scripting language, but there are a few quirks because, as with everything in
CMake, control flow constructs are commands.
If, ElseIf, Else