fix: update some headers to point to the correct location

Author: kcbimonte

docs/docs/steps/index.md

@@ -11,7 +11,7 @@ A build plan is a sequence of steps:
 * the [`get` step](get.md) fetches a [resource](../resources/index.md)
 * the [`put` step](put.md) updates a [resource](../resources/index.md)
 * the [`set_pipeline` step](set-pipeline.md) configures a [pipeline](../pipelines/index.md)
-* the [`load_var` step](load-var.md) loads a value into a [local var](../vars.md#the--var-source)
+* the [`load_var` step](load-var.md) loads a value into a [local var](../vars.md#local-var)
 * the [`in_parallel` step](in-parallel.md) runs steps in parallel
 * the [`do` step](do.md) runs steps in sequence
 * the [`across` step](modifier-and-hooks/across.md) modifier runs a step multiple times; once for each combination of

docs/docs/steps/load-var.md

@@ -5,5 +5,5 @@ title: Load Var Step
 # `load_var` Step
 
 Load the value for a var at runtime from a file, making it available to subsequent steps as
-a [local build var](../vars.md#the--var-source) named after the given identifier. Expand each section below for more
+a [local build var](../vars.md#local-var) named after the given identifier. Expand each section below for more
 details and examples.

docs/docs/steps/modifier-and-hooks/across.md

@@ -16,7 +16,7 @@ the [`set_pipeline` step](../set-pipeline.md), and [instanced pipelines](../../p
 maintain a dynamically sized group of related pipelines.
 
 More fields are also available for variable interpolation with the across step.
-See [Across Step & Dynamic Vars](../../vars.md#across-step--dynamic-vars) for details.
+See [Across Step & Dynamic Vars](../../vars.md#across-step-dynamic-vars) for details.
 
 !!! note
 

docs/docs/vars.md

@@ -19,7 +19,7 @@ The full syntax for vars is `((`_`source-name:secret-path.secret-field`_`))`.
 The optional _source-name_ identifies the [var source](#var-sources-experimental) from which the value will be read. If
 omitted (along with the `:` delimiter), the [cluster-wide credential manager](#the-cluster-wide-credential-manager) will
 be used, or the value may be provided [statically](#static-vars). The special name `.` refers to
-the [local var source](#the--var-source), while any other name refers to a [var source](#var-sources-experimental).
+the [local var source](#local-var), while any other name refers to a [var source](#var-sources-experimental).
 
 The required _secret-path_ identifies the location of the credential. The interpretation of this value depends on the
 var source type. For example, with Vault this may be a path like `path/to/cred`. For the Kubernetes secret manager this
@@ -36,7 +36,7 @@ The _secret-path_ and _secret-field_ may be surrounded by double quotes `"..."`
 like `.` and `:`. For instance, `((source:"my.secret"."field:1"))` will set the _secret-path_ to `my.secret` and the
 _secret-field_ to `field:1`.
 
-## The "`.`" var source
+## The "`.`" var source {: #local-var }
 
 The special var source name `.` refers to a "local var source."