jmeter-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From milam...@apache.org
Subject svn commit: r1694900 - in /jmeter/trunk/xdocs: ./ extending/ usermanual/
Date Sun, 09 Aug 2015 19:18:37 GMT
Author: milamber
Date: Sun Aug  9 19:18:36 2015
New Revision: 1694900

URL: http://svn.apache.org/r1694900
Log:
Fix some typo (found by hunspell tool)

Modified:
    jmeter/trunk/xdocs/changes_history.xml
    jmeter/trunk/xdocs/extending.xml
    jmeter/trunk/xdocs/extending/JMeter Extension Scenario.xml
    jmeter/trunk/xdocs/usermanual/best-practices.xml
    jmeter/trunk/xdocs/usermanual/build-jms-topic-test-plan.xml
    jmeter/trunk/xdocs/usermanual/component_reference.xml
    jmeter/trunk/xdocs/usermanual/functions.xml
    jmeter/trunk/xdocs/usermanual/get-started.xml
    jmeter/trunk/xdocs/usermanual/glossary.xml
    jmeter/trunk/xdocs/usermanual/ldapops_tutor.xml
    jmeter/trunk/xdocs/usermanual/test_plan.xml

Modified: jmeter/trunk/xdocs/changes_history.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/changes_history.xml?rev=1694900&r1=1694899&r2=1694900&view=diff
==============================================================================
--- jmeter/trunk/xdocs/changes_history.xml (original)
+++ jmeter/trunk/xdocs/changes_history.xml Sun Aug  9 19:18:36 2015
@@ -143,8 +143,8 @@ Documentations have been refreshed parti
 </p>
 
 <ch_title>Toolbar</ch_title>
-<p>JMeter's toolbar has been refreshed for some icons (start, toogle, etc.). Three
sizes are now avialable for the icons: 22x22, 32x32 and 48x48.<br>
-The property to define your prefered size is:
+<p>JMeter's toolbar has been refreshed for some icons (start, toogle, etc.). Three
sizes are now available for the icons: 22x22, 32x32 and 48x48.<br>
+The property to define your preferred size is:
 <pre>jmeter.toolbar.icons.size=value</pre>
 with the value 22x22 (default size), 32x32 or 48x48.</br></p>
 <p>The toolbar with 22x22 pixels icons
@@ -459,7 +459,7 @@ Only one instance of the section will be
 <figure width="989" height="406" image="changes/2.12/13_webdav.png"></figure>
 
 <ch_title>Better handling of embedded resources</ch_title>
-<p>When download embedded resources is checked, JMeter now uses User Agent header to
download or not resources embedded within conditionnal comments as per <a href="http://msdn.microsoft.com/en-us/library/ms537512%28v=vs.85%29.aspx"
target="_blank">About conditional comments</a>.</p>
+<p>When download embedded resources is checked, JMeter now uses User Agent header to
download or not resources embedded within conditional comments as per <a href="http://msdn.microsoft.com/en-us/library/ms537512%28v=vs.85%29.aspx"
target="_blank">About conditional comments</a>.</p>
 
 <ch_title>Ability to customize Cache Manager (Browser cache simulation) handling of
cached resources</ch_title>
 <p>You can now configure the behaviour of JMeter when a resource is found in Cache,
this can be controlled with <i>cache_manager.cached_resource_mode</i> property</p>
@@ -1316,7 +1316,7 @@ with <i>Body Data</i>, see also the Temp
 
 <li>
 In previous versions, <b>IncludeController</b> could run Test Elements located
inside a <b>Thread Group</b>, this behaviour (<i>which was not documented</i>)

-ould result in weird behaviour, it has been removed in this version (see <bugzilla>55464</bugzilla>).

+could result in weird behaviour, it has been removed in this version (see <bugzilla>55464</bugzilla>).

 The correct way to include Test Elements is to use <b>Test Fragment</b> as stated
in documentation of <b>Include Controller</b>.
 </li>
 
@@ -2062,7 +2062,7 @@ Furthermore it doesn't put anymore in Ca
 </p>
 
 <p>
-A major change has occured on JSR223 Test Elements, previously variables set up before script
execution where stored in ScriptEngineManager which was created once per execution, 
+A major change has occurred on JSR223 Test Elements, previously variables set up before script
execution where stored in ScriptEngineManager which was created once per execution, 
 now ScriptEngineManager is a singleton shared by all JSR223 elements and only ScriptEngine
is created once per execution, variables set up before script execution are now stored 
 in Bindings created on each execution, see <bugzilla>53365</bugzilla>.
 </p>
@@ -2203,7 +2203,7 @@ Cookie Manager has now the default HC3.1
 <li><bugzilla>53418</bugzilla> - New Option "Delay thread creation until
needed" that will create and start threads when needed instead of creating them on Test startup</li>
 <li><bugzilla>42245</bugzilla> - Show clear passwords in HTTP Authorization
Manager</li>
 <li><bugzilla>53616</bugzilla> - Display 'Apache JMeter' title in app title
bar in Gnome 3</li>
-<li><bugzilla>53759</bugzilla> - ClientJMeterEngine perfoms unnecessary
traverse using SearchByClass(TestListener)</li>
+<li><bugzilla>53759</bugzilla> - ClientJMeterEngine performs unnecessary
traverse using SearchByClass(TestListener)</li>
 <li><bugzilla>52601</bugzilla> - CTRL + F for the new Find feature</li>
 <li><bugzilla>53796</bugzilla> - TestCompiler uses static Set which can
grow huge</li>
 <li><bugzilla>53673</bugzilla> - Add JMeter version in the jmx file</li>
@@ -2294,7 +2294,7 @@ Cookie Manager has now the default HC3.1
 </p>
 
 <h3>New Visual Indicator of number of ERROR/FATAL messages in logs</h3>
-<p>Indicator shows number of ERROR/FATAL messsages in logs, it can be clicked to toggle
Log Viewer panel
+<p>Indicator shows number of ERROR/FATAL messages in logs, it can be clicked to toggle
Log Viewer panel
 <figure width="815" height="633" image="changes/2.7/16_log_errors_counter.png"></figure>
 </p>
 
@@ -3927,7 +3927,7 @@ JMeter now removes extraneous leading ".
 "Counter" is now shown as a Configuration element.
 </li>
 <li><bugzilla>41608</bugzilla> - misleading warning log message removed</li>
-<li><bugzilla>46359</bugzilla> - BSF JavaScript Preprocessor cannot access
sampler variable on first interation (Implement temporary work-round for BSF-22)</li>
+<li><bugzilla>46359</bugzilla> - BSF JavaScript Preprocessor cannot access
sampler variable on first iteration (Implement temporary work-round for BSF-22)</li>
 <li><bugzilla>46407</bugzilla> - BSF elements do not load script files,
attempt to interpret filename as script</li>
 <li>Better handling of Exceptions during test shutdown</li>
 <li>Fix potential thread safety issue in JMeterThread class</li>
@@ -3974,7 +3974,7 @@ JMeter now removes extraneous leading ".
 <li>Add BSF Listener element</li>
 <li><bugzilla>47176</bugzilla> -  Monitor Results : improve load status
graphic</li>
 <li><bugzilla>40045</bugzilla> - Allow Results monitor to select a specific
connector</li>
-<li>Read XML JTL files more efficiently - pass samples to visualisers as they are read,
rather than saving them all and then processing them</li>
+<li>Read XML JTL files more efficiently - pass samples to visualizers as they are read,
rather than saving them all and then processing them</li>
 </ul>
 
 <h3>Assertions, Config, Pre- &amp; Post-Processors</h3>
@@ -4574,7 +4574,7 @@ Some of the main enhancements are:
 </p>
 <ul>
 <li>Htmlparser 2.0 now used for parsing</li>
-<li>HTTP Authorisation now supports domain and realm</li>
+<li>HTTP Authorization now supports domain and realm</li>
 <li>HttpClient options can be specified via httpclient.parameters file</li>
 <li>HttpClient now behaves the same as Java Http for SSL certificates</li>
 <li>HTTP Mirror Server to allow local testing of HTTP samplers</li>
@@ -4626,7 +4626,7 @@ The original behaviour can be restored b
 jmeterthread.reversePostProcessors=true
 </p>
 <p>
-The HTTP Authorisation Manager now has extra columns for domain and realm, 
+The HTTP Authorization Manager now has extra columns for domain and realm, 
 so the temporary work-round of using '\' and '@' in the username to delimit the domain and
realm
 has been removed.
 </p>
@@ -4671,7 +4671,7 @@ It was unused so far, and used the only
 
 <h4>New functionality/improvements:</h4>
 <ul>
-<li>Add Domain and Realm support to HTTP Authorisation Manager</li>
+<li>Add Domain and Realm support to HTTP Authorization Manager</li>
 <li>HttpClient now behaves the same as the JDK http sampler for invalid certificates
etc</li>
 <li>Added httpclient.parameters.file to allow HttpClient parameters to be defined</li>
 <li><bugzilla>33964</bugzilla> - Http Requests can send a file as the entire
post body if name/type are omitted</li>
@@ -5143,7 +5143,7 @@ The XSL stylesheets also now accept eith
 <h4>New functionality:</h4>
 <ul>
 <li>While Controller</li>
-<li>BeanShell intilisation scripts</li>
+<li>BeanShell initialisation scripts</li>
 <li>Result Saver can optionally save failed results only</li>
 <li>Display as HTML has option not to download frames and images etc</li>
 <li>Multiple Tree elements can now be enabled/disabled/copied/pasted at once</li>
@@ -5391,7 +5391,7 @@ test engine code.</li>
     <li>Fixed bug that caused cookies not to be read if header name case not as expected.</li>

     <li>Clone entries before sending to sampler - prevents relocations from messing
up 
         information across threads</li> 
-    <li>Minor bug fix to convenience dialog for adding paramters to test sample.  
+    <li>Minor bug fix to convenience dialog for adding parameters to test sample. 

         Bug prevented entries in dialog from appearing in test sample.</li> 
     <li>Added xerces.jar to distribution</li> 
     <li>Added junit.jar to distribution and created a few tests.</li> 

Modified: jmeter/trunk/xdocs/extending.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/extending.xml?rev=1694900&r1=1694899&r2=1694900&view=diff
==============================================================================
--- jmeter/trunk/xdocs/extending.xml (original)
+++ jmeter/trunk/xdocs/extending.xml Sun Aug  9 19:18:36 2015
@@ -73,7 +73,7 @@ Timers provide a framework for delaying
 <dt><code>delay()</code> wait for a Timer specific amount of time</dt>
 <dd>JMeter calls this function prior to every sample.  The Timer should wait for a
period of time and then return.</dd>
 <dt><code>set()</code> prepare for sampling</dt>
-<dd>JMeter calls this function prior to the begining of a test session.  The timer
should initialize itself, read any values from its UI and prepare for operation.
+<dd>JMeter calls this function prior to the beginning of a test session.  The timer
should initialize itself, read any values from its UI and prepare for operation.
 </dd>
 </dl>
 </p>
@@ -84,7 +84,7 @@ The sampler controller is by far the mos
 <dl>
 <dt><code>start()</code></dt>
 <dd>
-JMeter calls this immediatly prior to starting a test.  It is most often use to disable the
SamplerController's GUI.
+JMeter calls this immediately prior to starting a test.  It is most often use to disable
the SamplerController's GUI.
 </dd>
 <dt><code>stop()</code></dt>
 <dd>

Modified: jmeter/trunk/xdocs/extending/JMeter Extension Scenario.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/extending/JMeter%20Extension%20Scenario.xml?rev=1694900&r1=1694899&r2=1694900&view=diff
==============================================================================
--- jmeter/trunk/xdocs/extending/JMeter Extension Scenario.xml (original)
+++ jmeter/trunk/xdocs/extending/JMeter Extension Scenario.xml Sun Aug  9 19:18:36 2015
@@ -27,7 +27,7 @@
 
 <section name="JMeter Extension Scenario">
 <p>The purpose of this tutorial is to
-describe the general steps involved in a JMeter extension scenerio. The
+describe the general steps involved in a JMeter extension scenario. The
 <a href="index.html">JMeter documentation</a> describes what must be done on
a microscopic level but does
 not provide an overall idea of the process. That is the intent of this brief
 article. The JMeter extension documentation should be consulted for details.</p>

Modified: jmeter/trunk/xdocs/usermanual/best-practices.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/best-practices.xml?rev=1694900&r1=1694899&r2=1694900&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/best-practices.xml (original)
+++ jmeter/trunk/xdocs/usermanual/best-practices.xml Sun Aug  9 19:18:36 2015
@@ -197,7 +197,7 @@ This is what you should see in the JMete
 Startup script running
 Startup script completed
 Httpd started on port: 9000
-Sessiond started on port: 9001
+Session started on port: 9001
 </source>
 <p>
 There is a sample script (<code>extras/remote.bsh</code>) you can use to test
the server.
@@ -274,11 +274,11 @@ Some long-running tests may cause the in
 <p>
 You can test BeanShell scripts outside JMeter by using the command-line interpreter:
 <source>
-$ java -cp bsh-xxx.jar[;other jars as needed] bsh.Interperter file.bsh [parameters]
+$ java -cp bsh-xxx.jar[;other jars as needed] bsh.Interpreter file.bsh [parameters]
 </source>
 or
 <source>
-$ java -cp bsh-xxx.jar bsh.Interperter
+$ java -cp bsh-xxx.jar bsh.Interpreter
 bsh% source("file.bsh");
 bsh% exit(); // or use EOF key (e.g. ^Z or ^D)
 </source>

Modified: jmeter/trunk/xdocs/usermanual/build-jms-topic-test-plan.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/build-jms-topic-test-plan.xml?rev=1694900&r1=1694899&r2=1694900&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/build-jms-topic-test-plan.xml (original)
+++ jmeter/trunk/xdocs/usermanual/build-jms-topic-test-plan.xml Sun Aug  9 19:18:36 2015
@@ -49,7 +49,7 @@ Topic messaging is generally used in cas
 consumed by multiple subscribers.  Queue messaging is generally used for transactions
 where the sender expects a response.  Messaging systems are quite different from
 normal HTTP requests. In HTTP, a single user sends a request and gets a response.
-Messaging system can work in sychronous and asynchronous mode.  A JMS sampler needs 
+Messaging system can work in synchronous and asynchronous mode.  A JMS sampler needs 
 the JMS implementation jar files; for example, from Apache ActiveMQ.  
 See <a href="#libraries_activemq">here</a> for the list of jars provided by ActiveMQ
3.0.</p>
 

Modified: jmeter/trunk/xdocs/usermanual/component_reference.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/component_reference.xml?rev=1694900&r1=1694899&r2=1694900&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/component_reference.xml (original)
+++ jmeter/trunk/xdocs/usermanual/component_reference.xml Sun Aug  9 19:18:36 2015
@@ -981,7 +981,7 @@ Webservice Soap Sampler assumes that emp
          <property name="Search Filter" required="Yes">searchfilter, must be specified
in LDAP syntax.</property>
          <property name="Scope" required="No">Use <code>0</code> for baseobject-,
<code>1</code> for onelevel- and <code>2</code> for a subtree search.
(Default=<code>0</code>)</property>
          <property name="Size Limit" required="No">Specify the maximum number of results
you want back from the server. (default=<code>0</code>, which means no limit.)
When the sampler hits the maximum number of results, it will fail with errorcode <code>4</code></property>
-         <property name="Time Limit" required="No">Specify the maximum amount of (cpu)time
(in miliseconds) that the server can spend on your search. Take care, this does not say anything
about the responsetime. (default is <code>0</code>, which means no limit)</property>
+         <property name="Time Limit" required="No">Specify the maximum amount of (cpu)time
(in milliseconds) that the server can spend on your search. Take care, this does not say anything
about the responsetime. (default is <code>0</code>, which means no limit)</property>
          <property name="Attributes" required="No">Specify the attributes you want
to have returned, separated by a semicolon. An empty field will return all attributes</property>
          <property name="Return object" required="No">Whether the object will be returned
(true) or not (false). Default=<code>false</code></property>
          <property name="Dereference aliases" required="No">If true, it will dereference
aliases, if false, it will not follow them (default=false)</property>
@@ -1139,7 +1139,7 @@ The <code>interrupt()</code> method can
     The return value (if not <code>null</code>) is stored as the sampler result.</property>
 </properties>
 <note>
-N.B. Each Sampler instance has its own BeanShell interpeter,
+N.B. Each Sampler instance has its own BeanShell interpreter,
 and Samplers are only called from a single thread
 </note><p>
 If the property "<code>beanshell.sampler.init</code>" is defined, it is passed
to the Interpreter
@@ -1992,7 +1992,7 @@ Relative paths are resolved against the
 <property name="Subject" required="">The e-mail message subject.</property>
 <property name="Suppress Subject Header" required="">If selected, the "<code>Subject:</code>"
header is omitted from the mail that is sent. 
 This is different from sending an empty "<code>Subject:</code>" header, though
some e-mail clients may display it identically.</property>
-<property name="Include timestamp in subject" required="">Includes the <code>System.currentTimemilis()</code>
in the subject line.</property>
+<property name="Include timestamp in subject" required="">Includes the <code>System.currentTimemillis()</code>
in the subject line.</property>
 <property name="Add Header" required="No">Additional headers can be defined using this
button.</property>
 <property name="Message" required="">The message body.</property>
 <property name="Send plain body (i.e. not multipart/mixed)">
@@ -3750,7 +3750,7 @@ restricted using server authentication.
 your browser to access a restricted page, and your browser displays a login dialog box. 
JMeter
 transmits the login information when it encounters this type of page.</p>
 <p>
-The Authorisation headers may not be shown in the Tree View Listener "<code>Request</code>"
tab.
+The Authorization headers may not be shown in the Tree View Listener "<code>Request</code>"
tab.
 The Java implementation does pre-emptive authentication, but it does not
 return the Authorization header when JMeter fetches the headers.
 The Commons HttpClient (3.1) implementation defaults to pre-emptive and the header will be
shown.
@@ -4312,7 +4312,7 @@ however the minimum and maximum values c
   <property name="Minimum Value" required="Yes">The minimum value (long) of the generated
random number.</property>
   <property name="Maximum Value" required="Yes">The maximum value (long) of the generated
random number.</property>
   <property name="Random Seed" required="No">The seed for the random number generator.
Default is the current time in milliseconds. 
-  If you use the same seed value with Per Thread set to true, you will get the same value
for earch Thread as per 
+  If you use the same seed value with Per Thread set to true, you will get the same value
for each Thread as per 
   <a href="http://docs.oracle.com/javase/6/docs/api/java/util/Random.html" >Random</a>
class.
   </property>
   <property name="Per Thread(User)?" required="Yes">If False, the generator is shared
between all threads in the thread group.
@@ -4840,7 +4840,7 @@ The script (or file) is processed using
 The script can check various aspects of the <a href="../api/org/apache/jmeter/samplers/SampleResult.html">SampleResult</a>.
 If an error is detected, the script should use AssertionResult.setFailureMessage("message")
and AssertionResult.setFailure(true).
 </p>
-<p>For futher details of all the methods available on each of the above variables,
please check the Javadoc</p>
+<p>For further details of all the methods available on each of the above variables,
please check the Javadoc</p>
 </component>
 
 <component name="JSR223 Assertion" index="&sect-num;.5.11">
@@ -4881,7 +4881,7 @@ The JSR223 Assertion allows JSR223 scrip
 The script can check various aspects of the <a href="../api/org/apache/jmeter/samplers/SampleResult.html">SampleResult</a>.
 If an error is detected, the script should use AssertionResult.setFailureMessage("message")
and AssertionResult.setFailure(true).
 </p>
-<p>For futher details of all the methods available on each of the above variables,
please check the Javadoc</p>
+<p>For further details of all the methods available on each of the above variables,
please check the Javadoc</p>
 </component>
 
 <component name="Compare Assertion" index="&sect-num;.5.12"  width="292" height="296"
screenshot="assertion/compare.png">
@@ -6250,7 +6250,7 @@ This has the advantage that even embedde
 JMeter needs to use the keytool application to create the keystore entries. 
 Versions of JMeter after 2.10 include code to check that keytool is available by looking
in various standard places.
 If JMeter is unable to find the keytool application, it will report an error.
-If necessary, the systen property <code>keytool.directory</code> can be used
to tell JMeter where to find keytool.
+If necessary, the system property <code>keytool.directory</code> can be used
to tell JMeter where to find keytool.
 This should be defined in the file <code>system.properties</code>.
 </p>
 <p>
@@ -6627,7 +6627,7 @@ For more details see "Extending JMeter".
 <component name="HTTP Mirror Server" index="&sect-num;.9.6"  width="671" height="174"
screenshot="mirrorserver.png">
 <description>
 <p>
-The HTTP Mirrror Server is a very simple HTTP server - it simply mirrors the data sent to
it.
+The HTTP Mirror Server is a very simple HTTP server - it simply mirrors the data sent to
it.
 This is useful for checking the content of HTTP requests.
 </p>
 <p>

Modified: jmeter/trunk/xdocs/usermanual/functions.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/functions.xml?rev=1694900&r1=1694899&r2=1694900&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/functions.xml (original)
+++ jmeter/trunk/xdocs/usermanual/functions.xml Sun Aug  9 19:18:36 2015
@@ -455,7 +455,7 @@ A reference name - <code>refName</code>
 Defaults to "<code>StringFromFile_</code>".
         </property>
         <property name="Start sequence number" required="No">Initial Sequence number
(if omitted, the End sequence number is treated as a loop count)</property>
-        <property name="End   sequence number" required="No">Final sequence number
(if omitted, seqence numbers can increase without limit)</property>
+        <property name="End   sequence number" required="No">Final sequence number
(if omitted, sequence numbers can increase without limit)</property>
 </properties>
 <p>The file name parameter is resolved when the file is opened or re-opened.</p>
 <p>The reference name parameter (if supplied) is resolved every time the function is
executed.</p>
@@ -918,7 +918,7 @@ If omitted, <code>,</code> is used. Note
         <property name="Format" required="No">
         The format to be passed to SimpleDateFormat.
         The function supports various shorthand aliases, see below.
-        If ommitted, the function returns the current time in milliseconds since the epoch.
+        If omitted, the function returns the current time in milliseconds since the epoch.
         </property>
         <property name="Name of variable" required="No">The name of the variable to
set.</property>
 </properties>

Modified: jmeter/trunk/xdocs/usermanual/get-started.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/get-started.xml?rev=1694900&r1=1694899&r2=1694900&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/get-started.xml (original)
+++ jmeter/trunk/xdocs/usermanual/get-started.xml Sun Aug  9 19:18:36 2015
@@ -261,7 +261,7 @@ then define the property <code>user.clas
 in <code>jmeter.properties</code>. See below for an explanation of the differences.
 </p>
 <p>
-Other jars (such as JDBC, JMS implementations and any other support libaries needed by the
JMeter code)
+Other jars (such as JDBC, JMS implementations and any other support libraries needed by the
JMeter code)
 should be placed in the <code>lib</code> directory - not the <code>lib/ext</code>
directory,
 or added to <code>user.classpath</code>.</p>
 <note>JMeter will only find <code>.jar</code> files, not <code>.zip</code>.</note>

Modified: jmeter/trunk/xdocs/usermanual/glossary.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/glossary.xml?rev=1694900&r1=1694899&r2=1694900&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/glossary.xml (original)
+++ jmeter/trunk/xdocs/usermanual/glossary.xml Sun Aug  9 19:18:36 2015
@@ -71,7 +71,7 @@ See, for example: <a href="http://en.wik
 <a name="StandardDeviation"><b>Standard Deviation</b></a> is a measure
of the variability
 of a data set. This is a standard statistical measure.
 See, for example: <a href="http://en.wikipedia.org/wiki/Standard_deviation">Standard
Deviation</a> entry at Wikipedia.
-JMeter calculates the population standard deviation (e.g. STDEVP function in spreadheets),
not the sample standard deviation (e.g. STDEV).
+JMeter calculates the population standard deviation (e.g. STDEVP function in spreadsheets),
not the sample standard deviation (e.g. STDEV).
 </p>
 
 <p>

Modified: jmeter/trunk/xdocs/usermanual/ldapops_tutor.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/ldapops_tutor.xml?rev=1694900&r1=1694899&r2=1694900&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/ldapops_tutor.xml (original)
+++ jmeter/trunk/xdocs/usermanual/ldapops_tutor.xml Sun Aug  9 19:18:36 2015
@@ -34,7 +34,7 @@
     The relative distinguished name (RDN) is the last part of the DN, eg. cn=admin.<br/>
     The characteristics of an object are determined by the objectClasses, which can be seen
as a collection of attributes.<br/>
     The type of an object is determined by the "structural objectClass" eg person, organizationalUnit
or country.<br/>
-    The attributes contain the data of an object, eg mailadress, name, streetadress etc.
Each attribute can have 0, 1 or more values.
+    The attributes contain the data of an object, eg mailaddress, name, streetaddress etc.
Each attribute can have 0, 1 or more values.
     </p>
 <subsection name="1 Bind operation" anchor="bind">
     <p>

Modified: jmeter/trunk/xdocs/usermanual/test_plan.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/test_plan.xml?rev=1694900&r1=1694899&r2=1694900&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/test_plan.xml (original)
+++ jmeter/trunk/xdocs/usermanual/test_plan.xml Sun Aug  9 19:18:36 2015
@@ -398,7 +398,7 @@ Assertion 1
 
 <subsection name="&sect-num;.10 Scoping Rules" anchor="scoping_rules">
 <p>
-The JMeter test tree contains elements that are both hierarchical and ordered.  Some elements
in the test trees are strictly hierarchical (Listeners, Config Elements, Post-Procesors, Pre-Processors,
Assertions, Timers), and some are primarily ordered (controllers, samplers).  When you create
your test plan, you will create an ordered list of sample request (via Samplers) that represent
a set of steps to be executed.  These requests are often organized within controllers that
are also ordered.  Given the following test tree:</p>
+The JMeter test tree contains elements that are both hierarchical and ordered.  Some elements
in the test trees are strictly hierarchical (Listeners, Config Elements, Post-Processors,
Pre-Processors, Assertions, Timers), and some are primarily ordered (controllers, samplers).
 When you create your test plan, you will create an ordered list of sample request (via Samplers)
that represent a set of steps to be executed.  These requests are often organized within controllers
that are also ordered.  Given the following test tree:</p>
 <figure image="scoping1.png">Example test tree</figure>
 <p>The order of requests will be, One, Two, Three, Four.</p>
 <p>Some controllers affect the order of their subelements, and you can read about these
specific controllers in <a href="component_reference.html">the component reference</a>.</p>
@@ -426,7 +426,7 @@ only one Manager is used, but there is c
 <subsection name="&sect-num;.11 Properties and Variables" anchor="properties">
 
 <p>
-JMeter <b>properties</b> are defined in jmeter.properties (see <a href="get-started.html#configuring_jmeter">Gettting
Started - Configuring JMeter</a> for more details).
+JMeter <b>properties</b> are defined in jmeter.properties (see <a href="get-started.html#configuring_jmeter">Getting
Started - Configuring JMeter</a> for more details).
 <br></br>
 Properties are global to jmeter, and are mostly used to define some of the defaults JMeter
uses.
 For example the property remote_hosts defines the servers that JMeter will try to run remotely.



Mime
View raw message