08/09: doc: cookbook: Mention "#true" and "#false".

[guix-commits]

civodul pushed a commit to branch master
in repository guix.

commit cd958802f20e07967d2245039ebadd5911c47333
Author: Ludovic Courtès <ludo@gnu.org>
AuthorDate: Wed Oct 14 11:28:30 2020 +0200

    doc: cookbook: Mention "#true" and "#false".
    
    * doc/guix-cookbook.texi (A Scheme Crash Course): Mention "#true" and
    "#false".
    (Extended example): Likewise.
---
 doc/guix-cookbook.texi | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/doc/guix-cookbook.texi b/doc/guix-cookbook.texi
index a783c0a..affb68c 100644
--- a/doc/guix-cookbook.texi
+++ b/doc/guix-cookbook.texi
@@ -128,8 +128,9 @@ REPL.
 @item
 Scheme syntax boils down to a tree of expressions (or @emph{s-expression} in
 Lisp lingo).  An expression can be a literal such as numbers and strings, or a
-compound which is a parenthesized list of compounds and literals.  @code{#t}
-and @code{#f} stand for the Booleans ``true'' and ``false'', respectively.
+compound which is a parenthesized list of compounds and literals.  @code{#true}
+and @code{#false} (abbreviated @code{#t} and @code{#f}) stand for the
+Booleans ``true'' and ``false'', respectively.
 
 Examples of valid expressions:
 
@@ -1090,9 +1091,9 @@ this:
   #t)
 @end lisp
 
-The procedure must return @code{#t} on success.  It's brittle to rely on the 
return
+The procedure must return @code{#true} on success.  It's brittle to rely on 
the return
 value of the last expression used to tweak the phase because there is no
-guarantee it would be a @code{#t}.  Hence the trailing @code{#t} to ensure the 
right value
+guarantee it would be a @code{#true}.  Hence the trailing @code{#true} to 
ensure the right value
 is returned on success.
 
 @subsubsection Code staging