Bug 1583863

Summary: Release Notes Fedora 28
Product: [Fedora] Fedora Documentation Reporter: Leslie Satenstein <lsatenstein>
Component: technical-notesAssignee: John J. McDonough <wb8rcr>
Status: CLOSED EOL QA Contact: Fedora Docs QA <docs-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: develCC: wb8rcr, zach
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-07 15:30:24 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:
Attachments:
Description Flags
Fedora 28 Release Notes none

Description Leslie Satenstein 2018-05-29 23:11:21 UTC 
Created attachment 1445585 [details]
Fedora 28 Release Notes

Description of problem:

I copy / pasted the Fedora Release Notes from https://docs.fedoraproject.org/

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

Fedora 28

I used LibreOffice writer to edit the guide.

I marked spelling errors, grammar errors, and sentence construction.

I also raised comments about different sections of the release guide. Vague or incorrect information

I would like « anyone » to review the attached document and accept/reject the changes

Zoom to each markup. Use the right mouse button on the error to acknowledge or reject the change I made or error I detected. You may add your own changes too. 

My intention, if my changes to the guide are marked up, is to back post the changes to the asciidoc files, raising a PR (whatever a PR is). 
 
Please email me your approvals/rejects using the same document.
Or respond with your attacement as a new comment

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

Feedback confirming my findings

Additional info:
Comment 1 Petr Bokoc 2019-11-07 15:30:24 UTC 
I'm closing this bug as part of a Bugzilla cleanup effort. The most likely reason is that the bug has been opened either against a component we no longer publish, or against Release Notes for an EOL release.