Provide an example in the introduction in order to motivate the lengthy

setup process.

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

diff --git a/docs/manual/howto/ssi.xml b/docs/manual/howto/ssi.xml
index 965c6384763bf3ae0219934642cd732deee16008..ea616fcd10fd8ccf5985bb9424123bcd59cb4b3a 100644 (file)
--- a/docs/manual/howto/ssi.xml
+++ b/docs/manual/howto/ssi.xml
@@ -66,14 +66,26 @@ existing HTML documents.</p>
     an existing HTML page, without having to serve the entire page
     via a CGI program, or other dynamic technology.</p>
 
+    <p>For example, you might place a directive into an existing HTML
+    page, such as:</p>
+
+    <example>
+    <!--#echo var="DATE_LOCAL" -->
+    </example>
+
+    <p>And, when the page is served, this fragment will be evaluated and replaced with its value:</p>
+
+    <example>
+    Tuesday, 15-Jan-2013 19:28:54 EST
+    </example>
+
     <p>The decision of when to use SSI, and when to have your page
     entirely generated by some program, is usually a matter of how
     much of the page is static, and how much needs to be
     recalculated every time the page is served. SSI is a great way
-    to add small pieces of information, such as the current time.
-    But if a majority of your page is being generated at the time
-    that it is served, you need to look for some other
-    solution.</p>
+    to add small pieces of information, such as the current time - shown
+    above.  But if a majority of your page is being generated at the time
+    that it is served, you need to look for some other solution.</p>
 </section>
 
 <section id="configuring">