From: Stefan Fritsch Date: Mon, 29 Oct 2012 20:43:48 +0000 (+0000) Subject: Merge 1403492: X-Git-Tag: 2.4.4~460 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=978387ab67402a50a40d6e0c4d3da8b9aac1b61c;p=apache Merge 1403492: fix cut'n'paste error git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1403493 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/expr.html.en b/docs/manual/expr.html.en index bef7c21188..4511a0d84e 100644 --- a/docs/manual/expr.html.en +++ b/docs/manual/expr.html.en @@ -55,7 +55,7 @@ In most cases, expressions are used to express boolean values. For these, the starting boint in the BNF is expr. However, a few directives like LogMessage accept expressions - that evaluate to a string value. For those, the starting boint in the BNF is code. + that evaluate to a string value. For those, the starting boint in the BNF is string.

diff --git a/docs/manual/expr.xml b/docs/manual/expr.xml
index 7b1f6d6626..6980419889 100644
--- a/docs/manual/expr.xml
+++ b/docs/manual/expr.xml
@@ -58,7 +58,7 @@
       In most cases, expressions are used to express boolean values.
       For these, the starting boint in the BNF is expr. However, a few directives
       like LogMessage accept expressions
-      that evaluate to a string value. For those, the starting boint in the BNF is code.
+      that evaluate to a string value. For those, the starting boint in the BNF is string.