diff options
| author | Boris Kolpackov <boris@codesynthesis.com> | 2021-10-26 03:47:06 +0200 |
|---|---|---|
| committer | Boris Kolpackov <boris@codesynthesis.com> | 2021-10-26 03:47:06 +0200 |
| commit | 1956dce01ba9a71d70cd47ac4a9f706df0aa297e (patch) | |
| tree | 66adf2034c73ef59aca2e61b1066c63cdec7cbb2 | |
| parent | c5e8a623d5d69517d7968bf8012d066f83f85e5e (diff) | |
Minor documentation tweak
| -rw-r--r-- | doc/manual.cli | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/manual.cli b/doc/manual.cli index 9d79259..55a6d4c 100644 --- a/doc/manual.cli +++ b/doc/manual.cli @@ -5683,12 +5683,12 @@ does not break or produce incorrect results if the environment changes. Instead, changes to the environment are detected and affected targets are automatically rebuilt. -The two use-cases where hermetic configurations are really useful are when we -need to save an environment which is not generally available (for example, an -environment of a Visual Studio development command prompt) or when our build -results need to exactly match the specific configuration (for example, because -parts of the overall result have already been built and installed, as is the -case with build system modules).| +The two use-cases where hermetic configurations are especially useful are when +we need to save an environment which is not generally available (for example, +an environment of a Visual Studio development command prompt) or when our +build results need to exactly match the specific configuration (for example, +because parts of the overall result have already been built and installed, as +is the case with build system modules).| If we now examine \c{config.build}, we will see something along these lines: |