[Emacs-diffs] fix/bug-31311-pcase-doc ca86dce 15/16: in U-pattern table, do ‘s/upattern/pattern/g’

[Thien-Thi Nguyen]

branch: fix/bug-31311-pcase-doc
commit ca86dce4a4c269992d5f343ce42f53714ecfd3eb
Author: Thien-Thi Nguyen <address@hidden>
Commit: Thien-Thi Nguyen <address@hidden>

    in U-pattern table, do ‘s/upattern/pattern/g’
    
    (keep ‘upattern’ in the Q-pattern table for now)
---
 doc/lispref/control.texi | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/doc/lispref/control.texi b/doc/lispref/control.texi
index 739a675..f690a3a 100644
--- a/doc/lispref/control.texi
+++ b/doc/lispref/control.texi
@@ -440,15 +440,15 @@ In this example, the function is @code{=}, @var{n} is 
one, and
 the actual function call becomes: @address@hidden(= 42 @var{expval})}}.
 @end table
 
address@hidden (app @var{function} @var{upattern})
address@hidden (app @var{function} @var{pattern})
 Matches if @var{function} called on @var{expval} returns a
-value that matches @var{upattern}.
+value that matches @var{pattern}.
 @var{function} can take one of the
 forms described for @var{predfun}, above.
 This is like @code{pred},
-except that it tests the result against @var{upattern},
+except that it tests the result against @var{pattern},
 rather than against a boolean truth value.
address@hidden Issue: Same as below (side-effecting FUNCTION or UPATTERN).
address@hidden Issue: Same as below (side-effecting FUNCTION or PATTERN).
 
 @item (guard @var{boolean-expression})
 Matches if @var{boolean-expression} evaluates to address@hidden  This
@@ -481,22 +481,22 @@ which matches any number smaller than 10 and let-binds 
the variable
 @c          and is considered {undefined, wontfix, futurefix}.
 @c          Leave undocumented for now.
 
address@hidden (let @var{upattern} @var{expr})
address@hidden (let @var{pattern} @var{expr})
 Evaluates @var{expr} to get @var{exprval}
-and matches if @var{exprval} matches @var{upattern}.
+and matches if @var{exprval} matches @var{pattern}.
 (It is called @code{let} because
address@hidden can bind symbols to values using the @var{symbol}
address@hidden can bind symbols to values using the @var{symbol}
 U-pattern.  For example:
 @address@hidden((or `(key . ,val) (let val 5)) val)}}.)
 @c Issue: Same as above (side-effecting EXPRESSION).
 
address@hidden (or @var{upattern1} @address@hidden)
address@hidden (or @var{pattern1} @address@hidden)
 Matches if one the argument U-patterns matches.  As soon as the first
 matching U-pattern is found, the rest are not tested.  For this reason,
 if any of the U-patterns let-bind symbols to the matched value, they
 should all bind the same symbols.
 
address@hidden (and @var{upattern1} @address@hidden)
address@hidden (and @var{pattern1} @address@hidden)
 Matches if all the argument U-patterns match.
 @end table