Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1679849

Summary:	Typo in typographic conventions section
Product:	[Retired] Fedora Documentation	Reporter:	Conor Kovats <conor.kovats>
Component:	documentation-guide	Assignee:	Petr Bokoc <pbokoc>
Status:	CLOSED EOL	QA Contact:	Fedora Docs QA <docs-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	devel	CC:	jhradile, pkovar, sparks, stickster, zach
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-22 09:29:15 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 Conor Kovats 2019-02-22 02:49:37 UTC

Document URL: https://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Documentation_Guide/pref-documentation-guide-Preface.html

Section Number and Name: 1.1 Typographic Conventions

Describe the issue: In the sentence "Key combinations can be distinguished from keycaps by the hyphen connecting each part of a key combination", I think "hyphen" is a typo and should be "plus"

Suggestions for improvement: change "hyphen" in the issue sentence to "plus"

Additional information: Context below with the given examples

Key combinations can be distinguished from keycaps by the hyphen connecting each part of a key combination. For example:

Press Enter to execute the command.
Press Ctrl+Alt+F2 to switch to the first virtual terminal. Press Ctrl+Alt+F1 to return to your X-Windows session.

Comment 1 Petr Bokoc 2019-02-22 09:29:15 UTC

Hello, thank you for the report. However I'm afraid I'll have to close it. The guide you see online is no longer being maintained, it's only kept up for historical purposes. On top of that, the publishing tool used to publish this guide (publican) is also no longer being maintained, so even if we fixed this, we'd have no way to publish the fix.

Sorry for the inconvenience; sometime in the future I'm going to go through BZ bugs for no longer maintained components and then shut down those components as well so people don't spend time opening bug reports that won't go anywhere, but that's going to take time.

Petr