[Guile-commits] 03/07: Mention (ice-9 peg) module path.

[Ludovic Courtès]

civodul pushed a commit to branch stable-2.2
in repository guile.

commit 1be85ca008fd9f79a957ab033582f9b8b9ff587b
Author: Arun Isaac <address@hidden>
Date:   Thu Nov 16 18:48:37 2017 +0530

    Mention (ice-9 peg) module path.
    
    * doc/ref/api-peg.texi (PEG Parsing): Mention (ice-9 peg) module path.
    
    Signed-off-by: Ludovic Courtès <address@hidden>
---
 doc/ref/api-peg.texi | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/doc/ref/api-peg.texi b/doc/ref/api-peg.texi
index 0e16aab..cbe3edd 100644
--- a/doc/ref/api-peg.texi
+++ b/doc/ref/api-peg.texi
@@ -17,11 +17,12 @@ Wikipedia has a clear and concise introduction to PEGs if 
you want to
 familiarize yourself with the syntax:
 @url{http://en.wikipedia.org/wiki/Parsing_expression_grammar}.
 
-The module works by compiling PEGs down to lambda expressions.  These
-can either be stored in variables at compile-time by the define macros
-(@code{define-peg-pattern} and @code{define-peg-string-patterns}) or calculated
-explicitly at runtime with the compile functions
-(@code{compile-peg-pattern} and @code{peg-string-compile}).
+The @code{(ice-9 peg)} module works by compiling PEGs down to lambda
+expressions.  These can either be stored in variables at compile-time by
+the define macros (@code{define-peg-pattern} and
address@hidden) or calculated explicitly at runtime
+with the compile functions (@code{compile-peg-pattern} and
address@hidden).
 
 They can then be used for either parsing (@code{match-pattern}) or searching
 (@code{search-for-pattern}).  For convenience, @code{search-for-pattern}