Fix Vale errors in env-vars.adoc (#10516)

* don't error for links to support site

* Fix Vale errors in env-vars.adoc

Resolved the following Vale errors:
- Lines 11,13,20,25,27,41-46,125,159,180,249,274-275,279,284,289-291: XrefTitleCase - Updated all xref link texts to title case
- Lines 50,107: ImageTitles - Added missing image titles
- Line 109: Avoid 'am' - Rewrote prose to avoid quoting step name containing 'am'
- Line 206: Avoid 'were' - 'as if they were defined' → 'as if they are defined'

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>

---------

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>

Author: 3 people

docs/guides/modules/security/pages/env-vars.adoc

@@ -8,23 +8,23 @@
 
 Use environment variables to set up various configuration options, and keep your set-up secure with secrets, private keys, and contexts. Environment variables in CircleCI are governed by an <<order-of-precedence,order of precedence>>, allowing control at each level in your configuration.
 
-See the xref:set-environment-variable.adoc[Set an environment variable] page for guidance on the different ways to set an environment variable.
+See the xref:set-environment-variable.adoc[Set an Environment Variable] page for guidance on the different ways to set an environment variable.
 
-If you have existing environment variables (or contexts) and you would like to rename your organization or repository, follow the xref:rename-organizations-and-repositories.adoc[Rename organizations and repositories] guide. The recommended steps ensure you do not lose access to environment variables or contexts in the process.
+If you have existing environment variables (or contexts) and you would like to rename your organization or repository, follow the xref:rename-organizations-and-repositories.adoc[Rename Organizations and Repositories] guide. The recommended steps ensure you do not lose access to environment variables or contexts in the process.
 
 [#built-in-environment-variables]
 == Built-in environment variables
 
 All projects have access to CircleCI's built-in environment variables. These environment variables are scoped at the job level, so they can be used with the `context` key in a job, but they do not exist at a pipeline level.
 
-For a full list of built-in environment variables, see the xref:reference:ROOT:variables.adoc#built-in-environment-variables[Project values and variables] page.
+For a full list of built-in environment variables, see the xref:reference:ROOT:variables.adoc#built-in-environment-variables[Project Values and Variables] page.
 
 [#private-keys-and-secrets]
 == Private keys and secrets
 
-To add private keys or secrets as environment variables for use throughout your project, navigate to menu:Project Settings[Environment Variables] in the link:https://app.circleci.com/[CircleCI web app]. You can find step-by-step instructions of this process on the xref:set-environment-variable.adoc#set-an-environment-variable-in-a-project[Environment variables] page. The variable values are neither readable nor editable in the app after they are set. To change the value of an environment variable, delete the current variable, and add it again with the new value.
+To add private keys or secrets as environment variables for use throughout your project, navigate to menu:Project Settings[Environment Variables] in the link:https://app.circleci.com/[CircleCI web app]. You can find step-by-step instructions of this process on the xref:set-environment-variable.adoc#set-an-environment-variable-in-a-project[Environment Variables] page. The variable values are neither readable nor editable in the app after they are set. To change the value of an environment variable, delete the current variable, and add it again with the new value.
 
-Private environment variables enable you to store secrets safely, even when your project is public. Refer to the xref:integration:oss.adoc[Building open source projects] page for associated security and settings information.
+Private environment variables enable you to store secrets safely, even when your project is public. Refer to the xref:integration:oss.adoc[Building Open Source Projects] page for associated security and settings information.
 
 include::ROOT:partial$shared-sections/secrets-masking.adoc[]
 
@@ -38,15 +38,16 @@ CircleCI uses Bash, which follows the POSIX naming convention for environment va
 
 Environment variables are used according to a specific precedence order, as follows:
 
-. Environment variables declared xref:set-environment-variable.adoc#set-an-environment-variable-in-a-shell-command[inside a shell command] in a `run` step, for example `FOO=bar make install`.
-. Environment variables declared with the `environment` key xref:set-environment-variable.adoc#set-an-environment-variable-in-a-step[for a `run` step].
-. Environment variables set with the `environment` key xref:set-environment-variable.adoc#set-an-environment-variable-in-a-job[for a job].
-. Special CircleCI environment variables defined in the xref:reference:ROOT:variables.adoc#built-in-environment-variables[CircleCI Built-in environment variables] document.
+. Environment variables declared xref:set-environment-variable.adoc#set-an-environment-variable-in-a-shell-command[Inside a Shell Command] in a `run` step, for example `FOO=bar make install`.
+. Environment variables declared with the `environment` key xref:set-environment-variable.adoc#set-an-environment-variable-in-a-step[For a `run` Step].
+. Environment variables set with the `environment` key xref:set-environment-variable.adoc#set-an-environment-variable-in-a-job[For a Job].
+. Special CircleCI environment variables defined in the xref:reference:ROOT:variables.adoc#built-in-environment-variables[CircleCI Built-in Environment Variables] document.
 . Context environment variables (assuming the user has access to the context). See the xref:contexts.adoc[Contexts] documentation for more information.
-. xref:set-environment-variable.adoc#set-an-environment-variable-in-a-project[Project-level environment variables] set on the *Project Settings* page in the web app.
+. xref:set-environment-variable.adoc#set-an-environment-variable-in-a-project[Project-Level Environment Variables] set on the *Project Settings* page in the web app.
 
 Environment variables declared inside a shell command `run` step, for example `FOO=bar make install`, will override environment variables declared with the `environment` and `contexts` keys. Environment variables added on the *Contexts* page in the web app will take precedence over variables added on the *Project Settings* page.
 
+.Environment variable order of precedence
 image::guides:ROOT:env-var-order.png[Environment variable order of precedence]
 
 [#example-configuration-of-environment-variables]
@@ -104,9 +105,10 @@ The above `.circleci/config.yml` demonstrates the following:
 
 When the above configuration runs, the output looks like the image below. Notice the environment variables stored in the project is masked, and displays as `+****+`:
 
+.Environment variable interpolation example
 image::guides:ROOT:env-vars-example-ui.png[Environment variable interpolation example]
 
-Notice there are two similar steps in the above image and configuration - "What branch am I on?" These steps illustrate two different methods to read environment variables.
+Notice there are two similar steps in the above image and configuration - both checking the current branch name. These steps illustrate two different methods to read environment variables.
 
 In the example configuration above, two syntax variants are used: `+${VAR}+` and `$VAR`. Both syntax variants are supported. You can read more about shell parameter expansion in the link:https://www.gnu.org/software/bash/manual/bashref.html#Shell-Parameter-Expansion[Bash documentation].
 
@@ -122,7 +124,7 @@ In the example below, `$ORGNAME` and `$REPONAME` will not be interpolated.
 working_directory: /go/src/github.com/$ORGNAME/$REPONAME
 ----
 
-NOTE: An exception to this interpolation rule is using project environment variables to pull xref:execution-managed:private-images.adoc[private images].
+NOTE: An exception to this interpolation rule is using project environment variables to pull xref:execution-managed:private-images.adoc[Private Images].
 
 You can reuse pieces of configuration across your `.circleci/config.yml` file. By using the `parameters` declaration, you can pass values into reusable `commands`, `jobs`, and `executors`:
 
@@ -156,7 +158,7 @@ workflows:
           repo_name: project2
 ----
 
-For more information, read the documentation on xref:reference:ROOT:reusing-config.adoc#using-the-parameters-declaration[using the parameters declaration].
+For more information, read the documentation on xref:reference:ROOT:reusing-config.adoc#using-the-parameters-declaration[Using the Parameters Declaration].
 
 Another possible method to interpolate values into your configuration is to use a `run` step to export environment variables to `BASH_ENV`, as shown below.
 
@@ -177,7 +179,7 @@ In every step, CircleCI uses `bash` to source `BASH_ENV`. This means that `BASH_
 [#environment-variable-substitution]
 === Environment variable substitution
 
-The CircleCI environment CLI offers a wrapper around the link:https://github.com/a8m/envsubst[`envsubst`] tool, available both locally as well as in all jobs running on CircleCI. `envsubst` is a command-line utility used to replace environment variables in text strings. You can also refer to the full xref:toolkit:environment-cli-usage-guide.adoc[Environment CLI usage guide].
+The CircleCI environment CLI offers a wrapper around the link:https://github.com/a8m/envsubst[`envsubst`] tool, available both locally as well as in all jobs running on CircleCI. `envsubst` is a command-line utility used to replace environment variables in text strings. You can also refer to the full xref:toolkit:environment-cli-usage-guide.adoc[Environment CLI Usage Guide].
 
 CLI command:
 
@@ -203,7 +205,7 @@ Within your repository create a file such as `template.json`, with value replace
 
 `envsubst` can convert all types of environment variable strings, including those encased in curly braces (`{}`).
 
-The config example below shows the corresponding environment variables as if they were defined directly within a step in the config. However, we strongly recommend creating the environment variables in the CircleCI app, either in xref:set-environment-variable.adoc#set-an-environment-variable-in-a-project[Project Settings] or as a xref:contexts.adoc[context].
+The config example below shows the corresponding environment variables as if they are defined directly within a step in the config. However, we strongly recommend creating the environment variables in the CircleCI app, either in xref:set-environment-variable.adoc#set-an-environment-variable-in-a-project[Project Settings] or as a xref:contexts.adoc[context].
 
 [,yaml]
 ----
@@ -246,7 +248,7 @@ Output:
 }
 ----
 
-For instructions on installing the CircleCI CLI locally, read the xref:toolkit:local-cli.adoc[Installing the CircleCI local CLI] guide.
+For instructions on installing the CircleCI CLI locally, read the xref:toolkit:local-cli.adoc[Installing the CircleCI Local CLI] guide.
 
 [#alpine-linux]
 === Alpine Linux
@@ -271,21 +273,21 @@ jobs:
 
 Do not add secrets or keys inside the `.circleci/config.yml` file. The full text of `.circleci/config.yml` is visible to developers with access to your project on CircleCI. Store secrets or keys in the CircleCI web app under one of the following:
 
-* In xref:set-environment-variable.adoc#set-an-environment-variable-in-a-project[Project settings].
-* In a xref:set-environment-variable.adoc#set-an-environment-variable-in-a-context[context].
+* In xref:set-environment-variable.adoc#set-an-environment-variable-in-a-project[Project Settings].
+* In a xref:set-environment-variable.adoc#set-an-environment-variable-in-a-context[Context].
 
 For more information, see the xref:security.adoc#encryption[Encryption] section of the security page.
 
-Running scripts within configuration may expose secret environment variables. See the xref:orchestrate:using-shell-scripts.adoc#shell-script-best-practices[Using shell scripts] page for best practices for secure scripts.
+Running scripts within configuration may expose secret environment variables. See the xref:orchestrate:using-shell-scripts.adoc#shell-script-best-practices[Using Shell Scripts] page for best practices for secure scripts.
 
 [#contexts]
 == Contexts
 
-You can further restrict access to environment variables using xref:contexts.adoc[contexts]. Contexts are set from the *Organization Settings* in the CircleCI web app.
+You can further restrict access to environment variables using xref:contexts.adoc[Contexts]. Contexts are set from the *Organization Settings* in the CircleCI web app.
 
 [#see-also]
 == See also
 
-* xref:security-recommendations.adoc[Security recommendations]
-* xref:set-environment-variable.adoc[Set an environment variable]
-* xref:inject-environment-variables-with-api.adoc[Inject variables using the CircleCI API]
+* xref:security-recommendations.adoc[Security Recommendations]
+* xref:set-environment-variable.adoc[Set an Environment Variable]
+* xref:inject-environment-variables-with-api.adoc[Inject Variables Using the CircleCI API]