Improve hyperlinks (r1737462 in trunk)

<section id="usage"><title>Usage</title>

<p>Macros are defined using <directive

<p>Macros are defined using <directive module="mod_macro"

type="section">Macro</directive> blocks, which contain the portion of

your configuration that needs to be repeated, complete with variables

for those parts that will need to be substituted.</p>

<p>For example,  you might use a macro to define a <directive

<p>For example, you might use a macro to define a <directive module="core"

type="section">VirtualHost</directive> block, in order to define

multiple similar virtual hosts:</p>

UndefMacro VHost

</highlight>

<p>At server startup time, each of these <directive>Use</directive>

<p>At server startup time, each of these <directive module="mod_macro">Use</directive>

invocations would be expanded into a full virtualhost, as

described by the <directive>Macro</directive> definition.</p>

described by the <directive module="mod_macro" type="section">Macro</directive>

definition.</p>

<p>The <directive>UndefMacro</directive> directive is used so that later

macros using the same variable names don't result in conflicting

definitions.</p>

<p>The <directive module="mod_macro">UndefMacro</directive> directive is

used so that later macros using the same variable names don't result in

conflicting definitions.</p>

<p>A more elaborate version of this example may be seen below in the

Examples section.</p>

</contextlist>

<usage>

    <p>The <directive>Macro</directive> directive controls the definition of

    a macro within the server runtime configuration files.

    <p>The <directive type="section">Macro</directive> directive controls the

    definition of a macro within the server runtime configuration files.

    The first argument is the name of the macro.

    Other arguments are parameters to the macro. It is good practice to prefix

    parameter names with any of '<code>$%@</code>', and not macro names