Bug 1378002

Summary:	Please fix a typo: "documention" → "documentation"
Product:	[Fedora] Fedora	Reporter:	Rafal Luzynski <digitalfreak>
Component:	devhelp	Assignee:	Matthew Barnes <mbarnes>
Status:	CLOSED NEXTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	debarshir, mbarnes
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-21 11:18:10 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Rafal Luzynski 2016-09-21 09:42:16 UTC

Description of problem:

A typo in the package summary: "documention" I guess should be "documentation".

Version-Release number of selected component (if applicable):

All currently supported versions, this bug has been introduced somewhere between Fedora 10 and 11, devhelp 0.21-3. I mark Fedora version as rawhide in this bug report although I'd rather mark all versions (Bugzilla does not support it). Also I guess it exists in other Fedora-like distros (RHEL, CentOS, etc.)

How reproducible:

Always

Steps to Reproduce:
1. If you have devhelp installed:

    rpm -qi devhelp

2. Otherwise:

    dnf info devhelp

3. Optionally prepend with LANG=C to make sure the output is in English

Actual results:

Output says: "Summary     : API documention browser"

Expected results:

Output should say: "Summary     : API documentation browser"

Additional info:

Even this component description here in this Bugzilla says "documention" instead of "documentation". :-)

http://pkgs.fedoraproject.org/cgit/rpms/devhelp.git/commit/devhelp.spec?id=10b5075

Comment 1 Debarshi Ray 2016-09-21 11:18:10 UTC

Thanks for noticing, Rafal! I have fixed it in the f25 and master branches. It seems a bit trivial to bother users with an update, so the fix will be picked up when we do the next build from those branches.