Fix typographical errors in installation section #195
No reviewers
Labels
No labels
in progress
in progress
meeting
need info
ongoing work project
on hold
pending activity
release test
user documentation
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
server/user-documentation!195
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "brettweir/user-documentation:proofread-installation"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This pull request makes the following changes to the installation section of the documentation:
I tried to take a light-touch approach here, but happy to update the PR if any changes are too aggressive.
Wow so many fixed typos 😃 Good job.
My other comments are a bit nitpicky, so take em or leave em!
@ -29,3 +29,3 @@=== Minimum requirementsThe question of the minimum requirements is always raised, even though it is obvious to anybody that it depends entirely on the deployment plan.The minimum requirements are often questioned, though they depend on the deployment plan.I think the phrasing here sounds odd. A bit like the minimum requirements aren't really trustworthy or agreed.
I would change this to read:
Minimum requirements are guidelines, but depend on the deployment plan.
@ -119,3 +119,3 @@=== Create a bootable installation mediumA installation on bare metal requires to transfer the installation file to a bootable media, mostly an USB memory stick. There are several option:An installation on bare metal requires transferring the installation file to bootable media, typically a USB memory stick. There are several options.While not really a typographical comment, it is not true that installation on bare metal actually requires this - because network boot is also often an option. So I would soften this to state:
An installation on bare metal might require transferring the installation file to bootable media, typically a USB memory stick. There are several options.
@ -129,3 +129,3 @@====No further steps are required besides the disks already contain partitions and file systems. In this case you may want to select the option "Free up space by removing or shrinking existing partitions". Then select _Done_ in the upper bar and you are 'done'.No further steps are required beyond the disks that already contain partitions and file systems. In this case you may want to select the option "Free up space by removing or shrinking existing partitions". Then select _Done_ in the upper bar and you are 'done'.No further steps are required beyond the disks that already contain partitions and file systems.
This doesn't make grammatical sense to me. Maybe:
No further steps are required beyond configuring disks that might already contain partitions and file systems.
@ -145,3 +145,3 @@By clicking onto the + sign you can add partitions according to your storage concept.Fedora uses a GPT partitioning scheme. Thus, on a BIOSboot system you must add a BIOSboot partion, preferrably as the first one. On a UEFIboot system you have to add a EFI system partition, preferrably as the first one. If you forget it, Anaconda will remind you.Fedora uses a GPT partitioning scheme. Thus, on a BIOSboot system you must add a BIOSboot partition, preferably as the first one. On a UEFIboot system you have to add an EFI system partition, preferably as the first one. If you forget it, Anaconda will remind you.Are BIOSboot and UEFIboot recognized terms? These seem odd to me, but were pre-existing, so maybe okay.
Due to the interchangeability of BIOS and UEFI in common parlance, I would use:
Thus on a system using legacy BIOS to boot...
On a system using UEFI to boot...
I also thought these were odd. Created server/tickets#207