diff --git a/www/docs/calldata.md b/www/docs/calldata.md
index 220a7b35..3165f462 100644
--- a/www/docs/calldata.md
+++ b/www/docs/calldata.md
@@ -61,7 +61,7 @@ There are also template functions available:
 Generates a new UUID for each invocation.
 
 `func randomString(length int) string`  
-Generates a new random string for each incovation. Accepts a length parameter. If the argument is `<= 0` then a random string is generated with a random length between length of `2` and `16`.
+Generates a new random string for each invocation. Accepts a length parameter. If the argument is `<= 0` then a random string is generated with a random length between length of `2` and `16`.
 
 `func randomInt(min, max int) int`  
 Generates a new non-negative pseudo-random number in range `[min, max)`.
diff --git a/www/docs/load.md b/www/docs/load.md
index 0e50c2dd..87aefa23 100644
--- a/www/docs/load.md
+++ b/www/docs/load.md
@@ -95,7 +95,7 @@ Status code distribution:
   [OK]   10000 responses
 ```
 
-Performs step load starting at `50` RPS and inscreasing by `10` RPS every `5s` until we reach `150` RPS at which point the load is sustained at constant RPS rate until we reach `10000` total requests. The RPS load is distributed among the `10` workers, all sharing `1` connection.
+Performs step load starting at `50` RPS and increasing by `10` RPS every `5s` until we reach `150` RPS at which point the load is sustained at constant RPS rate until we reach `10000` total requests. The RPS load is distributed among the `10` workers, all sharing `1` connection.
 
 ![Step Up Load](/images/const_c_step_up_rps.svg)
 
diff --git a/www/docs/options.md b/www/docs/options.md
index 7e89128f..e0b6bdc5 100644
--- a/www/docs/options.md
+++ b/www/docs/options.md
@@ -89,19 +89,19 @@ Examples:
 -n 10000 -c 10 --load-schedule=step --load-start=50 --load-step=10 --load-step-duration=5s
 ```
 
-Performs step load starting at `50` RPS and inscreasing by `10` RPS every `5s` until we reach `10000` total requests. The RPS load is distributed among the `10` workers, all sharing `1` connection.
+Performs step load starting at `50` RPS and increasing by `10` RPS every `5s` until we reach `10000` total requests. The RPS load is distributed among the `10` workers, all sharing `1` connection.
 
 ```sh
 -n 10000 -c 10 --load-schedule=step --load-start=50 --load-end=150 --load-step=10 --load-step-duration=5s
 ```
 
-Performs step load starting at `50` RPS and inscreasing by `10` RPS every `5s` until we reach `150` RPS at which point the load is sustained at constant RPS rate until we reach `10000` total requests. The RPS load is distributed among the `10` workers, all sharing `1` connection.
+Performs step load starting at `50` RPS and increasing by `10` RPS every `5s` until we reach `150` RPS at which point the load is sustained at constant RPS rate until we reach `10000` total requests. The RPS load is distributed among the `10` workers, all sharing `1` connection.
 
 ```sh
 -n 10000 -c 10 --load-schedule=step --load-start=50 --load-step=10 --load-step-duration=5s --load-max-duration=60s
 ```
 
-Performs step load starting at `50` RPS and inscreasing by `10` RPS every `5s` until `60s` has elapsed at which point the load is sustained at that RPS rate until we reach `10000` total requests. The RPS load is distributed among the `10` workers, all sharing `1` connection.
+Performs step load starting at `50` RPS and increasing by `10` RPS every `5s` until `60s` has elapsed at which point the load is sustained at that RPS rate until we reach `10000` total requests. The RPS load is distributed among the `10` workers, all sharing `1` connection.
 
 ```sh
 -n 10000 -c 10 --load-schedule=line --load-start=200 --load-step=-2 --load-end=50