From 568f613401cc67c91b62679b843eaa2fb74184a0 Mon Sep 17 00:00:00 2001 From: Erin Call Date: Thu, 26 Dec 2019 09:44:46 -0800 Subject: [PATCH] Associate lines of text with their yaml blocks [#8] As I skimmed through that section I noticed it wasn't immediately clear whether a line of text was referring to the example above it or the one below it. --- docs/parameter_reference.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/parameter_reference.md b/docs/parameter_reference.md index ba492ed..07d8107 100644 --- a/docs/parameter_reference.md +++ b/docs/parameter_reference.md @@ -90,7 +90,7 @@ values_files: [ "./over_9", "000.yml" ] Because the prefix setting is meta-configuration, it has some inherent edge-cases. Here is what it does in the cases we've thought of: -Unlike the other settings, it must be declared in the `settings` block, not `environment`. +Unlike the other settings, it must be declared in the `settings` block, not `environment`: ```yaml settings: @@ -99,7 +99,7 @@ environment: prefix: armet # no effect ``` -It does not apply to configuration in the `settings` block, only in `environment`. +It does not apply to configuration in the `settings` block, only in `environment`: ```yaml settings: @@ -109,7 +109,7 @@ environment: helm_timeout: 2m # timeout will be 2 minutes ``` -If the environment contains a variable in non-prefixed form, it will still be applied. +If the environment contains a variable in non-prefixed form, it will still be applied: ```yaml settings: @@ -118,7 +118,7 @@ environment: timeout: 2m # timeout will be 2 minutes ``` -If the environment contains both the prefixed and non-prefixed forms, drone-helm3 will use the prefixed form. +If the environment contains both the prefixed and non-prefixed forms, drone-helm3 will use the prefixed form: ```yaml settings: