svn commit: r1786504 - /jmeter/trunk/xdocs/usermanual/properties_reference.xml

[fs...@apache.org]

Author: fschumacher
Date: Sat Mar 11 10:36:12 2017
New Revision: 1786504

URL: http://svn.apache.org/viewvc?rev=1786504&view=rev
Log:
Try to be consistent with upper/lower case and correct a typo of an anchor.

Modified:
    jmeter/trunk/xdocs/usermanual/properties_reference.xml

Modified: jmeter/trunk/xdocs/usermanual/properties_reference.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/properties_reference.xml?rev=1786504&r1=1786503&r2=1786504&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/properties_reference.xml (original)
+++ jmeter/trunk/xdocs/usermanual/properties_reference.xml Sat Mar 11 10:36:12 2017
@@ -142,7 +142,7 @@ The <code>system.properties</code> file
     <note>
         Mac apparently looks better with the System LAF set through
         <source>jmeter.laf.mac=System</source>
-        Failing that, the JMeter default laf can be defined through:
+        Failing that, the JMeter default LAF can be defined through:
         <source>jmeter.laf=System</source>
         If none of the above <code>jmeter.laf</code> properties are defined, JMeter uses the <code>CrossPlatform</code> LAF.
         This is because the <code>CrossPlatform</code> LAF generally looks better than the <code>System</code> LAF.
@@ -289,9 +289,9 @@ gui.quick_9=ViewResultsFullVisualizer
 JMETER-SERVER</source>
     On Unix:
     <source>SERVER_PORT=1234 jmeter-server</source>
-    On the windows client:
+    On the Windows client:
     <source>set remote_hosts=<em>server</em>:1234</source>
-    On the unix client:
+    On the Unix client:
     <source>export remote_hosts=<em>server</em>:1234</source>
     Defaults to: <code>1099</code>
 </property>
@@ -324,7 +324,7 @@ JMETER-SERVER</source>
     Defaults to: <code>4000</code>
 </property>
 <property name="server.rmi.create">
-    From JMeter version 2.3.1, the jmeter server creates the RMI registry as part of the server process.<br/>
+    From JMeter version 2.3.1, the JMeter server creates the RMI registry as part of the server process.<br/>
     Set this property to <code>false</code>, to stop the server creating the RMI registry.<br/>
     Defaults to: <code>true</code>
 </property>
@@ -452,7 +452,7 @@ JMETER-SERVER</source>
 </properties>
 </section>
 
-<section name="&sect-num;.14 HTTP Cache Manager configuration" anchor="cache_maanger">
+<section name="&sect-num;.14 HTTP Cache Manager configuration" anchor="cache_manager">
 <properties>
 <property name="cacheable_methods">
     Space or comma separated list of methods that can be cached.<br/>
@@ -606,7 +606,7 @@ JMETER-SERVER</source>
 <property name="jmeter.save.saveservice.xml_pi">
     <note>N.B. The current implementation saves the values in XML as attributes, so the names must be valid XML names.</note>
     Versions of JMeter after 2.3.2 send the variable to all servers to ensure that the correct data is available at the client.<br/>
-    Optional xml processing instruction for line two of the file.<br/>
+    Optional XML processing instruction for line two of the file.<br/>
     Defaults to empty value
 </property>
 <property name="jmeter.save.saveservice.base_prefix">