#77 Fix misspellings
Merged 2 years ago by pbokoc. Opened 3 years ago by rffontenelle.
Unknown source fix-typos  into  master

@@ -35,7 +35,7 @@

  +

  Use a live image to install your favorite system, test Fedora on new hardware, troubleshoot, or share with friends.

  

- DVD Image::  DVD images boot directly into the installation enviroment, and allow you to choose from a variety of packages that are provided with it. In Fedora 21, the DVD option is only available in the *Fedora Server* Edition.

+ DVD Image::  DVD images boot directly into the installation environment, and allow you to choose from a variety of packages that are provided with it. In Fedora 21, the DVD option is only available in the *Fedora Server* Edition.

  +

  Use the Fedora Server DVD image when you want customized Fedora Server installations using an offline installation source.

  

@@ -21,7 +21,7 @@

  

  image::anaconda/CustomSpoke.png[The Manual Partitioning screen. At this point, no partitioning has been configured. The left column shows an option to automatically create a pre-defined layout. An existing Linux system has been detected also and is displayed below the automatic configuration selection. The right side of the screen shows available options for the currently selected mount point.]

  

- When you first open the `Manual Partitioning` screen, the column on the left side will display all previously existing partitions on all drives which you selected as installation targers in xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination]. If none of the selected drives contain any existing partitions, then a message informing you that no mount points currently exist will appear.

+ When you first open the `Manual Partitioning` screen, the column on the left side will display all previously existing partitions on all drives which you selected as installation targets in xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination]. If none of the selected drives contain any existing partitions, then a message informing you that no mount points currently exist will appear.

  

  Here, you can choose a partitioning scheme such as `LVM` or `BTRFS` and click the `Click here to create them automatically` to prompt the installer to create a basic partitioning layout; this layout follows the guidelines described in xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme]. The created layout is a basic layout where partition/volume sizes are determined automatically based on the total amount of available space.

  

@@ -6,7 +6,7 @@

  

  _Btrfs_ 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 supports snapshots that can be used for backup, replication, and namespace isolation (e.g. for use in containers).

  

- Creating a Btrfs layout is somewhat similar to LVM (described in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-lvm[Creating a Logical Volume Managament (LVM) Layout]) with slightly different terminology. A Btrfs _volume_ is the equivalent of an LVM volume group, and a Btrfs _subvolume_ is similar to a LVM logical volume. An important difference to note is how [application]*Anaconda* 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.

+ Creating a Btrfs layout is somewhat similar to LVM (described in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-lvm[Creating a Logical Volume Management (LVM) Layout]) with slightly different terminology. A Btrfs _volume_ is the equivalent of an LVM volume group, and a Btrfs _subvolume_ is similar to a LVM logical volume. An important difference to note is how [application]*Anaconda* 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.

  

  [WARNING]

  ====

@@ -2,7 +2,7 @@

  :experimental:

  

  [[sect-installation-gui-manual-partitioning-lvm]]

- ==== Creating a Logical Volume Managament (LVM) Layout

+ ==== Creating a Logical Volume Management (LVM) Layout

  

  _Logical Volume Management_ (LVM) presents a simple logical view of underlying physical storage space, such as hard drives or LUNs. Partitions on physical storage are represented as _physical volumes_ that can be grouped together into _volume groups_. Each volume group can be divided into multiple _logical volumes_, each of which is analogous to a standard disk partition. Therefore, LVM logical volumes function as partitions which can span multiple physical disks.

  

@@ -8,13 +8,13 @@

  

  To select a device type or a file system of a partition or a logical volume, select it in the list in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning[Manual Partitioning] and select a `Device Type` and a `File System` from their respective drop-down menus on the right side of the screen. Then, click `Update Settings` and repeat this process for all mount points you want to modify.

  

- To configure software RAID, make sure that you have enough physical hard drives selected as installation targets (the number of separate drives required for each type of RAID is noted in its description). Then, choose a RAID level when creating or modifying a Btrfs volume or LVM volume group, or select `Software RAID` as the device type to create software RAID with standard partitions. For detailed instructions, see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-btrfs[Creating a Btrfs Layout], xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-lvm[Creating a Logical Volume Managament (LVM) Layout], and xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-swraid[Creating Software RAID] as needed.

+ To configure software RAID, make sure that you have enough physical hard drives selected as installation targets (the number of separate drives required for each type of RAID is noted in its description). Then, choose a RAID level when creating or modifying a Btrfs volume or LVM volume group, or select `Software RAID` as the device type to create software RAID with standard partitions. For detailed instructions, see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-btrfs[Creating a Btrfs Layout], xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-lvm[Creating a Logical Volume Management (LVM) Layout], and xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-swraid[Creating Software RAID] as needed.

  

  .Device Types

  

  * `Standard Partition` - A standard partition can contain a file system or swap space. Standard partitions are most commonly used for `/boot` and the BIOS Boot and EFI System partitions. LVM logical volumes or Btrfs subvolumes are recommended for most other uses. See xref:appendixes/Disk_Partitions.adoc#appe-disk-partitions-overview[An Introduction to Disk Partitions] for additional information about the concepts behind physical partitions.

  

- * `LVM` - Choosing `LVM` as the `Device Type` creates an LVM logical volume and a volume group to contain it (unless one already exists, in which case the new volume is assigned to the existing group). LVM can improve performance when using physical disks and allows you to use multiple disks for a single mount point. For information on how to create a logical volume, see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-lvm[Creating a Logical Volume Managament (LVM) Layout]. Also see xref:appendixes/Understanding_LVM.adoc#appe-lvm-overview[Understanding LVM] for some additional information about LVM in general.

+ * `LVM` - Choosing `LVM` as the `Device Type` creates an LVM logical volume and a volume group to contain it (unless one already exists, in which case the new volume is assigned to the existing group). LVM can improve performance when using physical disks and allows you to use multiple disks for a single mount point. For information on how to create a logical volume, see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-lvm[Creating a Logical Volume Management (LVM) Layout]. Also see xref:appendixes/Understanding_LVM.adoc#appe-lvm-overview[Understanding LVM] for some additional information about LVM in general.

  

  * `LVM Thin Provisioning` - Using thin provisioning, you can manage a storage pool of free space, known as a _thin pool_, which can be allocated to an arbitrary number of devices when needed by applications. The thin pool can be expanded dynamically when needed for cost-effective allocation of storage space.

  

@@ -4,14 +4,14 @@

  [[sect-installation-gui-manual-partitioning-swraid]]

  ==== Creating Software RAID

  

- _Redundant arrays of independent disks_ (RAIDs) are constructed from multiple storage devices that are arranged to provide increased performance and, in some configurations, greater fault tolerance. See xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-filesystems[Device, File System and RAID Types] a description of different kinds of RAIDs.

+ _Redundant arrays of independent disks_ (RAIDs) are constructed from multiple storage devices that are arranged to provide increased performance and, in some configurations, greater fault tolerance. See xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-filesystems[Device, File System and RAID Types] for a description of different kinds of RAIDs.

  

  A RAID device is created in one step, and disks are added or removed as necessary. One RAID partition per physical disk is allowed for each device, so the number of disks available to the installation program determines which levels of RAID device are available to you. For example, if your system has two hard drives, the installation program will not allow you to create a RAID10 device, which requires 4 separate partitions.

  

  [IMPORTANT]

  ====

  

- This section only explains how to create software RAID with standard (physical) partitions. However, you can also configure LVM volume groups and Btrfs volumes to use RAID and place their logical volumes or Btrfs subvolumes on top of this RAID array. See xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-lvm[Creating a Logical Volume Managament (LVM) Layout] and xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-btrfs[Creating a Btrfs Layout] for instructions on creating RAID in LVM and Btrfs.

+ This section only explains how to create software RAID with standard (physical) partitions. However, you can also configure LVM volume groups and Btrfs volumes to use RAID and place their logical volumes or Btrfs subvolumes on top of this RAID array. See xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-lvm[Creating a Logical Volume Management (LVM) Layout] and xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-btrfs[Creating a Btrfs Layout] for instructions on creating RAID in LVM and Btrfs.

  

  ====

  
@@ -52,4 +52,4 @@

  

  . Configure other settings specific to the partition - its `Mount Point`, `Desired Capacity`, and `File System`. Press `Update Settings` to apply any changes to the configuration.

  

- Repeat this procedure for any additional standard partitions with software RAID you want to create. 

\ No newline at end of file

+ Repeat this procedure for any additional standard partitions with software RAID you want to create.

@@ -54,6 +54,6 @@

  

  . Select one or more nodes you want to log in to by marking or unmarking the check box next to each node discovered on the target. Below the list, select again the type of authentication you want to use; you can also select the `Use the credentials from discovery` option if the CHAP/reverse CHAP user name and password you used to discover the target are also valid for logging in to it.

  +

- After selecting all nodes you want to use, click `Log In` to initiate an iSCSI session. [application]*Anaconda* will attempt to log in to all selected nodes. If the login process is succesful, the `Add iSCSI Storage Target` dialog will close, and all nodes you have configured will now be shown in the list of network disks in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-installation-destination[Installation Destination - Specialized & Network Disks].

+ After selecting all nodes you want to use, click `Log In` to initiate an iSCSI session. [application]*Anaconda* will attempt to log in to all selected nodes. If the login process is successful, the `Add iSCSI Storage Target` dialog will close, and all nodes you have configured will now be shown in the list of network disks in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-installation-destination[Installation Destination - Specialized & Network Disks].

  

  You can repeat this procedure to discover additional iSCSI targets, or to add more nodes from a previously configured target. However, note that once you click the `Start Discovery` button for the first time, you will not be able to change the `iSCSI Initiator Name`. If you made an error when configuring the initiator name, you must restart the installation.

@@ -246,7 +246,7 @@

  

  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.

  

- Fedora Infrastructure maintains instructions for a configuring a local mirror at link:++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_, available at link:++https://docs.fedoraproject.org/++[], to configure `httpd`.

+ Fedora Infrastructure maintains instructions for configuring a local mirror at link:++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_, available at link:++https://docs.fedoraproject.org/++[], to configure `httpd`.

  

  [[sect-install-server-cobbler]]

  == Advanced network installations with Cobbler

@@ -319,7 +319,7 @@

  

  [option]#pbkdf-memory=#::  Sets the memory cost for PBKDF. Only relevant if [option]#--encrypted# is also specified. See the `cryptsetup(8)` man page for more information.

  

- [option]#pbkdf-time=#::  Sets the number of miliseconds to spend with PBKDF passphrase processing. Only relevant if [option]#--encrypted# is also specified. See information about the [option]#--iter-time# option in the `cryptsetup(8)` man page for more information.

+ [option]#pbkdf-time=#::  Sets the number of milliseconds to spend with PBKDF passphrase processing. Only relevant if [option]#--encrypted# is also specified. See information about the [option]#--iter-time# option in the `cryptsetup(8)` man page for more information.

  +

  Only one of [option]#--pbkdf-time=# or [option]#--pbkdf-iterations=# can be specified at the same time.

  
@@ -815,7 +815,7 @@

  

  [option]#pbkdf-memory=#::  Sets the memory cost for PBKDF. Only relevant if [option]#--encrypted# is also specified. See the `cryptsetup(8)` man page for more information.

  

- [option]#pbkdf-time=#::  Sets the number of miliseconds to spend with PBKDF passphrase processing. Only relevant if [option]#--encrypted# is also specified. See information about the [option]#--iter-time# option in the `cryptsetup(8)` man page for more information.

+ [option]#pbkdf-time=#::  Sets the number of milliseconds to spend with PBKDF passphrase processing. Only relevant if [option]#--encrypted# is also specified. See information about the [option]#--iter-time# option in the `cryptsetup(8)` man page for more information.

  +

  Only one of [option]#--pbkdf-time=# or [option]#--pbkdf-iterations=# can be specified at the same time.

  
@@ -1003,7 +1003,7 @@

  

  [option]#pbkdf-memory=#::  Sets the memory cost for PBKDF. Only relevant if [option]#--encrypted# is also specified. See the `cryptsetup(8)` man page for more information.

  

- [option]#pbkdf-time=#::  Sets the number of miliseconds to spend with PBKDF passphrase processing. Only relevant if [option]#--encrypted# is also specified. See information about the [option]#--iter-time# option in the `cryptsetup(8)` man page for more information.

+ [option]#pbkdf-time=#::  Sets the number of milliseconds to spend with PBKDF passphrase processing. Only relevant if [option]#--encrypted# is also specified. See information about the [option]#--iter-time# option in the `cryptsetup(8)` man page for more information.

  +

  Only one of [option]#--pbkdf-time=# or [option]#--pbkdf-iterations=# can be specified at the same time.

  
@@ -1067,7 +1067,7 @@

  

  [option]#pbkdf-memory=#::  Sets the memory cost for PBKDF. Only relevant if [option]#--encrypted# is also specified. See the `cryptsetup(8)` man page for more information.

  

- [option]#pbkdf-time=#::  Sets the number of miliseconds to spend with PBKDF passphrase processing. Only relevant if [option]#--encrypted# is also specified. See information about the [option]#--iter-time# option in the `cryptsetup(8)` man page for more information.

+ [option]#pbkdf-time=#::  Sets the number of milliseconds to spend with PBKDF passphrase processing. Only relevant if [option]#--encrypted# is also specified. See information about the [option]#--iter-time# option in the `cryptsetup(8)` man page for more information.

  +

  Only one of [option]#--pbkdf-time=# or [option]#--pbkdf-iterations=# can be specified at the same time.

  
@@ -1323,7 +1323,7 @@

  +

  Note that this option is independent of how the `--device` is specified.

  +

- Currently only the value `mac` is suported. `--bindto=mac` will bind  the connection to MAC address of the device (`HWADDR` value in the `ifcfg` file).

+ Currently only the value `mac` is supported. `--bindto=mac` will bind  the connection to MAC address of the device (`HWADDR` value in the `ifcfg` file).

  +

  For example:

  +