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 601785 - Grammatical errors in "Provide additional details" screen
Summary: Grammatical errors in "Provide additional details" screen
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: abrt
Version: 6.0
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Jiri Moskovcak
QA Contact: Michal Nowak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-08 15:41 UTC by Marc Milgram
Modified: 2015-02-01 22:52 UTC (History)
9 users (show)

Fixed In Version: abrt-1.1.5-1.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-10 19:33:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Marc Milgram 2010-06-08 15:41:18 UTC
Description of problem:
2 grammatical nits:
  1. "Are there any comment you'd like to share with the software maintainers?"
     "Are" and "comment" should either both be plural or both be singular.
  2. "Tip: Your comments are not private. Please monitor what you say accordingly"
     There is a period in the middle of the line.  There should probably be one
     at the end of the line as well.  It looks like there is only one space
     after the period.  There should be 2 spaces after the period.

Version-Release number of selected component (if applicable):
abrt-1.1.4-1.el6.x86_64


How reproducible:
100%

Steps to Reproduce:
1. Report a bug with abrt
2. Get to the "Provide additional details" screen

  
Actual results:
Line reads, "Are there any comment you'd like to share with the software maintainers?"
Another line reads, "Tip: Your comments are not private. Please monitor what you say accordingly"

Expected results:
Lines should read:
"Are there any comments you'd like to share with the software maintainers?"
and
"Tip: Your comments are not private.  Please monitor what you say accordingly."

Additional info:

Comment 1 RHEL Program Management 2010-06-08 15:53:34 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 4 releng-rhel@redhat.com 2010-11-10 19:33:07 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.


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