[jmeter] branch master updated: Typo in link destination

[fs...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

fschumacher pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/jmeter.git


The following commit(s) were added to refs/heads/master by this push:
     new f7b1167  Typo in link destination
f7b1167 is described below

commit f7b11670839f62076752ce3bf377dbdf30a31c09
Author: Felix Schumacher <fe...@internetallee.de>
AuthorDate: Thu Dec 26 11:52:19 2019 +0100

    Typo in link destination
---
 xdocs/usermanual/component_reference.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/xdocs/usermanual/component_reference.xml b/xdocs/usermanual/component_reference.xml
index 5536309..750d22b 100644
--- a/xdocs/usermanual/component_reference.xml
+++ b/xdocs/usermanual/component_reference.xml
@@ -5121,8 +5121,8 @@ the required load.</p>
     <code>Ramp-up Period</code> and <code>Delay</code> to <code>0</code>.</p>
 
 <h4>Multiple thread groups starting at the same time</h4>
-<p>A variation of <code>Ramp-up</code> issue might appear when <complink name="Test Plan" /> includes multiple <complink name="Thead Group" />s. To mitigate that issue
-    one typically adds "random" delay to each <complink name="Thead Group" /> so threads start at different times.</p>
+<p>A variation of <code>Ramp-up</code> issue might appear when <complink name="Test Plan" /> includes multiple <complink name="Thread Group" />s. To mitigate that issue
+    one typically adds "random" delay to each <complink name="Thread Group" /> so threads start at different times.</p>
 <p><code>Precise Throughput Timer</code> avoids that issue since it schedules executions in a random way. You do not need to add extra random delays to mitigate startup spike</p>
 
 <h4>Number of iterations per hour</h4>