Bug 1065503

Summary: There is an extra line after the step numbers in section 5.2 on the labeling on each step
Product: Red Hat OpenStack Reporter: Liz <lsurette>
Component: doc-Getting_Started_GuideAssignee: Bruce Reeler <breeler>
Status: CLOSED DUPLICATE QA Contact: ecs-bugs
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.0CC: breeler, rlandman, sclark, sradvan, yeylon
Target Milestone: ---Keywords: Documentation
Target Release: 5.0 (RHEL 7)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-18 03:20:38 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:
Bug Depends On:    
Bug Blocks: 1099570    
Attachments:
Description Flags
Current state none

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 ***