Bug 1295608 - [Docs] [Deploying OpenShift] Check Syntax and Links
Summary: [Docs] [Deploying OpenShift] Check Syntax and Links
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Documentation
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.5.2
Assignee: Shikha
QA Contact: Dayle Parker
URL:
Whiteboard:
Depends On:
Blocks: 1289516
TreeView+ depends on / blocked
 
Reported: 2016-01-05 02:27 UTC by Andrew Dahms
Modified: 2016-04-28 00:32 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-07 06:27:17 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Andrew Dahms 2016-01-05 02:27:55 UTC
The Deploying OpenShift Enterprise with Red Hat CloudForms guide must be reviewed to standardize use of AsciiDoc syntax and to update links to other guides in the Red Hat CloudForms documentation suite.

This includes the following items -

* Remove any procedure titles
* Remove any 'Result::' blocks
* Use 'btn:[Button Name]' for buttons
* Use +Text+ for labels and replaceables
* Ensure delimiters (e.g. ======) are six characters long
* Update links to other guides in the suite to use the correct title and
  section name

Comment 1 Andrew Dahms 2016-01-05 02:47:53 UTC
Assigning to Shikha for review.

Comment 2 Shikha 2016-01-06 15:22:24 UTC
Hi Andrew,
I have reviewed and updated the syntax and links for Deploying OpenShift guide.
Dayle, please review the merge request.
https://gitlab.cee.redhat.com/rhci-documentation/docs-Red_Hat_CloudForms/merge_requests/107

Regards,
Shikha

Comment 3 Dayle Parker 2016-01-06 23:58:12 UTC
The changes look good to me - thanks Shikha!

https://gitlab.cee.redhat.com/rhci-documentation/docs-Red_Hat_CloudForms/merge_requests/107 has been merged.

Comment 4 Andrew Dahms 2016-01-07 06:27:17 UTC
This content is now live on the Customer Portal.

Closing.


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