[install-guide] remove or replace references to Deployment Guide as needed

Pete Travis immanetize at fedoraproject.org
Sat Dec 21 05:20:45 UTC 2013


commit a63f640b43bd3ba89524d0c1e9c41d0677613448
Author: Pete Travis <immanetize at fedoraproject.org>
Date:   Fri Dec 20 22:20:24 2013 -0700

    remove or replace references to Deployment Guide as needed

 ...titions-section-2-itemizedlist-1-listitem-3.xml |    2 +-
 ...titions-section-2-itemizedlist-1-listitem-4.xml |    2 +-
 ...titions-section-2-itemizedlist-1-listitem-5.xml |    2 +-
 en-US/Create_LVM-common-para-2.xml                 |    2 +-
 en-US/Create_LVM-x86.xml                           |    2 +-
 en-US/Create_Software_RAID-common-para-1.xml       |    2 +-
 en-US/Kickstart2.xml                               |    2 +-
 en-US/Ksconfig.xml                                 |    4 ++--
 ...eps_Network_Install_section_2-common-para-8.xml |    2 +-
 en-US/X86_Bootloader.xml                           |    2 +-
 en-US/pxe-server-config-bios.xml                   |    2 +-
 en-US/pxe-server-config-efi.xml                    |    2 +-
 12 files changed, 13 insertions(+), 13 deletions(-)
---
diff --git a/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-3.xml b/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-3.xml
index 246b61a..fb3b8eb 100644
--- a/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-3.xml
+++ b/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-3.xml
@@ -5,7 +5,7 @@
 ]>
 <listitem>
 	<para>
-		<guilabel>logical volume (LVM)</guilabel> &mdash; Creating an LVM partition automatically generates an LVM logical volume. LVM can improve performance when using physical disks. To create a logical volume, refer to <xref linkend="Create_LVM-x86" />. For more information regarding LVM, refer to the <citetitle>Fedora Deployment Guide</citetitle>.
+		<guilabel>logical volume (LVM)</guilabel> &mdash; Creating an LVM partition automatically generates an LVM logical volume. LVM can improve performance when using physical disks. To create a logical volume, refer to <xref linkend="Create_LVM-x86" />. For more information regarding LVM, refer to the <citetitle>Fedora System Administrators Guide</citetitle>.
 	</para>
 </listitem>
 
diff --git a/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-4.xml b/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-4.xml
index 7f1d623..c5e3204 100644
--- a/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-4.xml
+++ b/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-4.xml
@@ -5,7 +5,7 @@
 ]>
 <listitem>
 	<para>
-	      <guilabel>software RAID</guilabel> &mdash; Creating two or more software RAID partitions allows you to create a RAID device. One RAID partition is assigned to each disk on the system. To create a RAID device, refer to <xref linkend="Create_Software_RAID-x86" />. For more information regarding RAID, refer to the chapter <citetitle>RAID (Redundant Array of Independent Disks)</citetitle> in the <citetitle>Fedora Deployment Guide</citetitle>.
+	      <guilabel>software RAID</guilabel> &mdash; Creating two or more software RAID partitions allows you to create a RAID device. One RAID partition is assigned to each disk on the system. To create a RAID device, refer to <xref linkend="Create_Software_RAID-x86" />. For more information regarding RAID, refer to the chapter <citetitle>RAID (Redundant Array of Independent Disks)</citetitle> in the <citetitle>Fedora System Administrators Guide</citetitle>.
 	</para>
 </listitem>
 
diff --git a/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-5.xml b/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-5.xml
index 5d0bc12..bb00c30 100644
--- a/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-5.xml
+++ b/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-5.xml
@@ -5,7 +5,7 @@
 ]>
 <listitem>
 	<para>
-		<guilabel>swap</guilabel> &mdash; Swap partitions are used to support virtual memory. In other words, data is written to a swap partition when there is not enough RAM to store the data your system is processing. Refer to the <citetitle>Fedora Deployment Guide</citetitle> for additional information.
+		<guilabel>swap</guilabel> &mdash; Swap partitions are used to support virtual memory. In other words, data is written to a swap partition when there is not enough RAM to store the data your system is processing. Refer to the <citetitle>Fedora System Administrators Guide</citetitle> for additional information.
 	</para>
 </listitem>
 
diff --git a/en-US/Create_LVM-common-para-2.xml b/en-US/Create_LVM-common-para-2.xml
index 027b5ab..8b902ae 100644
--- a/en-US/Create_LVM-common-para-2.xml
+++ b/en-US/Create_LVM-common-para-2.xml
@@ -4,6 +4,6 @@
 %BOOK_ENTITIES;
 ]>
 <para>
-	To read more about LVM, refer to the <citetitle>Fedora Deployment Guide</citetitle>. Note, LVM is only available in the graphical installation program.
+	To read more about LVM, refer to the <citetitle>Fedora System Administrators Guide</citetitle>. Note, LVM is only available in the graphical installation program.
 </para>
 
diff --git a/en-US/Create_LVM-x86.xml b/en-US/Create_LVM-x86.xml
index 64fa8af..08272ed 100644
--- a/en-US/Create_LVM-x86.xml
+++ b/en-US/Create_LVM-x86.xml
@@ -8,7 +8,7 @@
 	 <!--  Create LVM Logical Volume  --> <xi:include href="Create_LVM-common-important-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
 	 <!--  Important — LVM Unavailable in Text Installs  --> <xi:include href="Create_LVM-common-para-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
 	 <!--  Logical Volume Management (LVM) presents a simple logical view of underlying physical storage space  --> <xi:include href="Create_LVM-common-para-2.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-	 <!--  To read more about LVM, refer to the Fedora Deployment Guide  --> 
+	 <!--  To read more about LVM, refer to the Fedora System Administrators Guide  --> 
 	 
 	<figure float="0">
 		<title>Configure a logical volume</title>
diff --git a/en-US/Create_Software_RAID-common-para-1.xml b/en-US/Create_Software_RAID-common-para-1.xml
index ffb3c40..f596350 100644
--- a/en-US/Create_Software_RAID-common-para-1.xml
+++ b/en-US/Create_Software_RAID-common-para-1.xml
@@ -4,6 +4,6 @@
 %BOOK_ENTITIES;
 ]>
 <para>
-	<firstterm>Redundant arrays of independent disks</firstterm> (RAIDs) are constructed from multiple storage devices that are arranged to provide increased performance and — in some configurations — greater fault tolerance. Refer to the <citetitle>Fedora Deployment Guide</citetitle> for a description of different kinds of RAIDs.
+	<firstterm>Redundant arrays of independent disks</firstterm> (RAIDs) are constructed from multiple storage devices that are arranged to provide increased performance and — in some configurations — greater fault tolerance. 
 </para>
 
diff --git a/en-US/Kickstart2.xml b/en-US/Kickstart2.xml
index 581b4e1..11f72f6 100644
--- a/en-US/Kickstart2.xml
+++ b/en-US/Kickstart2.xml
@@ -2585,7 +2585,7 @@ If the <command>selinux</command> option is not present in the kickstart file, S
 						
 					</itemizedlist>
 					<para>
-						For more information regarding SELinux for Fedora, refer to the <citetitle>Fedora Deployment Guide</citetitle>.
+						For more information regarding SELinux for Fedora, refer to the <citetitle>Fedora Security Guide</citetitle>.
 					</para>
 				</listitem>
 			</varlistentry>
diff --git a/en-US/Ksconfig.xml b/en-US/Ksconfig.xml
index 2b7da6c..52c0509 100644
--- a/en-US/Ksconfig.xml
+++ b/en-US/Ksconfig.xml
@@ -488,7 +488,7 @@
 			If the system to be installed via kickstart does not have an Ethernet card, do not configure one on the <guilabel>Network Configuration</guilabel> page.
 		</para>
 		 <para>
-			Networking is only required if you choose a networking-based installation method (NFS, FTP, or HTTP). Networking can always be configured after installation with the <application>Network Administration Tool</application> (<command>system-config-network</command>). Refer to the Fedora Deployment Guide for details.
+       Networking is only required if you choose a networking-based installation method (NFS, FTP, or HTTP). Networking can always be configured after installation. Refer to the <citetitle>Fedora System Administrators Guide</citetitle> for details.
 		</para>
 		 <para>
 			For each Ethernet card on the system, click <guibutton>Add Network Device</guibutton> and select the network device and network type for the device. Select <guilabel>eth0</guilabel> to configure the first Ethernet card, <guilabel>eth1</guilabel> for the second Ethernet card, and so on.
@@ -565,7 +565,7 @@
 
 		</itemizedlist>
 		 <para>
-			These methods are not enabled by default. To enable one or more of these methods, click the appropriate tab, click the checkbox next to <guilabel>Enable</guilabel>, and enter the appropriate information for the authentication method. Refer to the Fedora Deployment Guide for more information about the options.
+       These methods are not enabled by default. To enable one or more of these methods, click the appropriate tab, click the checkbox next to <guilabel>Enable</guilabel>, and enter the appropriate information for the authentication method. Refer to the <citetitle>Fedora System Administrators Guide<citetitle> for more information about the options.
 		</para>
 
 	</section>
diff --git a/en-US/Steps_Network_Install_section_2-common-para-8.xml b/en-US/Steps_Network_Install_section_2-common-para-8.xml
index f68117e..d204b01 100644
--- a/en-US/Steps_Network_Install_section_2-common-para-8.xml
+++ b/en-US/Steps_Network_Install_section_2-common-para-8.xml
@@ -4,6 +4,6 @@
 %BOOK_ENTITIES;
 ]>
 <para>
-	Be sure to test the NFS share following the directions in the <citetitle>Fedora Deployment Guide</citetitle>. Refer to your NFS documentation for details on starting and stopping the NFS server.
+	Be sure to test the NFS share following the directions in the <citetitle>Fedora System Administrators Guide</citetitle>. Refer to your NFS documentation for details on starting and stopping the NFS server.
 </para>
 
diff --git a/en-US/X86_Bootloader.xml b/en-US/X86_Bootloader.xml
index ec75c88..c09a527 100644
--- a/en-US/X86_Bootloader.xml
+++ b/en-US/X86_Bootloader.xml
@@ -353,7 +353,7 @@
 
 		</itemizedlist>
 		 <para>
-			For additional information, refer to the <citetitle>Fedora Deployment Guide</citetitle>.
+			For additional information, refer to the <citetitle>Fedora System Administrators Guide</citetitle>.
 		</para>
 
 	</section> -->
diff --git a/en-US/pxe-server-config-bios.xml b/en-US/pxe-server-config-bios.xml
index 28e1b4b..e7e5470 100644
--- a/en-US/pxe-server-config-bios.xml
+++ b/en-US/pxe-server-config-bios.xml
@@ -27,7 +27,7 @@
             </step>
 	    <step>
 		    <para>
-		      Configure your DHCP server to use the boot images packaged with SYSLINUX. (If you do not have a DHCP server installed, refer to the <citetitle>DHCP Servers</citetitle> chapter in the <citetitle>Fedora Deployment Guide</citetitle>.)
+		      Configure your DHCP server to use the boot images packaged with SYSLINUX. (If you do not have a DHCP server installed, refer to the <citetitle>DHCP Servers</citetitle> chapter in the <citetitle>Fedora System Administrators Guide</citetitle>.)
 		    </para>
 		    <para>
 		      A sample configuration in <filename>/etc/dhcp/dhcpd.conf</filename> might look like:
diff --git a/en-US/pxe-server-config-efi.xml b/en-US/pxe-server-config-efi.xml
index c766b01..76c0f0a 100644
--- a/en-US/pxe-server-config-efi.xml
+++ b/en-US/pxe-server-config-efi.xml
@@ -39,7 +39,7 @@
             </step>
 		  <step>
 		    <para>
-		      Configure your DHCP server to use the EFI boot images packaged with GRUB. (If you do not have a DHCP server installed, refer to the <citetitle>DHCP Servers</citetitle> chapter in the <citetitle>Fedora Deployment Guide</citetitle>.)
+		      Configure your DHCP server to use the EFI boot images packaged with GRUB. (If you do not have a DHCP server installed, refer to the <citetitle>DHCP Servers</citetitle> chapter in the <citetitle>Fedora System Administrators Guide</citetitle>.)
 		    </para>
 		    <para>
 		      A sample configuration in <filename>/etc/dhcp/dhcpd.conf</filename> might look like:


More information about the docs-commits mailing list