From 9596dc768ad4b44aa3f6772a64912f8d04c4ea44 Mon Sep 17 00:00:00 2001
From: Matthew Fisher <matt.fisher@microsoft.com>
Date: Tue, 29 Jan 2019 12:35:44 -0800
Subject: [PATCH] add missing "and" (#5227)
Signed-off-by: Matthew Fisher <matt.fisher@microsoft.com>
---
docs/chart_template_guide/variables.md | 9 +++------
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/docs/chart_template_guide/variables.md b/docs/chart_template_guide/variables.md
index d924fe2cf..dda92559b 100644
--- a/docs/chart_template_guide/variables.md
+++ b/docs/chart_template_guide/variables.md
@@ -98,10 +98,7 @@ data:
Variables are normally not "global". They are scoped to the block in which they are declared. Earlier, we assigned `$relname` in the top level of the template. That variable will be in scope for the entire template. But in our last example, `$key` and `$val` will only be in scope inside of the `{{range...}}{{end}}` block.
-However, there is one variable that is always global - `$` - this
-variable will always point to the root context. This can be very
-useful when you are looping in a range need to know the chart's release
-name.
+However, there is one variable that is always global - `$` - this variable will always point to the root context. This can be very useful when you are looping in a range and need to know the chart's release name.
An example illustrating this:
```yaml
@@ -111,8 +108,8 @@ kind: Secret
metadata:
name: {{ .name }}
labels:
- # Many helm templates would use `.` below, but that will not work,
- # however `$` will work here
+ # Many helm templates would use `.` below, but that will not work,
+ # however `$` will work here
app.kubernetes.io/name: {{ template "fullname" $ }}
# I cannot reference .Chart.Name, but I can do $.Chart.Name
helm.sh/chart: "{{ $.Chart.Name }}-{{ $.Chart.Version }}"
--
GitLab