Minor edits to the documentation

docs/running-without-web-ui.rst

@@ -83,4 +83,4 @@ Below is an example that'll set the exit code to non zero if any of the followin
         else:
             environment.process_exit_code = 0
 
-This code could go into the locustfile.py or in any other file that is imported in the locustfile.
+(Note that this code could go into the locustfile.py or in any other file that is imported in the locustfile.)

docs/testing-requests-based SDK's.rst

@@ -7,7 +7,7 @@ Testing Requests based SDKs
 If a prebuilt SDK is available for your target system, Locust has a supported pattern for integrating
 its usage into your load testing efforts.
 
-The only perquisite to achieve this is that the SDK needs to have an accessible ``request.Sessions``
+The only prerequisite to achieve this is that the SDK needs to have an accessible ``request.Sessions``
 class.
 
 The following example shows the locust client overwriting the internal ``_session`` object of ``Archivist`` SDK

docs/writing-a-locustfile.rst

@@ -293,7 +293,7 @@ The easiest way to add a task for a User is by using the :py:meth:`task <locust.
             print("User instance (%r) executing my_task" % self)
 
 **@task** takes an optional weight argument that can be used to specify the task's execution ratio. In
-the following example, *task2* will be twice as likely to be selected than *task1*:
+the following example, *task2* will be twice as likely to be selected as *task1*:
 
 .. code-block:: python
 
@@ -343,7 +343,7 @@ with a task that looks like this::
 
     {my_task: 3, another_task: 1}
 
-*my_task* would be 3 times as likely to be executed than *another_task*.
+*my_task* would be 3 times as likely to be executed as *another_task*.
 
 Internally the above dict will actually be expanded into a list (and the ``tasks`` attribute is updated)
 that looks like this::