[Emacs-diffs] fix/bug-31311-pcase-doc 658699c 1/8: do ‘s/cl-case/case/g’

[Thien-Thi Nguyen]

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

    do ‘s/cl-case/case/g’
    
    however, keep the Issue comment (for now)
---
 doc/lispref/control.texi | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/doc/lispref/control.texi b/doc/lispref/control.texi
index 018df24..75b5103 100644
--- a/doc/lispref/control.texi
+++ b/doc/lispref/control.texi
@@ -302,7 +302,6 @@ For example:
 
 @c Issue: I use ‘case’ w/ the thought that it being an alias
 @c        to ‘cl-case’ is an ``implementation detail''.
address@hidden        (However, below i use ‘cl-case’ explicitly.  Hmmm.)
 @c        Is this okay?
 This subsection describes the @code{pcase} macro,
 a hybrid of @code{cond} and @code{case}
@@ -474,10 +473,10 @@ If all sub-patterns match, @code{and} matches.
 @end table
 
 @anchor{pcase-example-0}
address@hidden Example: Advantage Over @code{cl-case}
address@hidden Example: Advantage Over @code{case}
 
 Here's an example that highlights some advantages @code{pcase}
-has over @code{cl-case}
+has over @code{case}
 (@pxref{Conditionals,,,cl,Common Lisp Extensions}).
 
 @example
@@ -495,9 +494,9 @@ has over @code{cl-case}
 @end example
 
 @noindent
-With @code{cl-case}, you would need to explicitly declare a local
+With @code{case}, you would need to explicitly declare a local
 variable @code{code} to hold the return value of @code{get-return-code}.
-Also @code{cl-case} is difficult to use with strings because it
+Also @code{case} is difficult to use with strings because it
 uses @code{eql} for comparison.
 
 @anchor{pcase-example-1}