From d5429515d32cb67b65e999e52a69c46d97af0196 Mon Sep 17 00:00:00 2001 From: a Date: Thu, 25 Jul 2024 16:16:46 -0500 Subject: [PATCH] fix ref --- src/docs/markdown/extending-caddy/placeholders.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/docs/markdown/extending-caddy/placeholders.md b/src/docs/markdown/extending-caddy/placeholders.md index 14deee6..6a45096 100644 --- a/src/docs/markdown/extending-caddy/placeholders.md +++ b/src/docs/markdown/extending-caddy/placeholders.md @@ -14,7 +14,7 @@ If you are not yet familiar with placeholders, start by reading [here](/docs/con Internally, placeholders are simply a string in format `{foo.bar}` used as valid configuration values, which is later parsed at runtime. -Placeholders-like strings which start with a dollar sign (`{$FOO}`), are evaulated at Caddyfile parse time, and do not need to be dealt with by your plugin. This is because these are not placeholders, but Caddyfile-specific [environmental variable substitution](/docs/caddyfile/concepts/#environmental-variables), they just happen to share the `{}` syntax. +Placeholders-like strings which start with a dollar sign (`{$FOO}`), are evaulated at Caddyfile parse time, and do not need to be dealt with by your plugin. This is because these are not placeholders, but Caddyfile-specific [environmental variable substitution](/docs/caddyfile/concepts#environmental-variables), they just happen to share the `{}` syntax. It is therefore important to understand that `{env.HOST}` is inherently different from something like `{$HOST}`