[install-guide/f21-branch] More grammar and technical issues in CustomSpoke
by pbokoc
commit 07386b51017b1476a3563434c3aeea2bbc3441b2
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Tue Nov 18 17:00:50 2014 +0100
More grammar and technical issues in CustomSpoke
en-US/CustomSpoke_AddBtrfs.xml | 2 +-
en-US/CustomSpoke_AddLVM.xml | 2 +-
en-US/CustomSpoke_AddPhysical.xml | 7 ++-----
en-US/CustomSpoke_SoftwareRAID.xml | 11 ++++-------
4 files changed, 8 insertions(+), 14 deletions(-)
---
diff --git a/en-US/CustomSpoke_AddBtrfs.xml b/en-US/CustomSpoke_AddBtrfs.xml
index 542b1c9..6e4aca9 100644
--- a/en-US/CustomSpoke_AddBtrfs.xml
+++ b/en-US/CustomSpoke_AddBtrfs.xml
@@ -83,6 +83,6 @@
Repeat this procedure for any additional Btrfs subvolumes you want to create. Note that when creating additional subvolumes, a new volume is not automatically created each time; instead, any additional subvolumes are assigned to an existing volume.
</para>
<para>
- For each mount point you create, review its settings and make sure that it is assigned to the correct volume, that it has a sufficient capacity, and that it has a descriptive name so you can identify the volume later if you need to.
+ For each mount point you create, review its settings and make sure that it is assigned to the correct volume, that it has sufficient capacity, and that it has a descriptive name so you can identify the subvolume later if you need to.
</para>
</section>
diff --git a/en-US/CustomSpoke_AddLVM.xml b/en-US/CustomSpoke_AddLVM.xml
index f99686f..3ba4616 100644
--- a/en-US/CustomSpoke_AddLVM.xml
+++ b/en-US/CustomSpoke_AddLVM.xml
@@ -88,6 +88,6 @@
Repeat this procedure for any additional logical volumes you want to create. Note that when creating additional LVM logical volumes, a new volume group is not automatically created each time; instead, any additional volumes are assigned to an existing group.
</para>
<para>
- For each mount point you create, review its settings and make sure that it is assigned to the correct group, that it has a sufficient capacity, and that it has a descriptive name so you can identify the volume later if you need to.
+ For each mount point you create, review its settings and make sure that it is assigned to the correct group, that it has sufficient capacity, and that it has a descriptive name so you can identify the volume later if you need to.
</para>
</section>
diff --git a/en-US/CustomSpoke_AddPhysical.xml b/en-US/CustomSpoke_AddPhysical.xml
index 5ba8043..846c28a 100644
--- a/en-US/CustomSpoke_AddPhysical.xml
+++ b/en-US/CustomSpoke_AddPhysical.xml
@@ -49,7 +49,7 @@
</step>
<step>
<para>
- In the <guilabel>Configure Mount Point</guilabel> dialog, you can specify which physical devices (disks) this volume <emphasis>may</emphasis> reside on. You can select one or more disks which will be used to hold this volume by holding down <keycap>Ctrl</keycap> and clicking each disk in the list. If you select multiple disks here, <application>Anaconda</application> will determine where exactly the partition should be created based on how you configured the rest of the installation; if you want to make sure that this partition is placed on a specific hard drive, select only that drive and unselect all others.
+ In the <guilabel>Configure Mount Point</guilabel> dialog, you can specify which physical devices (disks) this volume <emphasis>may</emphasis> reside on. You can select one or more disks which will be used to hold this volume by holding down <keycap>Ctrl</keycap> and clicking each disk in the list. If you select multiple disks here, <application>Anaconda</application> will determine where exactly the partition should be created based on how you configured the rest of the installation. If you want to make sure that this partition is placed on a specific hard drive, select only that drive and unselect all others.
</para>
<para>
After you finish configuring the partition's location, click <guilabel>Save</guilabel> to return to the main <guilabel>Manual Partitioning</guilabel> screen.
@@ -57,14 +57,11 @@
</step>
<step>
<para>
- Configure other settings specific to the subvolume - its <guilabel>Mount Point</guilabel>, <guilabel>Desired Capacity</guilabel>, and <guilabel>File System</guilabel>. Press <guilabel>Update Settings</guilabel> to apply any changes to the configuration.
+ Configure other settings specific to the partition - its <guilabel>Mount Point</guilabel>, <guilabel>Desired Capacity</guilabel>, and <guilabel>File System</guilabel>. Press <guilabel>Update Settings</guilabel> to apply any changes to the configuration.
</para>
</step>
</procedure>
<para>
Repeat this procedure for any additional standard partitions you want to create.
</para>
- <para>
- For each mount point you create, review its settings and make sure that it is assigned to the correct volume, that it has a sufficient capacity, and that it has a descriptive name so you can identify the volume later if you need to.
- </para>
</section>
diff --git a/en-US/CustomSpoke_SoftwareRAID.xml b/en-US/CustomSpoke_SoftwareRAID.xml
index 2550345..0d952d0 100644
--- a/en-US/CustomSpoke_SoftwareRAID.xml
+++ b/en-US/CustomSpoke_SoftwareRAID.xml
@@ -36,7 +36,7 @@
</step>
<step>
<para>
- In the new dialog window, specify a mount point for which you want to create a separate logical volume - for example, <filename class="directory">/</filename>. Optionally, specify a size for the volume using standard units such as MB or GB (for example, <literal>50GB</literal>). Then, click <guilabel>Add mount point</guilabel> to add the volume and return to the main partitioning screen.
+ In the new dialog window, specify a mount point for which you want to create a separate software RAID partition - for example, <filename class="directory">/</filename>. Optionally, specify a size for the new partition using standard units such as MB or GB (for example, <literal>50GB</literal>). Then, click <guilabel>Add mount point</guilabel> to add the mount point and return to the main partitioning screen.
</para>
<note>
<para>
@@ -46,7 +46,7 @@
</step>
<step>
<para>
- The mount point has now been created using the default settings, which means it has been created as an LVM logical volume. Select the newly created mount point in the left pane to configure it further, and convert it to a physical partition by changing the <guilabel>Device Type</guilabel> option to <guilabel>RAID</guilabel>.
+ The mount point has now been created using the default settings, which means it has been created as an LVM logical volume. Select the newly created mount point in the left pane to configure it further, and convert it to a software RAID partition by changing the <guilabel>Device Type</guilabel> option to <guilabel>RAID</guilabel>.
</para>
</step>
<step>
@@ -61,7 +61,7 @@
</step>
<step>
<para>
- In the <guilabel>Configure Mount Point</guilabel> dialog, you can specify which physical devices (disks) this volume <emphasis>may</emphasis> reside on. You can select one or more disks which will be used to hold this volume by holding down <keycap>Ctrl</keycap> and clicking each disk in the list. If you select multiple disks here, <application>Anaconda</application> will determine where exactly the partition should be created based on how you configured the rest of the installation; if you want to make sure that this partition is placed on a specific set of hard drives, select only those drives and unselect all others.
+ In the <guilabel>Configure Mount Point</guilabel> dialog, you can specify which physical devices (disks) this partition <emphasis>may</emphasis> reside on. You can select one or more disks which will be used to hold this partition by holding down <keycap>Ctrl</keycap> and clicking each disk in the list. If you want to make sure that this partition is placed on a specific set of hard drives, select only those drives and unselect all others.
</para>
<para>
After you finish configuring the partition's location, click <guilabel>Save</guilabel> to return to the main <guilabel>Manual Partitioning</guilabel> screen.
@@ -69,14 +69,11 @@
</step>
<step>
<para>
- Configure other settings specific to the subvolume - its <guilabel>Mount Point</guilabel>, <guilabel>Desired Capacity</guilabel>, and <guilabel>File System</guilabel>. Press <guilabel>Update Settings</guilabel> to apply any changes to the configuration.
+ Configure other settings specific to the partition - its <guilabel>Mount Point</guilabel>, <guilabel>Desired Capacity</guilabel>, and <guilabel>File System</guilabel>. Press <guilabel>Update Settings</guilabel> to apply any changes to the configuration.
</para>
</step>
</procedure>
<para>
Repeat this procedure for any additional standard partitions with software RAID you want to create.
</para>
- <para>
- For each mount point you create, review its settings and make sure that it is assigned to the correct volume, that it has a sufficient capacity, and that it has a descriptive name so you can identify the volume later if you need to.
- </para>
</section>
9 years, 6 months
[install-guide/f21-branch] Don't talk about logical volumes in Create Standard Partition unless really needed
by pbokoc
commit f4e3d0f5fb272afd7471c20cf7b9382d5d8bdf9f
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Tue Nov 18 16:51:48 2014 +0100
Don't talk about logical volumes in Create Standard Partition unless really needed
en-US/CustomSpoke_AddPhysical.xml | 7 +++++--
1 files changed, 5 insertions(+), 2 deletions(-)
---
diff --git a/en-US/CustomSpoke_AddPhysical.xml b/en-US/CustomSpoke_AddPhysical.xml
index c2c8a5f..5ba8043 100644
--- a/en-US/CustomSpoke_AddPhysical.xml
+++ b/en-US/CustomSpoke_AddPhysical.xml
@@ -26,11 +26,14 @@
</step>
<step>
<para>
- In the new dialog window, specify a mount point for which you want to create a separate logical volume - for example, <filename class="directory">/</filename>. Optionally, specify a size for the volume using standard units such as MB or GB (for example, <literal>50GB</literal>). Then, click <guilabel>Add mount point</guilabel> to add the volume and return to the main partitioning screen.
+ In the new dialog window, specify a mount point for which you want to create a separate mount point - for example, <filename class="directory">/</filename>. Optionally, specify a size for the partition using standard units such as MB or GB (for example, <literal>50GB</literal>). Then, click <guilabel>Add mount point</guilabel> to add the mount point and return to the main partitioning screen.
</para>
<note>
<para>
- Some partitions have no mount points. When creating a swap partition, use a mount point of <literal>swap</literal>; for BIOS Boot, use <literal>biosboot</literal>; and for an EFI System Partition, use <literal>efi</literal>. This will configure the partition with the correct settings.
+ When creating a swap partition, specify the mount point as <literal>swap</literal>. For a BIOS Boot partition, use <literal>biosboot</literal>. For an EFI System Partition, use <literal>efi</literal>.
+ </para>
+ <para>
+ For information about these partition types, see <xref linkend="sect-installation-gui-manual-partitioning-recommended" />.
</para>
</note>
</step>
9 years, 6 months
[install-guide/f21-branch] Fixing various grammar issues in CustomSpoke
by pbokoc
commit 786f59ae65958820ecf6d4ef812b23dd258dd3c5
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Tue Nov 18 16:34:34 2014 +0100
Fixing various grammar issues in CustomSpoke
en-US/CustomSpoke_AddBtrfs.xml | 12 ++++++------
en-US/CustomSpoke_AddLVM.xml | 8 ++++----
en-US/CustomSpoke_AddPhysical.xml | 2 +-
en-US/CustomSpoke_RecommendedScheme.xml | 2 +-
en-US/CustomSpoke_SoftwareRAID.xml | 4 ++--
5 files changed, 14 insertions(+), 14 deletions(-)
---
diff --git a/en-US/CustomSpoke_AddBtrfs.xml b/en-US/CustomSpoke_AddBtrfs.xml
index e753d88..542b1c9 100644
--- a/en-US/CustomSpoke_AddBtrfs.xml
+++ b/en-US/CustomSpoke_AddBtrfs.xml
@@ -9,11 +9,11 @@
<firstterm>Btrfs</firstterm> is a type of file system, but it has several features characteristic of a storage device. It is designed to make the file system tolerant of errors, and to facilitate the detection and repair of errors when they occur. It uses checksums to ensure the validity of data and metadata, and maintains snapshots of the file system that can be used for backup or repair.
</para>
<para>
- Creating a Btrfs layout is somewhat similar to LVM (described in <xref linkend="sect-installation-gui-manual-partitioning-lvm" />) with slightly different terminology. A Btrfs <firstterm>volume</firstterm> is the equivalent of a LVM volume group, and a Btrfs <firstterm>subvolume</firstterm> is similar to a LVM logical volume. An important difference to note is how <application>Anaconda</application> reports sizes of separate mount points: For LVM, the exact size of each logical volume is shown next to each mount point in the left pane, while with Btrfs, the total size of the entire volume is shown next to each subvolume.
+ Creating a Btrfs layout is somewhat similar to LVM (described in <xref linkend="sect-installation-gui-manual-partitioning-lvm" />) with slightly different terminology. A Btrfs <firstterm>volume</firstterm> is the equivalent of an LVM volume group, and a Btrfs <firstterm>subvolume</firstterm> is similar to a LVM logical volume. An important difference to note is how <application>Anaconda</application> reports sizes for separate mount points: For LVM, the exact size of each logical volume is shown next to each mount point in the left pane, while with Btrfs, the total size of the entire volume is shown next to each subvolume.
</para>
<warning>
<para>
- Some partition types - notably the <filename class="directory">/boot</filename> and <filename class="directory">/usr</filename> directories and the BIOS Boot and EFI partitions - can not be placed on Btrfs subvolumes. Use standard physical volumes for them (or a LVM logical volume for <filename class="directory">/usr</filename>). See <xref linkend="sect-installation-gui-manual-partitioning-recommended" /> for more information.
+ Some partition types - notably the <filename class="directory">/boot</filename> and <filename class="directory">/usr</filename> directories and the BIOS Boot and EFI partitions - can not be placed on Btrfs subvolumes. Use standard physical volumes for them (or an LVM logical volume for <filename class="directory">/usr</filename>). See <xref linkend="sect-installation-gui-manual-partitioning-recommended" /> for more information.
</para>
</warning>
<para>
@@ -31,11 +31,11 @@
</step>
<step>
<para>
- In the new dialog window, specify a mount point you want to create a separate logical volume for - for example, <filename class="directory">/</filename>. Optionally, specify a size for the volume using standard units such as MB or GB (for example, <literal>50GB</literal>). Then, click <guilabel>Add mount point</guilabel> to add the volume and return to the main partitioning screen.
+ In the new dialog window, specify a mount point for which you want to create a separate logical volume - for example, <filename class="directory">/</filename>. Optionally, specify a size for the volume using standard units such as MB or GB (for example, <literal>50GB</literal>). Then, click <guilabel>Add mount point</guilabel> to add the volume and return to the main partitioning screen.
</para>
<note>
<para>
- When creating mount point for swap on Btrfs, specify the mount point as <literal>swap</literal>.
+ When creating a mount point for swap on Btrfs, specify the mount point as <literal>swap</literal>.
</para>
</note>
</step>
@@ -62,7 +62,7 @@
You can also make sure that the volume is encrypted by selecting the <guilabel>Encrypt</guilabel> option; this will enable LUKS encryption for the entire volume. See the <citetitle>&PRODUCT; Security Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />, for information about LUKS disk encryption.
</para>
<para>
- Additionally, you can set a fixed size for the volume by selecting the <guilabel>Fixed</guilabel> option from the <guilabel>Size policy</guilabel> menu, and entering a size for the volume group.
+ Additionally, you can set a fixed size for the volume by selecting the <guilabel>Fixed</guilabel> option from the <guilabel>Size policy</guilabel> menu and entering a size for the volume group.
</para>
<para>
After you finish configuring the Btrfs volume settings, click <guilabel>Save</guilabel> to return to the main <guilabel>Manual Partitioning</guilabel> screen.
@@ -70,7 +70,7 @@
</step>
<step>
<para>
- If you need to create more than one Btrfs volume, open the <guilabel>Volume</guilabel> drop-down menu, and select the <guilabel>Create a new volume group</guilabel> option. A new dialog window will open, identical to the one described in the previous step; again, select a name, storage devices, encryption settings, RAID level and size policy for the new volume, and click <guilabel>Save</guilabel>. The new volume will then become available in the <guilabel>Volume Group</guilabel> drop-down menu; you can then go through your existing mount points and change this setting to assign them to a different volume.
+ If you need to create more than one Btrfs volume, open the <guilabel>Volume</guilabel> drop-down menu and select the <guilabel>Create a new volume group</guilabel> option. A new dialog window will open, identical to the one described in the previous step. Again, select a name, storage devices, encryption settings, RAID level and size policy for the new volume, and click <guilabel>Save</guilabel>. The new volume will then become available in the <guilabel>Volume Group</guilabel> drop-down menu; you can then go through your existing mount points and change this setting to assign them to a different volume.
</para>
</step>
<step>
diff --git a/en-US/CustomSpoke_AddLVM.xml b/en-US/CustomSpoke_AddLVM.xml
index b61fcd0..f99686f 100644
--- a/en-US/CustomSpoke_AddLVM.xml
+++ b/en-US/CustomSpoke_AddLVM.xml
@@ -31,11 +31,11 @@
</step>
<step>
<para>
- In the new dialog window, specify a mount point you want to create a separate logical volume for - for example, <filename class="directory">/</filename>. Optionally, specify a size for the volume using standard units such as MB or GB (for example, <literal>50GB</literal>). Then, click <guilabel>Add mount point</guilabel> to add the volume and return to the main partitioning screen.
+ In the new dialog window, specify a mount point for which you want to create a separate logical volume - for example, <filename class="directory">/</filename>. Optionally, specify a size for the volume using standard units such as MB or GB (for example, <literal>50GB</literal>). Then, click <guilabel>Add mount point</guilabel> to add the volume and return to the main partitioning screen.
</para>
<note>
<para>
- When creating mount point for swap on LVM, specify the mount point as <literal>swap</literal>.
+ When creating a mount point for swap on LVM, specify the mount point as <literal>swap</literal>.
</para>
</note>
</step>
@@ -62,7 +62,7 @@
You can also make sure that the volume group is encrypted by selecting the <guilabel>Encrypt</guilabel> option; this will enable LUKS encryption for the entire volume group. See the <citetitle>&PRODUCT; Security Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />, for information about LUKS disk encryption.
</para>
<para>
- Additionally, you can set a fixed size for the volume group by selecting the <guilabel>Fixed</guilabel> option from the <guilabel>Size policy</guilabel> menu, and entering a size for the volume group.
+ Additionally, you can set a fixed size for the volume group by selecting the <guilabel>Fixed</guilabel> option from the <guilabel>Size policy</guilabel> menu and entering a size for the volume group.
</para>
<para>
After you finish configuring the volume group settings, click <guilabel>Save</guilabel> to return to the main <guilabel>Manual Partitioning</guilabel> screen.
@@ -75,7 +75,7 @@
</step>
<step>
<para>
- If you need to create more than one volume group, open the <guilabel>Volume Group</guilabel> drop-down menu, and select the <guilabel>Create a new volume group</guilabel> option. A new dialog window will open, identical to the one described in the previous step; again, select a name, storage devices, encryption settings, RAID level and size policy for the new group, and click <guilabel>Save</guilabel>. The new volume group will then become available in the <guilabel>Volume Group</guilabel> drop-down menu; you can then go through your existing mount points and change this setting to assign them to a different volume group.
+ If you need to create more than one volume group, open the <guilabel>Volume Group</guilabel> drop-down menu and select the <guilabel>Create a new volume group</guilabel> option. A new dialog window will open, identical to the one described in the previous step. Again, select a name, storage devices, encryption settings, RAID level and size policy for the new group, and click <guilabel>Save</guilabel>. The new volume group will then become available in the <guilabel>Volume Group</guilabel> drop-down menu; you can then go through your existing mount points and change this setting to assign them to a different volume group.
</para>
</step>
<step>
diff --git a/en-US/CustomSpoke_AddPhysical.xml b/en-US/CustomSpoke_AddPhysical.xml
index 56ef81e..c2c8a5f 100644
--- a/en-US/CustomSpoke_AddPhysical.xml
+++ b/en-US/CustomSpoke_AddPhysical.xml
@@ -26,7 +26,7 @@
</step>
<step>
<para>
- In the new dialog window, specify a mount point you want to create a separate logical volume for - for example, <filename class="directory">/</filename>. Optionally, specify a size for the volume using standard units such as MB or GB (for example, <literal>50GB</literal>). Then, click <guilabel>Add mount point</guilabel> to add the volume and return to the main partitioning screen.
+ In the new dialog window, specify a mount point for which you want to create a separate logical volume - for example, <filename class="directory">/</filename>. Optionally, specify a size for the volume using standard units such as MB or GB (for example, <literal>50GB</literal>). Then, click <guilabel>Add mount point</guilabel> to add the volume and return to the main partitioning screen.
</para>
<note>
<para>
diff --git a/en-US/CustomSpoke_RecommendedScheme.xml b/en-US/CustomSpoke_RecommendedScheme.xml
index 9fcbd27..cb72e93 100644
--- a/en-US/CustomSpoke_RecommendedScheme.xml
+++ b/en-US/CustomSpoke_RecommendedScheme.xml
@@ -182,7 +182,7 @@
</variablelist>
<important>
<para>
- If your system requires either a BIOS Boot partition or an EFI System Partition based on the requirements detailed above, this partition must be created as a standard physical partition. It can not reside on a LVM volume or a Btrfs subvolume.
+ If your system requires either a BIOS Boot partition or an EFI System Partition based on the requirements detailed above, this partition must be created as a standard physical partition. It can not reside on an LVM volume or a Btrfs subvolume.
</para>
</important>
<para>
diff --git a/en-US/CustomSpoke_SoftwareRAID.xml b/en-US/CustomSpoke_SoftwareRAID.xml
index 9889157..2550345 100644
--- a/en-US/CustomSpoke_SoftwareRAID.xml
+++ b/en-US/CustomSpoke_SoftwareRAID.xml
@@ -36,11 +36,11 @@
</step>
<step>
<para>
- In the new dialog window, specify a mount point you want to create a software RAID device for - for example, <filename class="directory">/</filename>. Optionally, specify a size for the volume using standard units such as MB or GB (for example, <literal>50GB</literal>). Then, click <guilabel>Add mount point</guilabel> to add the volume and return to the main partitioning screen.
+ In the new dialog window, specify a mount point for which you want to create a separate logical volume - for example, <filename class="directory">/</filename>. Optionally, specify a size for the volume using standard units such as MB or GB (for example, <literal>50GB</literal>). Then, click <guilabel>Add mount point</guilabel> to add the volume and return to the main partitioning screen.
</para>
<note>
<para>
- When creating mount point for swap on software RAID, specify the mount point as <literal>swap</literal>.
+ When creating a mount point for swap on software RAID, specify the mount point as <literal>swap</literal>.
</para>
</note>
</step>
9 years, 6 months
[install-guide/f21-branch] Change some wording on the Progress Hub to sound more correct.
by pbokoc
commit 7f755c25d468e3c3c9ef86b69136638b9d424281
Author: Samantha N. Bueno <sbueno+anaconda(a)redhat.com>
Date: Mon Nov 17 10:42:28 2014 -0500
Change some wording on the Progress Hub to sound more correct.
en-US/ProgressHub.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/en-US/ProgressHub.xml b/en-US/ProgressHub.xml
index f649acf..1d54757 100644
--- a/en-US/ProgressHub.xml
+++ b/en-US/ProgressHub.xml
@@ -12,7 +12,7 @@
<remark>TODO: screen</remark>
</para>
<para>
- In the top part of the screen, two additional options are available, allowing you to configure authentication settings - the <systemitem class="username">root</systemitem> password and an additional user account. Configuring <systemitem class="username">root</systemitem> the password is required to finish the installation; creating a user account can be skipped. If you do so, you will be prompted to create a non-root user account after the installation finishes and your system reboots.
+ In the top part of the screen, two additional options are available, allowing you to configure authentication settings - the <systemitem class="username">root</systemitem> password and an additional user account. Configuring the <systemitem class="username">root</systemitem> password is required to finish the installation; creating a user account can be skipped. If you do so, you will be prompted to create a non-root user account after the installation finishes and your system reboots.
</para>
<para>
The bottom of the screen shows a progress bar and a message informing you of the current progress of the installation. When the installation finishes and the <systemitem class="username">root</systemitem> password has been set, you can press the <guilabel>Finish configuration</guilabel> button to reboot your computer and log in to your newly installed &PRODUCT; system.
9 years, 6 months
[install-guide/f21-branch] Changing links to the Docs website so they're exposed
by pbokoc
commit 1b9ea528acec4128f4c03ea8b1555494701b381f
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Tue Nov 18 15:02:23 2014 +0100
Changing links to the Docs website so they're exposed
en-US/Boot_Options.xml | 4 ++--
en-US/CustomSpoke_AddBtrfs.xml | 2 +-
en-US/CustomSpoke_AddLVM.xml | 2 +-
en-US/Kickstart_Syntax_Reference.xml | 14 +++++++-------
en-US/NetworkSpoke.xml | 2 +-
en-US/NetworkSpoke_EditConnection.xml | 2 +-
en-US/NetworkSpoke_VirtualInterfaces.xml | 2 +-
en-US/Network_based_Installations.xml | 2 +-
en-US/PasswordSpoke.xml | 2 +-
en-US/StorageSpoke.xml | 2 +-
en-US/StorageSpoke_BootLoader.xml | 2 +-
en-US/Troubleshooting.xml | 8 ++++----
en-US/UserSpoke.xml | 2 +-
en-US/VNC_Installations.xml | 2 +-
14 files changed, 24 insertions(+), 24 deletions(-)
---
diff --git a/en-US/Boot_Options.xml b/en-US/Boot_Options.xml
index 1b99614..cedb998 100644
--- a/en-US/Boot_Options.xml
+++ b/en-US/Boot_Options.xml
@@ -455,7 +455,7 @@
<term><option>inst.sshd</option></term>
<listitem>
<para>
- Starts the <systemitem class="service">sshd</systemitem> service during the installation, which allows you to connect to the system during the installation using <systemitem class="protocol">SSH</systemitem> and monitor its progress. For more information on <systemitem class="protocol">SSH</systemitem>, see the <systemitem>ssh(1)</systemitem> man page and the corresponding chapter in the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at the <ulink url="httpL//docs.fedoraproject.org/">&PRODUCT; Documentation website</ulink>.
+ Starts the <systemitem class="service">sshd</systemitem> service during the installation, which allows you to connect to the system during the installation using <systemitem class="protocol">SSH</systemitem> and monitor its progress. For more information on <systemitem class="protocol">SSH</systemitem>, see the <systemitem>ssh(1)</systemitem> man page and the corresponding chapter in the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />.
</para>
<note>
<para>
@@ -470,7 +470,7 @@
<section id="sect-boot-options-network">
<title>Network Boot Options</title>
<para>
- Initial network initialization is handled by <application>dracut</application>. This section only lists some of the more commonly used options; for a complete list, see the <systemitem>dracut.cmdline(7)</systemitem> man page. Additional information on networking is also available in the <citetitle>&PRODUCT; Networking Guide</citetitle>, available at the <ulink url="http://docs.fedoraproject.org/">&PRODUCT; Documentation website</ulink>.
+ Initial network initialization is handled by <application>dracut</application>. This section only lists some of the more commonly used options; for a complete list, see the <systemitem>dracut.cmdline(7)</systemitem> man page. Additional information on networking is also available in the <citetitle>&PRODUCT; Networking Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />.
</para>
<variablelist>
<varlistentry>
diff --git a/en-US/CustomSpoke_AddBtrfs.xml b/en-US/CustomSpoke_AddBtrfs.xml
index c604e3a..e753d88 100644
--- a/en-US/CustomSpoke_AddBtrfs.xml
+++ b/en-US/CustomSpoke_AddBtrfs.xml
@@ -59,7 +59,7 @@
</para>
</note>
<para>
- You can also make sure that the volume is encrypted by selecting the <guilabel>Encrypt</guilabel> option; this will enable LUKS encryption for the entire volume. See the <citetitle>&PRODUCT; Security Guide</citetitle>, available at the <ulink url="http://docs.fedoraproject.org/">&PRODUCT; Documentation website</ulink>, for information about LUKS disk encryption.
+ You can also make sure that the volume is encrypted by selecting the <guilabel>Encrypt</guilabel> option; this will enable LUKS encryption for the entire volume. See the <citetitle>&PRODUCT; Security Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />, for information about LUKS disk encryption.
</para>
<para>
Additionally, you can set a fixed size for the volume by selecting the <guilabel>Fixed</guilabel> option from the <guilabel>Size policy</guilabel> menu, and entering a size for the volume group.
diff --git a/en-US/CustomSpoke_AddLVM.xml b/en-US/CustomSpoke_AddLVM.xml
index 99e646b..b61fcd0 100644
--- a/en-US/CustomSpoke_AddLVM.xml
+++ b/en-US/CustomSpoke_AddLVM.xml
@@ -59,7 +59,7 @@
</para>
</note>
<para>
- You can also make sure that the volume group is encrypted by selecting the <guilabel>Encrypt</guilabel> option; this will enable LUKS encryption for the entire volume group. See the <citetitle>&PRODUCT; Security Guide</citetitle>, available at the <ulink url="http://docs.fedoraproject.org/">&PRODUCT; Documentation website</ulink>, for information about LUKS disk encryption.
+ You can also make sure that the volume group is encrypted by selecting the <guilabel>Encrypt</guilabel> option; this will enable LUKS encryption for the entire volume group. See the <citetitle>&PRODUCT; Security Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />, for information about LUKS disk encryption.
</para>
<para>
Additionally, you can set a fixed size for the volume group by selecting the <guilabel>Fixed</guilabel> option from the <guilabel>Size policy</guilabel> menu, and entering a size for the volume group.
diff --git a/en-US/Kickstart_Syntax_Reference.xml b/en-US/Kickstart_Syntax_Reference.xml
index 4ad9f94..f50060b 100644
--- a/en-US/Kickstart_Syntax_Reference.xml
+++ b/en-US/Kickstart_Syntax_Reference.xml
@@ -36,7 +36,7 @@
The <option>-f</option> option specifies the release to start the comparison with, and the <option>-t</option> option to specify the release to end with. For additional information, see the <systemitem>ksverdiff(1)</systemitem> man page. Also note that you can not use this to display changes in a release that is newer than your system - the version of <package>pykickstart</package> on Fedora &PREVVER; can not display changes in Fedora &PRODVER;.
</para>
<para>
- Additionally, you can review the <citetitle>Fedora &PRODVER; Release Notes</citetitle>, available at <ulink url="http://docs.fedoraproject.org/">Fedora Documentation</ulink>, for a list of changes.
+ Additionally, you can review the <citetitle>Fedora &PRODVER; Release Notes</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />, for a list of changes.
</para>
<note>
<para>
@@ -338,7 +338,7 @@
<command>repo --name=<replaceable>repoid</replaceable> [--baseurl=<replaceable><url></replaceable>|--mirrorlist=<replaceable>url</replaceable>] [<replaceable>options</replaceable>]</command>
</programlisting>
<para>
- See the <citetitle>Fedora System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/">Fedora Documentation</ulink>, for information about the <application>Yum</application> package manager.
+ See the <citetitle>Fedora System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />, for information about the <application>Yum</application> package manager.
</para>
<important>
<para>
@@ -520,7 +520,7 @@
<term><option>--cipher=</option></term>
<listitem>
<para>
- Specifies which type of encryption will be used if the <application>Anaconda</application> default <systemitem>aes-xts-plain64</systemitem> is not satisfactory. You must use this option together with the <option>--encrypted</option> option; by itself it has no effect. Available types of encryption are listed in the <citetitle>Fedora Security Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/">Fedora Documentation</ulink>. Using either <systemitem>aes-xts-plain64</systemitem> or <systemitem>aes-cbc-essiv:sha256</systemitem> is strongly recommended.
+ Specifies which type of encryption will be used if the <application>Anaconda</application> default <systemitem>aes-xts-plain64</systemitem> is not satisfactory. You must use this option together with the <option>--encrypted</option> option; by itself it has no effect. Available types of encryption are listed in the <citetitle>Fedora Security Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />. Using either <systemitem>aes-xts-plain64</systemitem> or <systemitem>aes-cbc-essiv:sha256</systemitem> is strongly recommended.
</para>
</listitem>
</varlistentry>
@@ -1246,7 +1246,7 @@
<term><option>--cipher=</option></term>
<listitem>
<para>
- Specifies which type of encryption will be used if the <application>Anaconda</application> default <systemitem>aes-xts-plain64</systemitem> is not satisfactory. You must use this option together with the <option>--encrypted</option> option; by itself it has no effect. Available types of encryption are listed in the <citetitle>Fedora Security Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/">Fedora Documentation</ulink>. Using either <systemitem>aes-xts-plain64</systemitem> or <systemitem>aes-cbc-essiv:sha256</systemitem> is strongly recommended.
+ Specifies which type of encryption will be used if the <application>Anaconda</application> default <systemitem>aes-xts-plain64</systemitem> is not satisfactory. You must use this option together with the <option>--encrypted</option> option; by itself it has no effect. Available types of encryption are listed in the <citetitle>Fedora Security Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />. Using either <systemitem>aes-xts-plain64</systemitem> or <systemitem>aes-cbc-essiv:sha256</systemitem> is strongly recommended.
</para>
</listitem>
</varlistentry>
@@ -1595,7 +1595,7 @@
<term><option>--cipher=</option></term>
<listitem>
<para>
- Specifies which type of encryption will be used if the <application>Anaconda</application> default <systemitem>aes-xts-plain64</systemitem> is not satisfactory. You must use this option together with the <option>--encrypted</option> option; by itself it has no effect. Available types of encryption are listed in the <citetitle>Fedora Security Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/">Fedora Documentation</ulink>. Using either <systemitem>aes-xts-plain64</systemitem> or <systemitem>aes-cbc-essiv:sha256</systemitem> is strongly recommended.
+ Specifies which type of encryption will be used if the <application>Anaconda</application> default <systemitem>aes-xts-plain64</systemitem> is not satisfactory. You must use this option together with the <option>--encrypted</option> option; by itself it has no effect. Available types of encryption are listed in the <citetitle>Fedora Security Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />. Using either <systemitem>aes-xts-plain64</systemitem> or <systemitem>aes-cbc-essiv:sha256</systemitem> is strongly recommended.
</para>
</listitem>
</varlistentry>
@@ -1733,7 +1733,7 @@
<term><option>--cipher=</option></term>
<listitem>
<para>
- Specifies which type of encryption will be used if the <application>Anaconda</application> default <systemitem>aes-xts-plain64</systemitem> is not satisfactory. You must use this option together with the <option>--encrypted</option> option; by itself it has no effect. Available types of encryption are listed in the <citetitle>Fedora Security Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/">Fedora Documentation</ulink>. Using either <systemitem>aes-xts-plain64</systemitem> or <systemitem>aes-cbc-essiv:sha256</systemitem> is strongly recommended.
+ Specifies which type of encryption will be used if the <application>Anaconda</application> default <systemitem>aes-xts-plain64</systemitem> is not satisfactory. You must use this option together with the <option>--encrypted</option> option; by itself it has no effect. Available types of encryption are listed in the <citetitle>Fedora Security Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />. Using either <systemitem>aes-xts-plain64</systemitem> or <systemitem>aes-cbc-essiv:sha256</systemitem> is strongly recommended.
</para>
</listitem>
</varlistentry>
@@ -2282,7 +2282,7 @@
<command>network --bondopts=mode=active-backup,balance-rr;primary=eth1</command>
</programlisting>
<para>
- Available optional parameters are listed in the <citetitle>Working with Kernel Modules</citetitle> chapter of the <citetitle>Fedora System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/">Fedora Documentation</ulink>.
+ Available optional parameters are listed in the <citetitle>Working with Kernel Modules</citetitle> chapter of the <citetitle>Fedora System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />.
</para>
<important>
<para>
diff --git a/en-US/NetworkSpoke.xml b/en-US/NetworkSpoke.xml
index 31c0805..731b735 100644
--- a/en-US/NetworkSpoke.xml
+++ b/en-US/NetworkSpoke.xml
@@ -10,7 +10,7 @@
</para>
<note>
<para>
- Network configuration is an expansive topic and many of the options available during the installation are beyond the scope of this document. For detailed information about networking, including both theoretical topics and specific instructions and examples, see the <citetitle>&PRODUCT; Networking Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/">&PRODUCT; Documentation</ulink>.
+ Network configuration is an expansive topic and many of the options available during the installation are beyond the scope of this document. For detailed information about networking, including both theoretical topics and specific instructions and examples, see the <citetitle>&PRODUCT; Networking Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />.
</para>
</note>
<para>
diff --git a/en-US/NetworkSpoke_EditConnection.xml b/en-US/NetworkSpoke_EditConnection.xml
index 0c358f5..bddf74d 100644
--- a/en-US/NetworkSpoke_EditConnection.xml
+++ b/en-US/NetworkSpoke_EditConnection.xml
@@ -6,7 +6,7 @@
<section id="sect-installation-gui-network-configuration-advanced">
<title>Editing Network Interface Configuration</title>
<para>
- This section only details the most important settings for a typical wired connection used during installation. Many of the available options do not have to be changed in most installation scenarios and are not carried over to the installed system. Configuration of other types of networks is broadly similar, although the specific configuration parameters may be different. To learn more about network configuration after installation, see the <citetitle>&PRODUCT; Networking Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/">&PRODUCT; Documentation</ulink>.
+ This section only details the most important settings for a typical wired connection used during installation. Many of the available options do not have to be changed in most installation scenarios and are not carried over to the installed system. Configuration of other types of networks is broadly similar, although the specific configuration parameters may be different. To learn more about network configuration after installation, see the <citetitle>&PRODUCT; Networking Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />.
</para>
<para>
To configure a network connection manually, select that connection in the list on the left side of the screen, and click the <guilabel>Configure</guilabel> button. A dialog will appear that allows you to configure the selected connection. The configuration options presented depends on the connection type - the available options will be slightly different depending on whether it is a physical interface (wired or wireless network interface controller) or a virtual interface (Bond, Team or Vlan) which you previously configured in <xref linkend="sect-installation-gui-network-configuration-virtual-interface" />.. A full description of all configuration settings for all connection types is beyond the scope of this document; see the <citetitle>Networking Guide</citetitle> for details.
diff --git a/en-US/NetworkSpoke_VirtualInterfaces.xml b/en-US/NetworkSpoke_VirtualInterfaces.xml
index addb8c0..38ffe7a 100644
--- a/en-US/NetworkSpoke_VirtualInterfaces.xml
+++ b/en-US/NetworkSpoke_VirtualInterfaces.xml
@@ -26,7 +26,7 @@
</listitem>
</itemizedlist>
<para>
- Select the interface type you want to add, and click <guilabel>Add</guilabel>. Another dialog window will open, allowing you to edit any available settings for your chosen interface type. For information about available settings, see the respective sections of the <citetitle>&PRODUCT; Networking Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/">&PRODUCT; Documentation</ulink>. Basic documentation is also available in <xref linkend="sect-installation-gui-network-configuration-advanced" />.
+ Select the interface type you want to add, and click <guilabel>Add</guilabel>. Another dialog window will open, allowing you to edit any available settings for your chosen interface type. For information about available settings, see the respective sections of the <citetitle>&PRODUCT; Networking Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />. Basic documentation is also available in <xref linkend="sect-installation-gui-network-configuration-advanced" />.
</para>
<note>
<para>
diff --git a/en-US/Network_based_Installations.xml b/en-US/Network_based_Installations.xml
index f4dc714..54fe19f 100644
--- a/en-US/Network_based_Installations.xml
+++ b/en-US/Network_based_Installations.xml
@@ -305,7 +305,7 @@ menuentry 'Rescue installed system' --class fedora --class gnu-linux --class gn
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 <citetitle>Fedora System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org">Fedora Documentation</ulink>, to configure <systemitem class="daemon">httpd</systemitem>.
+ 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 <citetitle>Fedora System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />, to configure <systemitem class="daemon">httpd</systemitem>.
</para>
</section>
diff --git a/en-US/PasswordSpoke.xml b/en-US/PasswordSpoke.xml
index 296b722..631439e 100644
--- a/en-US/PasswordSpoke.xml
+++ b/en-US/PasswordSpoke.xml
@@ -13,7 +13,7 @@
</para>
<warning>
<para>
- The <systemitem class="username">root</systemitem> account has complete control over the system. If an unauthorized person gains access to this account, access or delete all users' personal files or otherwise exploit the machine for their own nefarious purposes. See the <citetitle>&PRODUCT; Security Guide</citetitle>, available at the <ulink url="http://docs.fedoraproject.org/">&PRODUCT; Documentation website</ulink>, for detailed documentation about account security and guidelines for choosing a strong password.
+ The <systemitem class="username">root</systemitem> account has complete control over the system. If an unauthorized person gains access to this account, access or delete all users' personal files or otherwise exploit the machine for their own nefarious purposes. See the <citetitle>&PRODUCT; Security Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />, for detailed documentation about account security and guidelines for choosing a strong password.
</para>
</warning>
<para>
diff --git a/en-US/StorageSpoke.xml b/en-US/StorageSpoke.xml
index 125fe72..45db3e8 100644
--- a/en-US/StorageSpoke.xml
+++ b/en-US/StorageSpoke.xml
@@ -58,7 +58,7 @@
</listitem>
</itemizedlist>
<para>
- Additionally, you can select <guilabel>Encrypt my data</guilabel>; this will encrypt all partitions except the ones needed to boot the system (such as <filename class="directory">/boot</filename>) using <firstterm>Linux Unified Key Setup</firstterm> (LUKS). Encrypting your hard drive is recommended. For detailed information about LUKS encryption, see the <citetitle>&PRODUCT; Security Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/">&PRODUCT; Documentation</ulink>.
+ Additionally, you can select <guilabel>Encrypt my data</guilabel>; this will encrypt all partitions except the ones needed to boot the system (such as <filename class="directory">/boot</filename>) using <firstterm>Linux Unified Key Setup</firstterm> (LUKS). Encrypting your hard drive is recommended. For detailed information about LUKS encryption, see the <citetitle>&PRODUCT; Security Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />.
</para>
<warning>
<para>
diff --git a/en-US/StorageSpoke_BootLoader.xml b/en-US/StorageSpoke_BootLoader.xml
index 72bdf81..aca52e2 100644
--- a/en-US/StorageSpoke_BootLoader.xml
+++ b/en-US/StorageSpoke_BootLoader.xml
@@ -14,7 +14,7 @@
</para>
</warning>
<para>
- If you have other operating systems already installed, the &PRODUCT; installer will attempt to automatically detect and configure the boot loader to start them. You can manually configure any additional operating systems after you finish the installation, if they are not detected properly. For instructions on editing <application>GRUB2</application> configuration, see the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/">&PRODUCT; Documentation</ulink>
+ If you have other operating systems already installed, the &PRODUCT; installer will attempt to automatically detect and configure the boot loader to start them. You can manually configure any additional operating systems after you finish the installation, if they are not detected properly. For instructions on editing <application>GRUB2</application> configuration, see the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />
</para>
<para>
To specify which device the boot loader should be installed on, click the <guilabel>Full disk summary and bootloader</guilabel> link at the bottom of the <guilabel>Installation Destination</guilabel> screen. The <guilabel>Selected Disks</guilabel> dialog will appear. If you are configuring your partitioning layout manually, the same dialog can be accessed from <xref linkend="sect-installation-gui-manual-partitioning" /> using the <guilabel><replaceable>X</replaceable> storage devices selected</guilabel> link in the bottom left corner of the screen.
diff --git a/en-US/Troubleshooting.xml b/en-US/Troubleshooting.xml
index eb41d2e..a054b3a 100644
--- a/en-US/Troubleshooting.xml
+++ b/en-US/Troubleshooting.xml
@@ -585,7 +585,7 @@ GRUB_CMDLINE_LINUX="rd.lvm.lv=rhel/root rd.md=0 rd.dm=0 vconsole.keymap=us $([ -
After you finish this procedure, you can reboot your computer. &PRODUCT; will not use the graphical boot sequence any more. If you wish to enable graphical boot, follow the same procedure, add the <literal>rhgb</literal> option to the <literal>GRUB_CMDLINE_LINUX</literal> line in the <filename>/etc/default/grub</filename> file and refresh the boot loader configuration again using the <command>grub2-mkconfig</command> command.
</para>
<para>
- See the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org">&PRODUCT; Documentation</ulink>, for more information about working with the <application>GRUB2</application> boot loader.
+ See the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />, for more information about working with the <application>GRUB2</application> boot loader.
</para>
</section>
@@ -620,7 +620,7 @@ GRUB_CMDLINE_LINUX="rd.lvm.lv=rhel/root rd.md=0 rd.dm=0 vconsole.keymap=us $([ -
<prompt>#</prompt> <command>systemctl set-default multi-user.target</command>
</screen>
<para>
- For more information about targets in <application>systemd</application>, see the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org">&PRODUCT; Documentation</ulink>.
+ For more information about targets in <application>systemd</application>, see the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />.
</para>
</section>
@@ -677,7 +677,7 @@ tmpfs 1.8G 2.6M 1.8G 1% /tmp
Some hardware configurations have a part of the system's RAM reserved and unavailable to the main system. Notably, laptop computers with integrated graphics cards will reserve some memory for the GPU. For example, a laptop with 4 GB of RAM and an integrated Intel graphics card will show only roughly 3.7 GB of available memory, even with a 64-bit system.
</para>
<para>
- Additionally, the <application>kdump</application> crash kernel dumping mechanism reserves some memory for the secondary kernel used in case of the primary kernel crashing. This reserved memory will also not be displayed as available when using the <command>free</command> command. For details about <application>kdump</application> and its memory requirements, see the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org">&PRODUCT; Documentation</ulink>.
+ Additionally, the <application>kdump</application> crash kernel dumping mechanism reserves some memory for the secondary kernel used in case of the primary kernel crashing. This reserved memory will also not be displayed as available when using the <command>free</command> command. For details about <application>kdump</application> and its memory requirements, see the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />.
</para>
</note>
<para>
@@ -744,7 +744,7 @@ GRUB_CMDLINE_LINUX="rd.lvm.lv=rhel/root vconsole.font=latarcyrheb-sun16 rd.lvm.l
GRUB_DISABLE_RECOVERY="true"
</programlisting>
<para>
- See the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org">&PRODUCT; Documentation</ulink>, for more information about working with the <application>GRUB2</application> boot loader.
+ See the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />, for more information about working with the <application>GRUB2</application> boot loader.
</para>
</section>
diff --git a/en-US/UserSpoke.xml b/en-US/UserSpoke.xml
index 93a1c9b..f4aeb9e 100644
--- a/en-US/UserSpoke.xml
+++ b/en-US/UserSpoke.xml
@@ -39,7 +39,7 @@
If you give administrator privileges to an user, make sure that the account is protected by a strong password. Never give an user administrator privileges without requiring any password for the account.
</para>
<para>
- See the <citetitle>&PRODUCT; Security Guide</citetitle>, available at the <ulink url="http://docs.fedoraproject.org/">&PRODUCT; Documentation website</ulink>, for detailed information about password security including guidelines for selecting strong passwords.
+ See the <citetitle>&PRODUCT; Security Guide</citetitle>, available at the <ulink url="http://docs.fedoraproject.org/" />, for detailed information about password security including guidelines for selecting strong passwords.
</para>
</warning>
<para>
diff --git a/en-US/VNC_Installations.xml b/en-US/VNC_Installations.xml
index 7178b9f..fb5ff89 100644
--- a/en-US/VNC_Installations.xml
+++ b/en-US/VNC_Installations.xml
@@ -194,7 +194,7 @@
<section id="sect-vnc-installations-connect-mode">
<title>Installing in VNC Connect Mode</title>
<para>
- VNC connect mode is when the system being installed initiates a connection to the VNC viewer running on a remote system. Before you start, make sure the remote system is configured to accept incoming connection on the port you want to use for VNC. The exact way to make sure the connection will not be blocked depends on your network and on your workstation's configuration. Information about configuring the firewall in &PRODUCT; is available in the <citetitle>&PRODUCT; Security Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org">&PRODUCT; Documentation</ulink>.
+ VNC connect mode is when the system being installed initiates a connection to the VNC viewer running on a remote system. Before you start, make sure the remote system is configured to accept incoming connection on the port you want to use for VNC. The exact way to make sure the connection will not be blocked depends on your network and on your workstation's configuration. Information about configuring the firewall in &PRODUCT; is available in the <citetitle>&PRODUCT; Security Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />.
</para>
<procedure id="proc-vnc-installations-connect-mode">
<title>Starting VNC in Connect Mode</title>
9 years, 6 months
[install-guide/f21-branch] Clarifying mount point names in CustomSpoke
by pbokoc
commit b771ae436df7b575b53a16357609c0caaa16811e
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Mon Nov 17 22:40:18 2014 +0100
Clarifying mount point names in CustomSpoke
en-US/CustomSpoke_AddPhysical.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/en-US/CustomSpoke_AddPhysical.xml b/en-US/CustomSpoke_AddPhysical.xml
index 84c8cf7..56ef81e 100644
--- a/en-US/CustomSpoke_AddPhysical.xml
+++ b/en-US/CustomSpoke_AddPhysical.xml
@@ -30,7 +30,7 @@
</para>
<note>
<para>
- Some partitions have no mount points. When creating a swap partition, use a mount point of <literal>swap</literal> for BIOS Boot, use <literal>biosboot</literal>, and for an EFI System Partition, use <literal>efi</literal>. This will configure the partition with the correct settings.
+ Some partitions have no mount points. When creating a swap partition, use a mount point of <literal>swap</literal>; for BIOS Boot, use <literal>biosboot</literal>; and for an EFI System Partition, use <literal>efi</literal>. This will configure the partition with the correct settings.
</para>
</note>
</step>
9 years, 6 months