Part II
-------

When you refer to "the JBoss HTTP Connector mod_cluster", either use parenthetical commas or parentheses.

23) 4. Overview
reduced configuration --> reduced-configuration
utilizing --> using, it is not "using efficiently" it is just using it lol

24) 4.1 Key Features
"makes intelligent decisions on" --> makes intelligent decisions about

25) 4.2. Components – Proxy Server
Shared Memory Manager (Module?) – the rest of the modules listed have Module after their names. There are varying methods of capitalizing these in the section; please review for consistency. (Recommend removing Module from the last three modules and not capitalizing 'module'.)

26) 4.2 Components
Difference between "Proxy Server" and "Worker node components" both in capitalization and in the level of detail in the titles; please coordinate.

27) 4.2 Components
life cycle events --> life-cycle events according to our Word Usage Guide
(also occurs elsewhere in the document, do grep or rpl)

28) 5. Install Proxy Server Components
JBoss HTTP Connector mod-cluster <-- mod_cluster is used elsewhere, review for consistency

29) 5.1.1. mod_manager.so
"uses this location for generated keys" <-- uses this location to store generated keys, perhaps,to avoid for-for confusion

30) 5.1.1. mod_manager.so
Are there any limits on Maxcontext, Maxnode, Maxhost, Maxsessionid parameters?

31) 5.1.1. mod_manager.so
images/mod_status.png <--could stand to go inside a <figure> tag with a title, since it is all white it just kinda makes the spacing in the document look weird.

32) 5.1.2. mod_proxy_cluster.so
Again, keep an eye on case in your module names.
"to change load balancing behaviour" --> load-balancing

33) 5.1.3. mod_advertise.so
case in module names
"If port is not specified, the default port specified is 23364." --> the default port used, not specified

34) 5.2 Install Proxy Server Components
"on a JBoss Enterprise Web Server." <-- on a server instance, or on JBoss etc. not on a JBoss etc.

35) 5.2 Install Proxy Server Components
"The Native components are Operating System and processor architecture specific." --> The native components are specific to particular operating systems and processor architectures. (Either that or you need to hyphenate in a complicated way.)
Also, check caps on Native Components.

36) Task: Install Proxy Server Components
"Edit the JBoss Enterprise Web Server Apache configuration file" --> Edit the [Apache] configuration file in your JBEWS instance: JBOSS_EWS_DIST/httpd/conf/httpd.conf
Instruction for commenting out the line could be clearer, too.
(Question for the devs: is there anything the mod_proxy_balancer module is compatible with, and if not, why is it here?)

37) 6. Configure Basic Proxy Server
"to configure a JBoss Enterprise Web Server" --> again, a JBEWS instance, or just JBEWS.
Also, "JBoss HTTP connector mod_cluster" is poorly marked up and capitalized in the opening here.

38) IMPORTANT: Task: Configure a Proxy Server Listener
Step 2 XML syntax highlighting is broken.

39) Task: Configure a Proxy Server Listener
Step 2, "Where IP_ADDRESS and PORT_NUMBER are the values from the Listen directive." --> s/are/match

40) IMPORTANT: Task: Configure a Proxy Server Listener
Step 3 last paragraph seems to contradict the final sentence in 6.1. Basic Proxy Configuration Overview "Server Advertisement" formalpara.

41) Task: Install and Configure a JBoss Enterprise Application Platform Worker Node
Inconsistent markup of jvmRoute attribute

42) Task: Install and Configure a JBoss Enterprise Application Platform Worker Node – Step 5
"For Linux users" is not followed by advice for any other user.

43) Task: Install and Configure a JBoss Enterprise Application Platform Worker Node – Important Box in Step 5
"JBoss Clustering relies on the UDP (User Datagram Protocol) multi-casting provided by jGroups." <-- multi-casting is elsewhere written as "multicast"; pick one and stick with it

44) Task: Install and Configure a JBoss Enterprise Application Platform Worker Node – Important Box in Step 5
Inconsistent indentation of commands in the screen tag
Also, there seem to be two save operations in that set of commands... not sure those are both supposed to be there

45) Task: Install and Configure a JBoss Enterprise Web Server Worker Node
Appendix B, Java Properties Reference is only mentioned in the EWS worker note config section, but the opening of this Appendix suggests that it refers to JBEAP, not JBEWS. Which is it? And should this appear in the previous task's prerequisites as well?

46) 8. Further Server Configuration feels like a bit of a "misc" section. Can this content go elsewhere?

47) Task: Configure Application Platform Worker Node with Static Proxy List
comma separated --> comma-separated

48) 9.2 Clustered Node Operation
"The JBoss HTTP Connector can operate in non-clustered or clustered mode." --> in either clustered or non-clustered mode

49) IMPORTANT: 9.2 Clustered Node Operation
Does not include details on configuring clustered/non-clustered operation.

50) 10. Load Balancing Demonstration
jboss-eap-5.1/mod_cluster/demo directory.
Only in 5.1? I imagine this will need to be edited in future; may as well make it multi-version compliant now.

51) 10. Load Balancing Demonstration
I think QE likes us to avoid letting applications possess things (load-demo.war's)

52) 10. Load Balancing Demonstration
"Load-demo app" <-- decide how you will refer to the app and use it consistently; avoid swapping between this and load-demo.war
Similarly, decide whether to refer to it as the Demonstration or the Demo

53) 10.1 Set up the Demonstration
Step 2 Note – text and admonition weight (note vs important) should match the admonition in the previous section, if this note is here at all.

54) 10.1 Set up the Demonstration
Step 3 - just prefix the step name with "Tomcat 6 only" or something, remove the admonition

55) 10.1 Set up the Demonstration
Step 3 - "<web-app>element," <-- missing space, and element not marked up as I would expect
Also, is it actually "appending" (that is, is </web-app> the last thing in the file before you add this)?

56) Task: Configure Client Control Tab Fields
"...to learn the values you must supply in the Client Control tab of the Load Balancing Demonstration." <-- 'complete this task to learn' is a vague task goal; what does the task actually accomplish?
I would recommend making Step 2 "Supply values for <required fields> and, optionally, <optional fields>." Move your list of references outside the task – either beforehand with "the demo client requires a number of values, defined here" or after with "the fields in step two expect values as defined in the following list".

57) Task: Interact with the Demonstration
Task Prerequesites <-- differs from the straight "Prerequisites" in all other sections, and is misspelled

58) Task: Interact with the Demonstration
I'm not sure "experiment" should be a task/procedure.
Additionally, screenshots couldn't go amiss.