From e3a213be4fe7e19a685a97c61b35c26bd529ffdf Mon Sep 17 00:00:00 2001 From: Tien Pham Date: Sat, 17 Nov 2018 19:35:48 +0200 Subject: [PATCH] docs(environment-variables): Fix typo (#9999) `relavant` => `relevant` --- docs/docs/environment-variables.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/environment-variables.md b/docs/docs/environment-variables.md index 617d2fd01a202..9d002b096f75b 100644 --- a/docs/docs/environment-variables.md +++ b/docs/docs/environment-variables.md @@ -10,7 +10,7 @@ Note that we need to distinguish in this discussion between variables which have special places in order to be used in different deployment environments, and true OS-level environment variables that could be used in, for example, command-line calls. We'll call the former "Project Env Vars" and the latter "OS Env Vars". -In both cases we want to be able to access the relavant value of these variable for the environment +In both cases we want to be able to access the relevant value of these variable for the environment we're in. By default gatsby supports only 2 environments: