[install-guide/F21-rewrite] Look at the mirroring wiki page if you want a local repo.

[Pete Travis]

commit 9e7723ee72536ec19b3b0a2107016fd85afef97a
Author: Pete Travis <immanetize at fedoraproject.org>
Date:   Sun Sep 7 12:20:55 2014 -0600

    Look at the mirroring wiki page if you want a local repo.
    
    Bonus changes include chapter wide markup repair, and minor tab
    alignment for the cobbler section.

 en-US/Network_based_Installations.xml |   45 +++++++++++++++++---------------
 1 files changed, 24 insertions(+), 21 deletions(-)
---
diff --git a/en-US/Network_based_Installations.xml b/en-US/Network_based_Installations.xml
index 21df376..e6a2092 100644
--- a/en-US/Network_based_Installations.xml
+++ b/en-US/Network_based_Installations.xml
@@ -21,7 +21,8 @@
         </para>
       </warning>
       -->
-    <section id="pxe-overview">
+      <section id="pxe-overview">
+        <title>PXE Installation Overview</title>
       <para>
         Pre-Execution Environment, or PXE, is a techonology that allows computers to boot directly from resources provided over the network.  Installing Fedora over the network means you don't have to create media, and you can install to multiple computers or virtual machine simultaneously.  The process involves a number of components and features working together to provide the resources required.
       </para>
@@ -50,7 +51,7 @@
         </para>
       </formalpara>
       <formalpara>
-        <title>Kernel & Initramfs</title>
+        <title>Kernel and Initramfs</title>
         <para>
           The kernel is the core of any Linux operating system, and the initramfs provides the kernel with required tools and resources.  These files are also provided by tftp.
         </para>
@@ -60,9 +61,9 @@
         <para>
           A Fedora repository must be available for the installation.  The example in this section uses the public Fedora mirrors as the repository source, but you can also use a repo on the local network provided by NFS, FTP, or HTTP.
         </para>
-        <remark>Dump a link in here to the inst.repo option.  Update the inst.repo option with examples if needed. --Pete</remark>
+     </formalpara>
+         <remark>Dump a link in here to the inst.repo option.  Update the inst.repo option with examples if needed. --Pete</remark>
         <remark>A link to mirrormanager and some instructions to other guides too.  All the elaboration on installation methods might be going to far, but we can ref. --Pete</remark>
-      </formalpara>
     </section>
     <section id="pxe-dhcpd">
       <title>DHCP Server Configuration</title>
@@ -130,6 +131,7 @@
           </procedure>
         </section>
         <section id="pxe-tftpd">
+          <title>Installing the tftp server</title>
           <procedure>
             <title>Installing the tftp server</title>
             <step>
@@ -301,22 +303,23 @@ label local
               </step>
             </procedure>
           </section>
-    <section id="sect-install-server-cobbler">
-      <para>
-        For more complex environments, &PRODUCT; offers the <package>cobbler</package> installation server.   Tasks like managing kickstart configurtations, coordinating repositories, maintaining dns records, dhcp servers, and even puppet manifests are effectively automated by <package>cobbler</package>.
-      </para>
-      <para>
-        While levaraging all of the features provided by cobbler can be relatively simple, the full functionality of this powerful tool is too broad to be documented in this guide.  The cobbler community provides excellent documentation at <ulink url="http://www.cobblerd.org/manuals/2.6.0/" /> to accompany the packages in the Fedora repository.
-       </para>
-    
-    <section id="sect-booting-pxe-installation">
-        <title>Booting the Network Installation</title>
-        <para>
-            After the PXE server has been configured and the installation tree or ISO image made available, you are ready to start the network installation. You must make sure that the system you are installing &PRODUCT; on is configured to boot from the network. The exact way to ensure varies depending on the hardware you are using.
-        </para>
-        <para>
-            For more specific instructions about booting your system, see <xref linkend="sect-booting-network" />.
-        </para>
-    </section>
+          <section id="pxe-repositories">
+            <title>Providing repositories</title>
+            <para>
+              The examples in this section use the public Fedora mirrors as the package source.  For faster installations, installing to many systems, or more isolated environments, you may wish to maintain a local repository.
+            </para>
+            <para>
+              Fedora Infrastructure maintains instructions for a configuring a local mirror at <ulink url="https://fedoraproject.org/wiki/Infrastructure/Mirroring" />.  The preferred method for providing repositories is via HTTP, and you can refer to the Fedora <citetitle>System Adminsitrators Guide</citetitle> for Fedora &PRODVER; to configure <systemitem class="daemon">httpd</systemitem>.
+            </para>
+          </section>
 
+          <section id="sect-install-server-cobbler">
+            <title>Advanced network installations with Cobbler</title>
+            <para>
+              For more complex environments, &PRODUCT; offers the <package>cobbler</package> installation server.   Tasks like managing kickstart configurtations, coordinating repositories, maintaining dns records, dhcp servers, and even puppet manifests are effectively automated by <package>cobbler</package>.
+            </para>
+            <para>
+              While levaraging all of the features provided by cobbler can be relatively simple, the full functionality of this powerful tool is too broad to be documented in this guide.  The cobbler community provides excellent documentation at <ulink url="http://www.cobblerd.org/manuals/2.6.0/" /> to accompany the packages in the Fedora repository.
+            </para>
+          </section>
 </chapter>