avoid literal : in index entries

[gnulib.git] / doc / regex.texi

diff --git a/doc/regex.texi b/doc/regex.texi
index 093f4cc..bf8049e 100644 (file)
--- a/doc/regex.texi
+++ b/doc/regex.texi
@@ -885,7 +885,7 @@ All other characters are ordinary.  For example, @samp{[.*]} matches
 Collating symbols can be represented inside lists.
 You form a @dfn{collating symbol} by
 putting a collating element between an @dfn{open-collating-symbol
-operator} and an @dfn{close-collating-symbol operator}.  @samp{[.}
+operator} and a @dfn{close-collating-symbol operator}.  @samp{[.}
 represents the open-collating-symbol operator and @samp{.]} represents
 the close-collating-symbol operator.  For example, if @samp{ll} is a
 collating element, then @samp{[[.ll.]]} would match @samp{ll}.
@@ -914,8 +914,8 @@ symbol.
 @subsection Character Class Operators (@code{[:} @dots{} @code{:]})
 
 @cindex character classes
-@cindex @samp{[:} in regex
-@cindex @samp{:]} in regex
+@cindex @samp{[colon} in regex
+@cindex @samp{colon]} in regex
 
 If the syntax bit @code{RE_CHAR_CLASSES} is set, then Regex recognizes
 character class expressions inside lists.  A @dfn{character class
@@ -1624,7 +1624,7 @@ compiled pattern.  @var{string} is the string you want to match; it can
 contain newline and null characters.  @var{size} is the length of that
 string.  @var{start} is the string index at which you want to
 begin matching; the first character of @var{string} is at index zero.
-@xref{Using Registers}, for a explanation of @var{regs}; you can safely
+@xref{Using Registers}, for an explanation of @var{regs}; you can safely
 pass zero.
 
 @code{re_match} matches the regular expression in @var{pattern_buffer}