Bug 172483 - Word "course" should be "coarse", Section 1 "What is SELinux"
Summary: Word "course" should be "coarse", Section 1 "What is SELinux"
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: rhel-sg
Version: 4.5
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
: ---
Assignee: Don Domingo
QA Contact:
URL: https://www.redhat.com/docs/manuals/e...
Whiteboard:
Depends On:
Blocks: 149551
TreeView+ depends on / blocked
 
Reported: 2005-11-05 03:07 UTC by Leam
Modified: 2010-08-25 23:16 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-01-15 01:27:51 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Leam 2005-11-05 03:07:02 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.0.3705; .NET CLR 1.1.4322)

Description of problem:
Change word "course" to "coarse" in #1, "What is SELinux", paragraph starting "Under DAC, there are...", page i.

Version-Release number of selected component (if applicable):
rhel-selg(EN)-4-HTML-RHI (2005-02-15-T16:20)

How reproducible:
Always

Steps to Reproduce:
1. Read.
2.
3.
  

Actual Results:  Saw the problem.

Expected Results:  Different word.

Additional info:

rhel-selg(EN)-4-HTML-RHI (2005-02-15-T16:20)
Comment 1 Karsten Wade 2005-11-05 09:52:56 UTC 
Thanks for the catch!  Probably too much reliance on the spell checker, eh?

I'm not sure that this content will be updated, but if it is, I'll be sure to
make this fix.

Now set to block bug #149551, the tracking bug for this guide.
Comment 2 Mike Behm 2006-02-06 13:13:57 UTC 
Made change as requested.
Comment 3 Karsten Wade 2006-03-30 19:17:12 UTC 
No longer a member of the documentation group, reassgning to group manager to
resolve.
Comment 4 Michael Hideo 2007-06-06 05:03:56 UTC 
Adding ecs-dev-list for wider coverage
Comment 5 Michael Hideo 2007-10-23 02:48:16 UTC 
Removing automation notification
Note You need to log in before you can comment on or make changes to this bug.