docs: Replace <strong>Note:</strong> with <note> per style guide

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

Author: rbowen

docs/manual/developer/lua.xml

@@ -97,11 +97,10 @@ pool, and if it has high usage, use the <code>thread</code> setting. As your ser
 load increases, so will the number of states being actively used, and having your scope
 set to <code>once/request/conn</code> will stop being beneficial to your memory footprint.
 </p>
-<p>
-<strong>Note:</strong> The <code>min</code> and <code>max</code> settings for the
+<note>The <code>min</code> and <code>max</code> settings for the
 <code>server</code> scope denotes the minimum and maximum states to keep in a pool per
 server <em>process</em>, so keep this below your <code>ThreadsPerChild</code> limit.
-</p>
+</note>
 </section>
 
 <section><title>Using code caching</title>

docs/manual/mod/mod_dir.xml

@@ -102,10 +102,10 @@ a directory</description>
     literally if it has any arguments before or after it, even if they are "disabled"
     as well.</p>
 
-    <p><strong>Note:</strong> Multiple <directive>DirectoryIndex</directive>
+    <note>Multiple <directive>DirectoryIndex</directive>
     directives within the <a href="../sections.html"><em>same context</em></a> will add
     to the list of resources to look for rather than replace:
-    </p>
+    </note>
     <highlight language="config">
 # Example A: Set index.html as an index page, then add index.php to that list as well.
 &lt;Directory "/foo"&gt;

docs/manual/mod/mod_proxy.xml

@@ -943,10 +943,10 @@ expressions</description>
     the socket is local, the hostname used (in this case <code>localhost</code>)
     is moot, but it is passed as the Host: header value of the request.</p>
 
-    <note><strong>Note:</strong> The path associated with the <code>unix:</code>
+    <note>The path associated with the <code>unix:</code>
     URL is <directive>DefaultRuntimeDir</directive> aware.</note>
 
-    <note><strong>Note:</strong> <directive>RewriteRule</directive> requires
+    <note><directive>RewriteRule</directive> requires
     the <code>[P,NE]</code> option to prevent the <code>'|'</code> character
     from being escaped.</note>
 
@@ -1594,7 +1594,7 @@ when the <var>url</var> parameter contains backreference(s) (see note below).
        matches, the server will substitute any parenthesized matches into the given
        string and use it as a new <var>url</var>.</p>
 
-    <note><strong>Note: </strong>This directive cannot be used within a
+    <note>This directive cannot be used within a
     <code>&lt;Directory&gt;</code> context.</note>
 
     <note type="warning"><title>Worker matching with backreferences</title>

docs/manual/mod/mod_proxy_html.xml

@@ -106,8 +106,9 @@ still be configured using regular filter directives, this will not support
 i18n at all.  Instead, a new directive <directive>ProxyHTMLEnable</directive>
 has been introduced to configure both mod_proxy_html's filter and mod_xml2enc.
 It is recommended that you always use ProxyHTMLEnable even where i18n
-support is not required. <strong>Note that this is a change from earlier
-versions where filter directives were used to activate mod_proxy_html.</strong></p>
+support is not required.</p>
+<note>This is a change from earlier
+versions where filter directives were used to activate mod_proxy_html.</note>
 
 </section>
 

docs/manual/mod/mod_request.xml

@@ -65,13 +65,13 @@ mod_include.</description>
     into the URL space from another server using
     <module>mod_proxy</module>.</p>
 
-    <p><strong>Note:</strong> Each request set aside has to be set
+    <note>Each request set aside has to be set
     aside in temporary RAM until the request is complete. As a result,
     care should be taken to ensure sufficient RAM is available on the
     server to support the intended load. Use of this directive
     should be limited to where needed on targeted parts of your
     URL space, and with the lowest possible value that is still big
-    enough to hold a request body.</p>
+    enough to hold a request body.</note>
 
     <p>If the request size sent by the client exceeds the maximum
     size allocated by this directive, the server will return