s/DataDog/Datadog (helm#21498)

Signed-off-by: Gabriel Aszalos <gabriel.aszalos@gmail.com>
vboulineau · Mar 17, 2020 · c0f487e · c0f487e
1 parent aa307a3
commit c0f487e
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 5 deletions.
diff --git a/stable/datadog/Chart.yaml b/stable/datadog/Chart.yaml
@@ -1,8 +1,8 @@
 apiVersion: v1
 name: datadog
-version: 2.0.8
+version: 2.0.9
 appVersion: "7"
-description: DataDog Agent
+description: Datadog Agent
 keywords:
 - monitoring
 - alerting

diff --git a/stable/datadog/templates/NOTES.txt b/stable/datadog/templates/NOTES.txt
@@ -1,6 +1,5 @@
-
 {{- if (or (.Values.datadog.apiKeyExistingSecret) (not (eq .Values.datadog.apiKey "<DATADOG_API_KEY>"))) }}
-DataDog agents are spinning up on each node in your cluster. After a few
+Datadog agents are spinning up on each node in your cluster. After a few
 minutes, you should see your agents starting in your event stream:
     https://app.datadoghq.com/event/stream
 

diff --git a/stable/datadog/values.yaml b/stable/datadog/values.yaml
@@ -541,7 +541,7 @@ agents:
   ## @param enabled - boolean - required
   ## You should keep Datadog DaemonSet enabled!
   ## The exceptional case could be a situation when you need to run
-  ## single DataDog pod per every namespace, but you do not need to
+  ## single Datadog pod per every namespace, but you do not need to
   ## re-create a DaemonSet for every non-default namespace install.
   ## Note: StatsD and DogStatsD work over UDP, so you may not
   ## get guaranteed delivery of the metrics in Datadog-per-namespace setup!