RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 801068 - Spelling inconsistencies in Installation Guide
Summary: Spelling inconsistencies in Installation Guide
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Installation_Guide
Version: 6.2
Hardware: powerpc
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Jack Reed
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-07 15:39 UTC by Kwan Lowe
Modified: 2013-06-17 05:43 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-25 23:35:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Kwan Lowe 2012-03-07 15:39:21 UTC
Description of problem:

"Disk" and "disc" spellings are inconsistent on the page and throughout the document.  I know this is definitely a niggle but each time I see it it jumps out. I understand there are differences between optical vs magnetic media, but this is not the case here:

  13.2.2. Preparing a driver disc
  You can create a driver update disc on CD or DVD.
  13.2.2.1. Creating a driver update disk on CD or DVD

I.e., the "driver update disc" and "driver update disk" here refer to the same thing. 

Version-Release number of selected component (if applicable):
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/sect-Preparing_a_driver_update_disk-ppc.html

How reproducible:
N/A

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 Jack Reed 2012-07-27 01:22:31 UTC
Thanks for reporting this. I've corrected the discrepancy you identified between 13.2.2 and 13.2.2.1.

I searched the rest of the document and found a few other instances that needed to be corrected in the same vein. 

However, sections 6.3 and 6.4 use 'disk' for two reasons that I've determined are valid if not ideal. Firstly, anaconda and the screenshots provided refer to 'driver disk', and secondly, 'disk' in this context refers collectively to all media, not just optical disks, which would necessitate a change to 'disc' (including explicitly in 6.3.3: "Insert the driver update disk that you created on CD, DVD, or USB flash drive").

There are also erroneous references to a 'Windows installation disk' in section 39.2. However, the instances are so numerous that it would cause a lot of translation work for a section that is not pertinent to most installations.

Comment 6 Jack Reed 2013-02-25 23:35:47 UTC
This bug has been verified and implemented for 6.4, so I am changing the status to CLOSED CURRENTRELEASE.


Note You need to log in before you can comment on or make changes to this bug.