[Emacs-diffs] fix/bug-31311-pcase-doc dc4b413 09/18: do ‘s/predfun/function/g’

[Thien-Thi Nguyen]

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

    do ‘s/predfun/function/g’
---
 doc/lispref/control.texi | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/lispref/control.texi b/doc/lispref/control.texi
index 5e7debc..0725097 100644
--- a/doc/lispref/control.texi
+++ b/doc/lispref/control.texi
@@ -364,10 +364,10 @@ Two symbols to avoid are @code{t}, which behaves like 
@code{_}
 (above) and is deprecated, and @code{nil}, which signals error.
 It makes no sense to bind these (@pxref{Constant Variables}).
 
address@hidden (pred @var{predfun})
-Matches if the predicate @var{predfun} returns address@hidden
address@hidden (pred @var{function})
+Matches if the predicate @var{function} returns address@hidden
 when called on @var{expval}.
address@hidden can have one of the possible forms:
address@hidden can have one of the possible forms:
 
 @table @asis
 @item function name (a symbol)
@@ -395,7 +395,7 @@ the actual function call becomes: @address@hidden(= 42 
@var{expval})}}.
 Matches if @var{function} called on @var{expval} returns a
 value that matches @var{pattern}.
 @var{function} can take one of the
-forms described for @var{predfun}, above.
+forms described for @var{function}, above.
 This is like @code{pred},
 except that it tests the result against @var{pattern},
 rather than against a boolean truth value.