[build-path-prefix-map-spec] 46/50: spec-main.rst: copyediting. No functional change.

[Ximin Luo]

This is an automated email from the git hooks/post-receive script.

infinity0 pushed a commit to branch master
in repository build-path-prefix-map-spec.

commit 8428b3cbede2694e6098ef5c59bd33aeb0c4a1c1
Author: Daniel Shahaf <d.s at daniel.shahaf.name>
Date:   Sun Mar 5 13:34:00 2017 +0000

    spec-main.rst: copyediting.  No functional change.
---
 spec-main.rst | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/spec-main.rst b/spec-main.rst
index 7c69b3d..eeed84f 100644
--- a/spec-main.rst
+++ b/spec-main.rst
@@ -65,7 +65,7 @@ The encoding is as follows:
   3. ``:`` → ``%.``
 
   When decoding, ``%`` characters at the end of a string are a parse error, as
-  are ``%[X]`` substrings where ``[X]`` is any character not in ``#+.``.
+  are ``%X`` substrings where ``X`` is any character not in ``#+.``.
 
   This encoding allows paths containing ``%``, ``=``, ``:`` to be mapped; since
   users may want to run their builds under such paths. However as a producer,
@@ -83,7 +83,7 @@ The encoding is as follows:
 
   A. Decoding:
 
-     1. check elem does not match the regex ``/%[^#+.]|%$/g``, then
+     1. check that ``elem`` does not match the regex ``/%[^#+.]|%$/g``, then
      2. ``elem.replace("%.", ":").replace("%+", "=").replace("%#", "%")``
 
   B. Encoding:
@@ -110,7 +110,7 @@ their new mappings onto the right of any existing value.
 
 Producers who build *general software* that uses this envvar, MUST NOT expect
 any special contracts on the output emitted by *general consumers* based on
-this variable - only that their output be reproducible when the build path
+this variable ― only that their output be reproducible when the build path
 changes and the value of this envvar is changed to match the new paths.
 
 On the other hand, if you know you will only support a limited set of
@@ -170,7 +170,7 @@ Notes and links
     ``envvar += ":" + encoded_pair`` which would be valid even if envvar is
     originally empty.
 
-.. [4] This is to "fail early" in the cases that a naive producer does not
+.. [4] This is to "fail early" in case a naive producer does not
     encode characters like ``=`` but the build path or target path does
     actually contain them.
 

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/reproducible/build-path-prefix-map-spec.git