[Emacs-diffs] fix/bug-31311-pcase-doc ef4a105 2/9: rewrite "The rest of this subsection..." para

[Thien-Thi Nguyen]

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

    rewrite "The rest of this subsection..." para
    
    - drop "another Lisp macro" (allusion to ‘pcase-defmacro’)
      omission from 2018-05-17, "add subsection ‘Extending @code{pcase}’"
    - add MAINTAINME comment
---
 doc/lispref/control.texi | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/doc/lispref/control.texi b/doc/lispref/control.texi
index 21e4eac..cd3c32c 100644
--- a/doc/lispref/control.texi
+++ b/doc/lispref/control.texi
@@ -297,6 +297,7 @@ For example:
 
 @node Pattern-Matching Conditional
 @subsection Pattern-Matching Conditional
address@hidden MAINTAINME: ``subsection'', ``subheading''
 @cindex pcase
 @cindex pattern matching
 
@@ -364,12 +365,11 @@ of the last of @var{body-forms} in the successful clause.
 Otherwise, @code{pcase} evaluates to @code{nil}.
 @end defmac
 
address@hidden Issue: For presentation, we ‘s/U-pattern/core pattern/g’.
address@hidden        ISTM (from a quick grep) ``core'' is not overused.
address@hidden        Is there a better term?
-The rest of this subsection describes the core @var{pattern}
-forms, and concludes with a another Lisp macro you can use to
-extend the core set.
+The rest of this subsection
+describes different forms of core patterns,
+presents some examples,
+and concludes with important caveats on using the
+let-binding facility provided by some pattern forms.
 A core pattern can have the following forms:
 
 @table @code