From 822ae2b7e8c9a0963bbb1b3ea917dffb2442a30f Mon Sep 17 00:00:00 2001 From: Jason Yundt Date: Jul 25 2021 15:39:30 +0000 Subject: Replace "can not" with "cannot" "can not" is probably acceptable to most people, but "cannot" is probably acceptable to pretty much everyone and is more clear. See: https://english.stackexchange.com/questions/4510/why-is-cannot-spelled-as-one-word/ --- diff --git a/modules/install-guide/pages/_partials/install/CustomSpoke_AddLVM.adoc b/modules/install-guide/pages/_partials/install/CustomSpoke_AddLVM.adoc index e273ba1..ba05cd7 100644 --- a/modules/install-guide/pages/_partials/install/CustomSpoke_AddLVM.adoc +++ b/modules/install-guide/pages/_partials/install/CustomSpoke_AddLVM.adoc @@ -11,7 +11,7 @@ See xref:appendixes/Understanding_LVM.adoc#appe-lvm-overview[Understanding LVM] [WARNING] ==== -Some partition types - notably the `/boot` directory and the BIOS Boot and EFI partitions - can not be placed on logical volumes. Use standard physical volumes for them. See xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme] for more information. +Some partition types - notably the `/boot` directory and the BIOS Boot and EFI partitions - cannot be placed on logical volumes. Use standard physical volumes for them. See xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme] for more information. ==== diff --git a/modules/install-guide/pages/_partials/install/CustomSpoke_AddPhysical.adoc b/modules/install-guide/pages/_partials/install/CustomSpoke_AddPhysical.adoc index 0a47fcb..254d691 100644 --- a/modules/install-guide/pages/_partials/install/CustomSpoke_AddPhysical.adoc +++ b/modules/install-guide/pages/_partials/install/CustomSpoke_AddPhysical.adoc @@ -4,7 +4,7 @@ [[sect-installation-gui-manual-partitioning-standard]] ==== Creating Standard Partitions -_Standard partitions_ are the most common type of partition, with the widest support across operating systems. For example, Microsoft Windows uses exclusively physical partitions and can not natively work with LVM or Btrfs. Most {PRODUCT} partitioning setups will also require at least one standard partition for the `/boot` directory, and possibly also another standard partition with the BIOS Boot or EFI System file system to store the boot loader. +_Standard partitions_ are the most common type of partition, with the widest support across operating systems. For example, Microsoft Windows uses exclusively physical partitions and cannot natively work with LVM or Btrfs. Most {PRODUCT} partitioning setups will also require at least one standard partition for the `/boot` directory, and possibly also another standard partition with the BIOS Boot or EFI System file system to store the boot loader. See xref:appendixes/Disk_Partitions.adoc#appe-disk-partitions-overview[An Introduction to Disk Partitions] for additional information about the concepts behind physical partitions. diff --git a/modules/install-guide/pages/_partials/install/CustomSpoke_FileSystems.adoc b/modules/install-guide/pages/_partials/install/CustomSpoke_FileSystems.adoc index ec078bf..c25fe18 100644 --- a/modules/install-guide/pages/_partials/install/CustomSpoke_FileSystems.adoc +++ b/modules/install-guide/pages/_partials/install/CustomSpoke_FileSystems.adoc @@ -37,7 +37,7 @@ To configure software RAID, make sure that you have enough physical hard drives [IMPORTANT] ==== -Note that the size of an XFS file system can not currently be reduced without destroying and recreating the file system. If you expect that you will need to adjust the sizes of your file systems often, using XFS is not recommended, as it makes administration substantially more time-consuming. +Note that the size of an XFS file system cannot currently be reduced without destroying and recreating the file system. If you expect that you will need to adjust the sizes of your file systems often, using XFS is not recommended, as it makes administration substantially more time-consuming. ==== diff --git a/modules/install-guide/pages/_partials/install/CustomSpoke_PartitioningAdvice.adoc b/modules/install-guide/pages/_partials/install/CustomSpoke_PartitioningAdvice.adoc index a3535ce..ea85942 100644 --- a/modules/install-guide/pages/_partials/install/CustomSpoke_PartitioningAdvice.adoc +++ b/modules/install-guide/pages/_partials/install/CustomSpoke_PartitioningAdvice.adoc @@ -10,7 +10,7 @@ There is no best way to partition every system; the optimal setup depends on how * In some cases, creating separate mount points for directories other than `/`, `/boot` and `/home` may be useful; for example, on a server running a [application]*MySQL* database, having a separate mount point for `/var/lib/mysql` will allow you to preserve the database during a reinstallation without having to restore it from backup afterwards. However, having unnecessary separate mount points will make storage administration more difficult. -* Some special restrictions apply to certain directories with regards on which partitioning layouts can they be placed. Notably, the `/boot` directory must always be on a physical partition (not on an LVM volume or a Btrfs subvolume), and `/usr` can not be on a Btrfs subvolume. +* Some special restrictions apply to certain directories with regards on which partitioning layouts can they be placed. Notably, the `/boot` directory must always be on a physical partition (not on an LVM volume or a Btrfs subvolume), and `/usr` cannot be on a Btrfs subvolume. * If you are new to Linux, consider reviewing the [citetitle]_Linux Filesystem Hierarchy Standard_ at link:++https://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.html++[] for information about various system directories and their contents. @@ -28,7 +28,7 @@ This limitation only applies to `/usr` or `/var`, not to directories below them. * Consider leaving a portion of the space in an LVM volume group unallocated. This unallocated space gives you flexibility if your space requirements change but you do not wish to remove data from other volumes. You can also select the `Thin provisioning` device type for the partition to have the unused space handled automatically by the volume. -* The size of an `XFS` file system can not be reduced - if you need to make a partition or volume with this file system smaller, you must back up your data, destroy the file system, and create a new, smaller one in its place. Therefore, if you expect needing to manipulate your partitioning layout later, you should use the `ext4` file system instead. +* The size of an `XFS` file system cannot be reduced - if you need to make a partition or volume with this file system smaller, you must back up your data, destroy the file system, and create a new, smaller one in its place. Therefore, if you expect needing to manipulate your partitioning layout later, you should use the `ext4` file system instead. * Use Logical Volume Management (LVM) if you anticipate expanding your storage by adding more hard drives after the installation. With LVM, you can create physical volumes on the new drives, and then assign them to any volume group and logical volume as you see fit - for example, you can easily expand your system's `/home` (or any other directory residing on a logical volume). diff --git a/modules/install-guide/pages/_partials/install/CustomSpoke_RecommendedScheme.adoc b/modules/install-guide/pages/_partials/install/CustomSpoke_RecommendedScheme.adoc index 2c99ce3..ac1c18e 100644 --- a/modules/install-guide/pages/_partials/install/CustomSpoke_RecommendedScheme.adoc +++ b/modules/install-guide/pages/_partials/install/CustomSpoke_RecommendedScheme.adoc @@ -13,7 +13,7 @@ In most cases, at least the following mount points should always be created: If your system has a hardware RAID controller, be aware that some BIOS types do not support booting from it. In that case, the `/boot` partition must be created on a partition outside of the RAID array, such as on a separate hard drive. -Also note that the `/boot` directory can not be placed on a LVM logical volume. Use a standard partition. +Also note that the `/boot` directory cannot be placed on a LVM logical volume. Use a standard partition. ==== @@ -71,7 +71,7 @@ Systems with BIOS firmware and UEFI systems in BIOS compatibility mode::: If th [NOTE] ==== -You can force the installer to use GPT on disks smaller than 2 TB by using the [option]#inst.gpt# boot option as described in xref:advanced/Boot_Options.adoc#chap-anaconda-boot-options[Boot Options]. However, the opposite is not possible - you can not use MBR on disks larger than 2 TB. +You can force the installer to use GPT on disks smaller than 2 TB by using the [option]#inst.gpt# boot option as described in xref:advanced/Boot_Options.adoc#chap-anaconda-boot-options[Boot Options]. However, the opposite is not possible - you cannot use MBR on disks larger than 2 TB. ==== + @@ -84,7 +84,7 @@ UEFI-based systems require an _EFI System Partition_ at least 50 MB in size (rec [IMPORTANT] ==== -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. +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 cannot reside on an LVM volume or a Btrfs subvolume. Also note that if your system does not require any of these partitions, they will not be shown in the `File System` menu in mount point options. diff --git a/modules/install-guide/pages/_partials/install/DateTimeSpoke.adoc b/modules/install-guide/pages/_partials/install/DateTimeSpoke.adoc index 869e25c..6976717 100644 --- a/modules/install-guide/pages/_partials/install/DateTimeSpoke.adoc +++ b/modules/install-guide/pages/_partials/install/DateTimeSpoke.adoc @@ -17,7 +17,7 @@ You can also select a time zone relative to Greenwich Mean Time (GMT) without se [NOTE] ==== -The list of cities and regions comes from the Time Zone Database ([package]*tzdata*) public domain, which is maintained by the Internet Assigned Numbers Authority (IANA). The Fedora Project can not add cities or regions into this database. You can find more information at the link:++https://www.iana.org//time-zones++[IANA official website]. +The list of cities and regions comes from the Time Zone Database ([package]*tzdata*) public domain, which is maintained by the Internet Assigned Numbers Authority (IANA). The Fedora Project cannot add cities or regions into this database. You can find more information at the link:++https://www.iana.org//time-zones++[IANA official website]. ==== diff --git a/modules/install-guide/pages/_partials/install/LangSupportSpoke.adoc b/modules/install-guide/pages/_partials/install/LangSupportSpoke.adoc index 28ce703..5179e2d 100644 --- a/modules/install-guide/pages/_partials/install/LangSupportSpoke.adoc +++ b/modules/install-guide/pages/_partials/install/LangSupportSpoke.adoc @@ -4,7 +4,7 @@ [[sect-installation-gui-language-support]] === Language Support -The `Language Support` screen allows you to configure language settings for your system. The default language is determined by your selection in xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-welcome[Welcome Screen and Language Selection] and support for this language can not be removed. You can only add additional languages, which will be available on the installed system - not during the installation. +The `Language Support` screen allows you to configure language settings for your system. The default language is determined by your selection in xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-welcome[Welcome Screen and Language Selection] and support for this language cannot be removed. You can only add additional languages, which will be available on the installed system - not during the installation. If you want to change the default language, or the language used during the installation, you must reboot your system, start the installer again, and select a different language in xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-welcome[Welcome Screen and Language Selection]. diff --git a/modules/install-guide/pages/_partials/install/StorageSpoke.adoc b/modules/install-guide/pages/_partials/install/StorageSpoke.adoc index 164b1a0..bfaad53 100644 --- a/modules/install-guide/pages/_partials/install/StorageSpoke.adoc +++ b/modules/install-guide/pages/_partials/install/StorageSpoke.adoc @@ -22,7 +22,7 @@ In the top part of the screen, all locally available storage devices (SATA, IDE If you need to configure additional local storage devices, select `Refresh` on the lower-right corner. Follow the instructions in the dialog that opens. All detected disks, including any new ones, will be displayed in the `Local Standard Disks` section. -The `Specialized & Network Disks` section below shows advanced network storage (such as iSCSI and FCoE disks) currently configured. When you first open this screen, no such devices will be displayed because they can not be automatically detected; to search for network storage devices, press `Add a disk` button and proceed with xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-installation-destination[Installation Destination - Specialized & Network Disks]. Any network storage you configure will then show up in the `Specialized & Network Disks` the same way local disks are shown above. +The `Specialized & Network Disks` section below shows advanced network storage (such as iSCSI and FCoE disks) currently configured. When you first open this screen, no such devices will be displayed because they cannot be automatically detected; to search for network storage devices, press `Add a disk` button and proceed with xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-installation-destination[Installation Destination - Specialized & Network Disks]. Any network storage you configure will then show up in the `Specialized & Network Disks` the same way local disks are shown above. All storage devices which will be used to install {PRODUCT} have a black circle icon with a white check mark on them. Disks not marked by this icon will not be used during the installation - they will be ignored if you choose automatic partitioning, and they will not be available in manual partitioning. diff --git a/modules/install-guide/pages/_partials/install/UserSpoke.adoc b/modules/install-guide/pages/_partials/install/UserSpoke.adoc index 7c8fee8..02a5ff6 100644 --- a/modules/install-guide/pages/_partials/install/UserSpoke.adoc +++ b/modules/install-guide/pages/_partials/install/UserSpoke.adoc @@ -53,8 +53,8 @@ image::anaconda/UserSpoke_Advanced.png[Advanced settings for the new user accoun * The user's `Home directory` (`/home/pass:attributes[{blank}]_username_pass:attributes[{blank}]` by default). -* The user's ID (UID). The default value is 1000. UIDs 0-999 are reserved by the system so they can not be assigned to an user. +* The user's ID (UID). The default value is 1000. UIDs 0-999 are reserved by the system so they cannot be assigned to an user. -* The the group ID (GID) of the user's default group. The default group name will be the same as the user name, and its default GID is 1000. GIDs 0-999 are reserved by the system so they can not be assigned to an user's group. +* The the group ID (GID) of the user's default group. The default group name will be the same as the user name, and its default GID is 1000. GIDs 0-999 are reserved by the system so they cannot be assigned to an user's group. * The user's group membership. The user account you are creating will always have one default group membership (the user's default group with an ID set in the `Specify a group ID manually` field). In the `Group Membership` field, you can specify additional groups as a comma-separated list. Groups which do not already exist will be created; you can specify custom GIDs for them in parentheses. If you do not specify a custom GID for a new group, it will be assigned automatically. diff --git a/modules/install-guide/pages/advanced/Kickstart_Installations.adoc b/modules/install-guide/pages/advanced/Kickstart_Installations.adoc index 35e75ce..1076ebd 100644 --- a/modules/install-guide/pages/advanced/Kickstart_Installations.adoc +++ b/modules/install-guide/pages/advanced/Kickstart_Installations.adoc @@ -18,7 +18,7 @@ To use Kickstart, you must: . Create a Kickstart file. -. Create boot media or configure a network boot (PXE) server which will be used to begin the installation. Note that live media can not be used for Kickstart installations - use installation media that can boot directly into the installer, such as the standard or netinstall ISO image from the Server edition. +. Create boot media or configure a network boot (PXE) server which will be used to begin the installation. Note that live media cannot be used for Kickstart installations - use installation media that can boot directly into the installer, such as the standard or netinstall ISO image from the Server edition. . Make the Kickstart file available on removable media, a hard drive, or a network location. diff --git a/modules/install-guide/pages/appendixes/Kickstart_Syntax_Reference.adoc b/modules/install-guide/pages/appendixes/Kickstart_Syntax_Reference.adoc index bbf09b4..44600c7 100644 --- a/modules/install-guide/pages/appendixes/Kickstart_Syntax_Reference.adoc +++ b/modules/install-guide/pages/appendixes/Kickstart_Syntax_Reference.adoc @@ -39,7 +39,7 @@ While the general principles of Kickstart installations tend to stay the same, t $ [command]#ksverdiff -f F{PREVVER} -t F{PRODVER}# ---- -The [option]#-f# option specifies the release to start the comparison with, and the [option]#-t# option to specify the release to end with. For additional information, see the `ksverdiff(1)` 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* on Fedora{nbsp}{PREVVER} can not display changes in Fedora{nbsp}{PRODVER}. +The [option]#-f# option specifies the release to start the comparison with, and the [option]#-t# option to specify the release to end with. For additional information, see the `ksverdiff(1)` man page. Also note that you cannot use this to display changes in a release that is newer than your system - the version of [package]*pykickstart* on Fedora{nbsp}{PREVVER} cannot display changes in Fedora{nbsp}{PRODVER}. Additionally, you can review the [citetitle]_Fedora{nbsp}{PRODVER} Release Notes_, available at link:++https://docs.fedoraproject.org/++[], for a list of changes. @@ -663,14 +663,14 @@ For the swap sizes assigned by these commands, see the section describing swap i [option]#--grow#:: Grow the volume to fill available space (if any), or up to the limit set by the [option]#--maxsize=# option. -[option]#--size=#:: The size of the logical volume in megabytes. This option can not be used together with the [option]#--percent=# option. +[option]#--size=#:: The size of the logical volume in megabytes. This option cannot be used together with the [option]#--percent=# option. -[option]#--percent=#:: Specify the amount by which to grow the logical volume, as a percentage of the free space in the volume group after any statically-sized logical volumes are taken into account. This option can not be used together with the [option]#--size=# and [option]#--grow# options. +[option]#--percent=#:: Specify the amount by which to grow the logical volume, as a percentage of the free space in the volume group after any statically-sized logical volumes are taken into account. This option cannot be used together with the [option]#--size=# and [option]#--grow# options. + [IMPORTANT] ==== -When creating a new logical volume, you must either specify its size statically using the [option]#--size=# option, or as a percentage of remaining free space using the [option]#--percent=# option. You can not use both of these options on the same logical volume. +When creating a new logical volume, you must either specify its size statically using the [option]#--size=# option, or as a percentage of remaining free space using the [option]#--percent=# option. You cannot use both of these options on the same logical volume. ==== @@ -681,7 +681,7 @@ When creating a new logical volume, you must either specify its size statically [IMPORTANT] ==== -This option can only be used for partitions which result in a file system such as the `/boot` partition and `swap` space. It can not be used to create partitionsm, LVM physical or logical volumes or RAID members. +This option can only be used for partitions which result in a file system such as the `/boot` partition and `swap` space. It cannot be used to create partitionsm, LVM physical or logical volumes or RAID members. ==== @@ -896,7 +896,7 @@ Never specify multipath devices by device names like `mpatha`. Device names such [IMPORTANT] ==== -This option can only be used for partitions which result in a file system such as the `/boot` partition and `swap` space. It can not be used to create partitionsm, LVM physical or logical volumes or RAID members. +This option can only be used for partitions which result in a file system such as the `/boot` partition and `swap` space. It cannot be used to create partitionsm, LVM physical or logical volumes or RAID members. ==== @@ -1025,7 +1025,7 @@ Automatically create partitions required by your hardware platform. These includ [NOTE] ==== -This command can not be used together with [command]#autopart#, because [command]#autopart# does the same and creates other partitions or logical volumes such as `/` and `swap` on top. In contrast with [command]#autopart#, this command only creates platform-specific partitions and leaves the rest of the drive empty, allowing you to create a custom layout. +This command cannot be used together with [command]#autopart#, because [command]#autopart# does the same and creates other partitions or logical volumes such as `/` and `swap` on top. In contrast with [command]#autopart#, this command only creates platform-specific partitions and leaves the rest of the drive empty, allowing you to create a custom layout. ==== @@ -1859,7 +1859,7 @@ The syntax for this command is unusual because it is an add-on rather than a bui [application]*Kdump* is a kernel crash dumping mechanism that allows you to save the contents of the system's memory for later analysis. It relies on [application]*kexec*, which can be used to start a Linux kernel from the context of another kernel without rebooting the system and preserve the contents of the first kernel memory that would otherwise be lost. -In case of a system crash, [application]*kexec* starts a second kernel (a _capture kernel_). This capture kernel resides in a reserved part of the system memory that is inaccessible to the main kernel. [application]*Kdump* then captures the contents of the crashed kernel's memory (a _crash dump_) and saves it to a specified location. This location can not be configured using Kickstart; it must be specified after the installation by editing the `/etc/kdump.conf` configuration file. +In case of a system crash, [application]*kexec* starts a second kernel (a _capture kernel_). This capture kernel resides in a reserved part of the system memory that is inaccessible to the main kernel. [application]*Kdump* then captures the contents of the crashed kernel's memory (a _crash dump_) and saves it to a specified location. This location cannot be configured using Kickstart; it must be specified after the installation by editing the `/etc/kdump.conf` configuration file. Available options are: diff --git a/modules/install-guide/pages/install/Booting_the_Installation.adoc b/modules/install-guide/pages/install/Booting_the_Installation.adoc index 6c4f645..ba7e8fc 100644 --- a/modules/install-guide/pages/install/Booting_the_Installation.adoc +++ b/modules/install-guide/pages/install/Booting_the_Installation.adoc @@ -15,7 +15,7 @@ After you have made a bootable USB flash drive or a CD or DVD using the steps de [WARNING] ==== -There are no separate media provided for BIOS and UEFI systems; all of them can boot from the same ISO image. However, once you install {PRODUCT}, you can not switch between UEFI and BIOS. The system must run on the same firmware it was installed on; if you, for example, perform the installation on an UEFI system in UEFI mode, and then switch it to BIOS compatibility mode, {PRODUCT} will no longer boot and will require a reinstallation. +There are no separate media provided for BIOS and UEFI systems; all of them can boot from the same ISO image. However, once you install {PRODUCT}, you cannot switch between UEFI and BIOS. The system must run on the same firmware it was installed on; if you, for example, perform the installation on an UEFI system in UEFI mode, and then switch it to BIOS compatibility mode, {PRODUCT} will no longer boot and will require a reinstallation. ==== diff --git a/modules/install-guide/pages/install/Installing_Using_Anaconda.adoc b/modules/install-guide/pages/install/Installing_Using_Anaconda.adoc index f6d1897..f651bea 100644 --- a/modules/install-guide/pages/install/Installing_Using_Anaconda.adoc +++ b/modules/install-guide/pages/install/Installing_Using_Anaconda.adoc @@ -20,7 +20,7 @@ The {PRODUCT} installer, [application]*Anaconda*, is different from most other o In [application]*Anaconda* you are only required to select your language and locale first, and then you are presented with a central screen, where you can configure most aspects of the installation in any order you like. This does not apply to all parts of the installation process, however - for example, when installing from a network location, you must configure the network before you can select which packages to install. -Some screens will be automatically configured depending on your hardware and the type of media you used to start the installation. You can still change the detected settings in any screen. Screens which have not been automatically configured, and therefore require your attention before you begin the installation, are marked by an exclamation mark. You can not start the actual installation process before you finish configuring these settings. +Some screens will be automatically configured depending on your hardware and the type of media you used to start the installation. You can still change the detected settings in any screen. Screens which have not been automatically configured, and therefore require your attention before you begin the installation, are marked by an exclamation mark. You cannot start the actual installation process before you finish configuring these settings. Additional differences appear in certain screens; notably the custom partitioning process is very different from other Linux distributions. These differences are described in each screen's subsection. @@ -95,7 +95,7 @@ Limits of interactive text mode installation include: * The installer will always use the English language and the US English keyboard layout. You can configure your language and keyboard settings, but these settings will only apply to the installed system, not to the installation. -* You can not configure any advanced storage methods (LVM, software RAID, FCoE, zFCP and iSCSI). +* You cannot configure any advanced storage methods (LVM, software RAID, FCoE, zFCP and iSCSI). * It is not possible to configure custom partitioning; you must use one of the automatic partitioning settings. You also cannot configure where the boot loader will be installed. diff --git a/modules/install-guide/pages/install/Preparing_for_Installation.adoc b/modules/install-guide/pages/install/Preparing_for_Installation.adoc index dfed033..048235e 100644 --- a/modules/install-guide/pages/install/Preparing_for_Installation.adoc +++ b/modules/install-guide/pages/install/Preparing_for_Installation.adoc @@ -288,7 +288,7 @@ target device. If you made a mistake, you could lose important data. ==== === Creating a Boot CD or DVD -In addition to creating a bootable USB flash drive, you can also use the provided ISO images to create bootable optical media (a CD or DVD). This approach may be necessary when installing {PRODUCT} on an older system which can not boot from USB. +In addition to creating a bootable USB flash drive, you can also use the provided ISO images to create bootable optical media (a CD or DVD). This approach may be necessary when installing {PRODUCT} on an older system which cannot boot from USB. [NOTE] ====