update docs

docs/src/variables.md

@@ -11,9 +11,9 @@ Variables can be defined statically as part of the suite or test configuration,
 - Local Variables - These are defined at the test level under the field `define`. They are only valid for that single test. They can be useful for specifying complex structures to be used as matcher arguments, or they can be used to override suite variables for a single test.
 - Environment Variables - These are pulled from your shell environment or from a [env file](./configuration/config.md#environment-variables). They are useful for synchronizing values in your tests that are also available to your server or other services.
 
-## Variable Precendence
+## Variable Precedence
 
-Variables can be defined as any or all of the above types, and certain types take precendence over others. In order from highest precendence:
+Variables can be defined as any or all of the above types, and certain types take precedence over others. In order from highest precedence:
 
 > Local -> Extracted / Global -> Environment (.env) -> Environment (Shell)
 

docs/src/variables/env_variables.md

@@ -13,7 +13,7 @@ For example, if you have a `SERVER_URL` variable defined in your local environme
       status: 200
 ```
 
-However, since variables defined in your test suite take precendence, if you were to define the SERVER_URL in your suite configuration, that value will be used instead.
+However, since variables defined in your test suite take precedence, if you were to define the SERVER_URL in your suite configuration, that value will be used instead.
 
 ```yaml
 suite: User endpoint tests