-
Notifications
You must be signed in to change notification settings - Fork 21
Merge all updates from dev to master for 6.0 release #447
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
* Updated copyright year * Updated versions on links to style guides * Removed statement about providing DocBook guidance
…link Fixes #409 and other required repairs.
…date daobrien/416 chris wright update
Applied various fixes for 6.0
* First batch of updates * Remaining enhancements
* First changes for Enhancements 2 * Adding next batch of enhancements * Added further enhancements * Implemented fixes from review
* Adding snippet guidance Part 1 * Further enhancements to 6.0 * Fixes to implement feedback * Further fixes * Update to implement Fernando's feedback * Adding addressing of issue 399 to the scope * Implemented review comments
* Added audience, new in this release, fix for 'like' entry * Minor fixes
Revert addition of audience section
A small subsection on when and when not to use captions and callouts.
Addresses #424 Add info on using captions.
…dianet Fixes #356. Removes big RH logo from centre of page.
Added example for 'unset'
update preface.xml to add in audience file and resolve issue #408
* Final update to release notes for 6.0 * Updated publication month
en-US/Language.xml
Outdated
| <entry> To create another administrator account, click <guimenuitem>New</guimenuitem> on the <guimenuitem>File</guimenuitem> menu. <emphasis>OR</emphasis> To set privileges for another administrator, click <guimenuitem>New</guimenuitem> on the <guimenuitem>File</guimenuitem> menu. </entry> | ||
| <entry> | ||
| <para> | ||
| To create another administrator account, click <guimenuitem>New</guimenuitem> on the <guimenuitem>File</guimenuitem> menu. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@julian-cable This wording seems a little odd to me. Wouldn't we normally say "..., click File --->New..."?
I don't think this is critical, but it might be worth adding an example of this wording in a future edition of the style guide.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree and updated in #449.
en-US/Language.xml
Outdated
| Use the utility to run activities and to save your settings (if the utility does both functions). | ||
| </para> | ||
| <para> | ||
| <emphasis>Or:</emphasis> Use the utility to run activities, and then when you are done, save your settings (if the process consists of two separate steps, of which the utility does only one). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| <emphasis>Or:</emphasis> Use the utility to run activities, and then when you are done, save your settings (if the process consists of two separate steps, of which the utility does only one). | |
| <emphasis>Or:</emphasis> Use the utility to run activities, and then when you are done, save your settings (if the process consists of two separate steps, of which the utility does only one). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again, we might make an issue against a future edition. The phrase "when you are done" bit here is extraneous. "...activities, and then save..."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree and updated in #449.
nmuller66
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@julian-cable I left a couple of comments that we might want to add as issues for the next release. I don't think they are critical enough to circle back around during this release process. Please review and resolve or create issues if you agree, then I think we can proceed with the merge.
No description provided.