Bug 1065503 - There is an extra line after the step numbers in section 5.2 on the labeling on each step
Summary: There is an extra line after the step numbers in section 5.2 on the labeling ...
Keywords:
Status: CLOSED DUPLICATE of bug 1052826
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: doc-Getting_Started_Guide
Version: 4.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 5.0 (RHEL 7)
Assignee: Bruce Reeler
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks: RHELOSP-RHCI
TreeView+ depends on / blocked
 
Reported: 2014-02-14 19:41 UTC by Liz
Modified: 2014-10-30 22:29 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-18 03:20:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Current state (84.03 KB, image/png)
2014-02-14 19:41 UTC, Liz
no flags Details

Description Liz 2014-02-14 19:41:02 UTC
Description of problem:
There is an extra line after the step numbers in section 5.2 on the labeling on each step

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

How reproducible:
Always

Steps to Reproduce:
1. Navigate to section 5.2 of Getting Started Guide: http://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/4/html-single/Getting_Started_Guide/index.html#sect-Running_PackStack_Interactively
2.
3.

Actual results:
There is an extra line after the step numbers in section 5.2 on the labeling on each step

Expected results:
The step number and action should be on the same line.

Additional info:

Comment 1 Liz 2014-02-14 19:41:32 UTC
Created attachment 863403 [details]
Current state

Comment 3 Bruce Reeler 2014-02-18 03:20:38 UTC
This appears to be a problem with the way documents are displayed on the portal. It does not occur in locally built docs.

This is a duplicate of bug BZ1052826, so closing this bug as a duplicate.

*** This bug has been marked as a duplicate of bug 1052826 ***


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