Bug 1247427 - The sentence "The NAKACK2 protocol is a successor to the NAKACK2 protocol" should be corrected
The sentence "The NAKACK2 protocol is a successor to the NAKACK2 protocol" sh...
Status: CLOSED CURRENTRELEASE
Product: JBoss Data Grid 6
Classification: JBoss
Component: Documentation (Show other bugs)
6.5.0
Unspecified Unspecified
unspecified Severity urgent
: CR1
: 6.5.1
Assigned To: Christian Huffman
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-07-27 21:28 EDT by Takuro Nagamoto
Modified: 2015-09-16 16:04 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Build Name: 12532, Administration and Configuration Guide-6.5 Build Date: 23-07-2015 06:03:08 Topic ID: 42157-741802 [Specified]
Last Closed: 2015-09-16 16:04:36 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Takuro Nagamoto 2015-07-27 21:28:01 EDT
Title: Supported JGroups Protocols

Describe the issue:
I am translating this doc and encountered the following sentence in the table A.1 "Supported JGroups Protocols" in Appendix A, which I think should be corrected.

"The NAKACK2 protocol is a successor to the NAKACK2 protocol and was introduced in JGroups 3.1. "


Suggestions for improvement:
"The NAKACK2 protocol is a successor to the NAKACK2 protocol" should be like "The NAKACK2 protocol is a successor to the NAKACK1 protocol". The second "NAKACK2" should be the version lower than NAKACK2.

Additional information:
Comment 3 Christian Huffman 2015-09-16 16:04:36 EDT
This sentence has been corrected; a link to the appropriate section on the Customer Portal is below:

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Data_Grid/6.5/html-single/Administration_and_Configuration_Guide/index.html#Supported_JGroups_Protocols

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