summaryrefslogtreecommitdiffstats
path: root/docs/guides/monitor/kubernetes-k8s-netdata.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/guides/monitor/kubernetes-k8s-netdata.md')
-rw-r--r--docs/guides/monitor/kubernetes-k8s-netdata.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/guides/monitor/kubernetes-k8s-netdata.md b/docs/guides/monitor/kubernetes-k8s-netdata.md
index 097cc13ac9..40af0e94ed 100644
--- a/docs/guides/monitor/kubernetes-k8s-netdata.md
+++ b/docs/guides/monitor/kubernetes-k8s-netdata.md
@@ -13,7 +13,7 @@ troubleshoot issues with your cluster.
Some k8s providers, like GKE (Google Kubernetes Engine), do deploy clusters bundled with monitoring capabilities, such
as Google Stackdriver Monitoring. However, these pre-configured solutions might not offer the depth of metrics,
-customization, or integration with your perferred alerting methods.
+customization, or integration with your preferred alerting methods.
Without this visibility, it's like you built an entire house and _then_ smashed your way through the finished walls to
add windows.
@@ -23,7 +23,7 @@ you actively troubleshoot anomalies or outages. Better yet, this toolkit include
let you monitor the many layers of a Kubernetes cluster entirely for free.
We already have a few complementary tools and collectors for monitoring the many layers of a Kubernetes cluster,
-_entirely for free_. These methods work together to help you troubleshoot performance or availablility issues across
+_entirely for free_. These methods work together to help you troubleshoot performance or availability issues across
your k8s infrastructure.
- A [Helm chart](https://github.com/netdata/helmchart), which bootstraps a Netdata Agent pod on every node in your