Corrections submitted by simon@

git-svn-id: https://svn.macports.org/repository/macports/trunk/doc@29143 d073be05-634f-4543-b044-5fe20cf6d1d6

guide/new/xml/portfiledev.xml

@@ -66,8 +66,8 @@
     install</command> steps, which conform to phases configure, build, and
     destroot respectively. For applications that do not conform to this
     standard behavior, any installation phase may be augmented using <link
-    linkend="development.examples.pre-post">pre- and/or post- phases</link>,
-    or even <link linkend="development.examples.override">overridden</link> or
+    linkend="development.examples.augment">pre- and/or post- phases</link>, or
+    even <link linkend="development.examples.override">overridden</link> or
     <link linkend="development.examples.eliminate">eliminated</link>. See
     <link linkend="development.examples">Example Portfiles</link>
     below.</para>
@@ -685,7 +685,7 @@ variant debug   { configure.args-append --enable-debug }</programlisting>
       <para>TODO:</para>
     </section>
 
-    <section>
+    <section id="development.practices.use-variables">
       <title>Use Variables</title>
 
       <para>TODO: Set variables so changing paths may be done in one place;

guide/new/xml/portfileref.xml

@@ -16,7 +16,7 @@
     <command>configure</command>, <command>make</command>, and <command>make
     install</command> steps, but for applications that do not conform to this
     behavior, installation phases may be declared in a Portfile to <link
-    linkend="development.examples.pre-post">augment</link> or <link
+    linkend="development.examples.augment">augment</link> or <link
     linkend="development.examples.override">override</link> the default
     behavior as described in the <link linkend="development">Portfile
     Development</link> chapter.</para>