Bug 1371293 - Table 3.1 Router Configuration Parameters Format Is Wrong Architecture Document
Summary: Table 3.1 Router Configuration Parameters Format Is Wrong Architecture Document
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.2.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: brice
QA Contact: Vikram Goyal
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-29 20:12 UTC by Dave Sullivan
Modified: 2016-09-22 01:15 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-22 01:15:56 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Dave Sullivan 2016-08-29 20:12:31 UTC
Description of problem:

Table 3.1 Router Configuration Parameters Format Is Wrong Architecture Document

Looks like there should only be two columns in the table bu there are three.

And it line wraps as well.

https://access.redhat.com/documentation/en/openshift-enterprise/version-3.2/architecture/


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:


Document URL: 

https://access.redhat.com/documentation/en/openshift-enterprise/version-3.2/architecture/

Section Number and Name: 

Table 3.1

Describe the issue: 

See above

Suggestions for improvement: 

Additional information:

Comment 2 brice 2016-08-30 00:04:10 UTC
PR submitted for this:

https://github.com/openshift/openshift-docs/pull/2757

Simple fix. Putting it onto peer review.

Comment 3 openshift-github-bot 2016-08-30 04:43:30 UTC
Commit pushed to master at https://github.com/openshift/openshift-docs

https://github.com/openshift/openshift-docs/commit/ea872afbad55c4fbe9b54ffe8b53dbbcbea8eedb
Merge pull request #2757 from bfallonf/bz1371293

Bug 1371293 Fixed table markup


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