Merge pull request #1453 from howardosborne/master

minor typos in docs

docs/quickstart.rst

@@ -122,7 +122,7 @@ and point it to http://127.0.0.1:8089. Then you should be greeted with something
 
 .. image:: images/webui-splash-screenshot.png
 
-Fill out the form and try it out! (but note that if you dont change your locust file to match your target system you'll mostly get error responses)
+Fill out the form and try it out! (but note that if you don't change your locust file to match your target system you'll mostly get error responses)
 
 .. image:: images/webui-running-statistics.png
 
@@ -133,7 +133,7 @@ More options
 ============
 
 To run Locust distributed across multiple Python processes or machines, you can start a single Locust master process 
-with the ``--master`` command line parameter, and then any number of Locust worker processes usin the ``--worker`` 
+with the ``--master`` command line parameter, and then any number of Locust worker processes using the ``--worker`` 
 command line parameter. See :ref:`running-locust-distributed` for more info.
 
 To start tests directly, without using the web interface, use ``--headless``. 

docs/retrieving-stats.rst

@@ -16,7 +16,7 @@ if you plan on running Locust in an automated way with the ``--headless`` flag:
 The files will be named ``example_stats.csv``, ``example_failures.csv`` and ``example_history.csv``
 (when using ``--csv=example``). The first two files will contain the stats and failures for the whole 
 test run, with a row for every stats entry (URL endpoint) and an aggregated row. The ``example_history.csv`` 
-will get new rows with the *current* (10 seconds sliding window) stats appanded during the whole test run. 
+will get new rows with the *current* (10 seconds sliding window) stats appended during the whole test run. 
 By default only the Aggregate row is appended regularly to the history stats, but if Locust is started with 
 the ``--csv-full-history`` flag, a row for each stats entry (and the Aggregate) is appended every time 
 the stats are written (once every 2 seconds by default).

docs/running-locust-distributed.rst

@@ -38,7 +38,7 @@ To start locust in master mode::
 
     locust -f my_locustfile.py --master
 
-And then on each worker (replace ``192.168.0.14`` with IP of the master machine, or leave out the parameter alltogether if your workers are on the same machine as the master)::
+And then on each worker (replace ``192.168.0.14`` with IP of the master machine, or leave out the parameter altogether if your workers are on the same machine as the master)::
 
     locust -f my_locustfile.py --worker --master-host=192.168.0.14
 

docs/running-locust-without-web-ui.rst

@@ -76,7 +76,7 @@ Below is an example that'll set the exit code to non zero if any of the followin
             logging.error("Test failed due to average response time ratio > 200 ms")
             environment.process_exit_code = 1
         elif environment.stats.total.get_response_time_percentile(0.95) > 800:
-            logging.error("Test failed due to 95th percentil response time > 800 ms")
+            logging.error("Test failed due to 95th percentile response time > 800 ms")
             environment.process_exit_code = 1
         else:
             environment.process_exit_code = 0

docs/writing-a-locustfile.rst

@@ -389,7 +389,7 @@ SequentialTaskSet class. It is possible to nest SequentialTaskSets within a Task
         def first_task(self):
             pass
         
-        tasks = [functon_task]
+        tasks = [function_task]
         
         @task
         def second_task(self):
@@ -608,7 +608,7 @@ python ``import`` statement.
 For small tests, keeping all of the test code in a single ``locustfile.py`` should work fine, but for 
 larger test suites, you'll probably want to split the code into multiple files and directories. 
 
-How you structure the test source code is ofcourse entirely up to you, but we recommend that you 
+How you structure the test source code is of course entirely up to you, but we recommend that you 
 follow Python best practices. Here's an example file structure of an imaginary Locust project:
 
 * Project root