You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@jmeter.apache.org by pm...@apache.org on 2012/09/01 00:05:05 UTC

svn commit: r1379637 - /jmeter/trunk/xdocs/usermanual/best-practices.xml

Author: pmouawad
Date: Fri Aug 31 22:05:04 2012
New Revision: 1379637

URL: http://svn.apache.org/viewvc?rev=1379637&view=rev
Log:
fix typo

Modified:
    jmeter/trunk/xdocs/usermanual/best-practices.xml

Modified: jmeter/trunk/xdocs/usermanual/best-practices.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/best-practices.xml?rev=1379637&r1=1379636&r2=1379637&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/best-practices.xml (original)
+++ jmeter/trunk/xdocs/usermanual/best-practices.xml Fri Aug 31 22:05:04 2012
@@ -35,7 +35,7 @@
 <section name="&sect-num;.1 Limit the Number of Threads" anchor="limit_threads">
 <p>Your hardware's capabilities will limit the number of threads you can effectively
 run with JMeter.  It will also depend on how fast your server is (a faster server
-gives makes JMeter work harder since it returns request quicker).  The more
+ makes JMeter work harder since it returns request quicker).  The more
 JMeter works, the less accurate its timing information will be.  The more work
 JMeter does, the more each thread has to wait to get access to the CPU, the more
 inflated the timing information gets.  If you need large-scale load testing, consider