From 83c2c613b1552d32085387b932253bcaf5f558b3 Mon Sep 17 00:00:00 2001 From: Robert Wallach Date: Tue, 20 Mar 2018 15:11:28 -0500 Subject: [PATCH] Update editor-configuration.md --- articles/editor/editor-configuration.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/articles/editor/editor-configuration.md b/articles/editor/editor-configuration.md index 3a81652..1f73fc1 100644 --- a/articles/editor/editor-configuration.md +++ b/articles/editor/editor-configuration.md @@ -16,7 +16,7 @@ You can make changes to the `.stoplight.yml` file by opening it: ![](../../assets/images/editor-configuration2.png) -Environments make it easy to auto-populate variables (hostnames, ports, passwords, etc.) used by specifications and scenarios. Read more about them [here](../testing/variables-environment.md). +Environments make it easy to auto-populate variables (hostnames, ports, passwords, etc.) used by specifications and scenarios. Read more about them [here](/testing/using-variables/environment). The environments and variables defined in the `.stoplight.yml` are shared amongst all users, which makes this a good place to define common or shared variables, such as the url host for a particular API + environment. @@ -30,6 +30,6 @@ These environments can be customized by editing the `environments` key of the `. *** -**Related** +**Related Articles** -* [Testing Environment Variables](../testing/variables-environment.md) +* [Testing Environment Variables](/testing/using-variables/environment)