Bug 1047468 - typo in section 8.3
Summary: typo in section 8.3
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Docs API Guide
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Dan Macpherson
QA Contact: Dan Macpherson
URL:
Whiteboard:
Depends On:
Blocks: sat-docs
TreeView+ depends on / blocked
 
Reported: 2013-12-31 09:12 UTC by Sharuzzaman Ahmat Raslan
Modified: 2015-09-16 02:20 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-16 02:20:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
missing closing parenthesis (101.10 KB, image/png)
2013-12-31 09:12 UTC, Sharuzzaman Ahmat Raslan 		no flags Details
View All

Description Sharuzzaman Ahmat Raslan 2013-12-31 09:12:30 UTC 
Created attachment 843693 [details]
missing closing parenthesis

Description of problem:
On page 52 of Red Hat Satellite 5.6 API Overview, section 8.3, there is a typo, where the closing parenthesis is missing.

The word is "string - The access value (one of the following: public, private, or protected."



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

How reproducible:
Always

Steps to Reproduce:
1. Open PDF of Red Hat Satellite 5.6 API Overview
2. Go to page 52, section 8.3
3. Parenthesis is missing in the Return section

Actual results:
Parenthesis missing

Expected results:
Closing parenthesis should be there

Additional info:
Screenshot attached
Comment 1 Dan Macpherson 2014-01-21 15:19:38 UTC 
This bug can be worked on early during the planning stages for Satellite 5.7.
Comment 2 Dan Macpherson 2014-01-24 00:40:44 UTC 
Revised in topic 27103:
string - The access value, which is one of the following: <literal>public</literal>, <literal>private</literal>, or <literal>protected</literal>.
Comment 4 Dan Macpherson 2015-09-16 02:20:24 UTC 
This change should be implemented int he 5.7 documentation. Please feel free to reopen if further changes are required.
Note You need to log in before you can comment on or make changes to this bug.