Add five little words to clear up that we mean in a .htaccess context

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1308707 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/mod/mod_ssl.xml b/docs/manual/mod/mod_ssl.xml
index 05667db926416a0d2a1b63c0cec6db35947d5f30..217f1a08191b12e7807c6bd5a6c89fa902cb0fa8 100644 (file)
--- a/docs/manual/mod/mod_ssl.xml
+++ b/docs/manual/mod/mod_ssl.xml
@@ -1364,8 +1364,8 @@ the <a href="../expr.html#functions">ap_expr documentation</a>.</p>
 representation and then evaluated in a second step. Actually, in Global and
 Per-Server Class context <em>expression</em> is parsed at startup time and
 at runtime only the machine representation is executed. For Per-Directory
-context this is different: here <em>expression</em> has to be parsed and
-immediately executed for every request.</p>
+context, specifically in a .htaccess context, this is different: here <em>
+expression</em> has to be parsed and immediately executed for every request.</p>
 <example><title>Example</title>
 <pre>SSLRequire (    %{SSL_CIPHER} !~ m/^(EXP|NULL)-/                \
             and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd."        \