From b620df780a74b4a28dd152095dde668d425b628d Mon Sep 17 00:00:00 2001 From: Pedro Lamas Date: Sun, 8 Aug 2021 14:49:27 +0100 Subject: [PATCH] Fixes link in scripts.markdown and schema.markdown (#18826) --- source/_docs/blueprint/schema.markdown | 2 +- source/_docs/scripts.markdown | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_docs/blueprint/schema.markdown b/source/_docs/blueprint/schema.markdown index 2f88a109dc4..b47b1e125a3 100644 --- a/source/_docs/blueprint/schema.markdown +++ b/source/_docs/blueprint/schema.markdown @@ -121,7 +121,7 @@ A blueprint can have as many inputs as you like. The inputs are available as custom YAML tags, but not as template variables. To use a blueprint input in a template, it first needs to be exposed as either -a [script level variable](/integrations/script/#-configuration-variables) or in +a [script level variable](/integrations/script/#configuration-variables) or in a [variable script step](/docs/scripts/#variables). ```yaml diff --git a/source/_docs/scripts.markdown b/source/_docs/scripts.markdown index 98dd5df48ee..f76598b68eb 100644 --- a/source/_docs/scripts.markdown +++ b/source/_docs/scripts.markdown @@ -674,4 +674,4 @@ automation: [service calls page]: /getting-started/scripts-service-calls/ [conditions page]: /getting-started/scripts-conditions/ [shorthand-template]: /docs/scripts/conditions/#template-condition-shorthand-notation -[script variables]: /integrations/script/#-configuration-variables +[script variables]: /integrations/script/#configuration-variables