Update guide: Kubernetes monitoring with Netdata: Overview and visualizations (#10691)

* Start work on update

* Finish initial re-draft

* Sneak in tweaks to anomaly guides

* Tweaks to both guide and deploy instructions

* Add meta description

* Fixes for Odysseas

1 files changed, 11 insertions, 10 deletions

diff --git a/packaging/installer/methods/kubernetes.md b/packaging/installer/methods/kubernetes.md
index ceabcc8159..f593765fc3 100644
--- a/packaging/installer/methods/kubernetes.md
+++ b/packaging/installer/methods/kubernetes.md
@@ -41,7 +41,7 @@ dashboards available in Netdata Cloud.
 
 ## Claim your Kubernetes cluster to Netdata Cloud
 
-To start [Kubernetes monitoring](https://learn.netdata.cloud/docs/cloud/visualizations/kubernetes/), you must first
+To start [Kubernetes monitoring](https://learn.netdata.cloud/docs/cloud/visualize/kubernetes/), you must first
 [claim](/claim/README.md) your Kubernetes cluster to [Netdata Cloud](https://app.netdata.cloud). Claiming securely
 connects your Kubernetes cluster to stream metrics data to Netdata Cloud, enabling Kubernetes-specific visualizations
 like the health map and time-series composite charts.
@@ -107,7 +107,7 @@ Read up on the various configuration options in the [Helm chart
 documentation](https://github.com/netdata/helmchart#configuration) if you need to tweak your Kubernetes monitoring.
 
 Your first option is to create an `override.yml` file, if you haven't created one already for
-[claim](#claim-your-kubernetes-cluster-to-netdata-cloud), then apply the new configuration to your cluster with `helm
+[claiming](#claim-your-kubernetes-cluster-to-netdata-cloud), then apply the new configuration to your cluster with `helm
 upgrade`.
 
 ```bash
@@ -123,9 +123,9 @@ helm upgrade --set parent.database.volumesize=4Gi netdata netdata/netdata
 
 ### Configure service discovery
 
-Netdata's [service discovery](https://github.com/netdata/agent-service-discovery/#service-discovery), which is
-installed as part of the Helm chart installation, finds what services are running on a cluster's pods, converts that
-into configuration files, and exports them so they can be monitored.
+Netdata's [service discovery](https://github.com/netdata/agent-service-discovery/#service-discovery), installed as part
+of the Helm chart installation, finds what services are running in a cluster's containers and automatically collects
+service-level metrics from them.
 
 Service discovery supports [popular applications](https://github.com/netdata/helmchart#applications) and [Prometheus
 endpoints](https://github.com/netdata/helmchart#prometheus-endpoints).
@@ -171,16 +171,17 @@ helm upgrade netdata netdata/netdata
 
 ## What's next?
 
-[Start Kubernetes monitoring](https://learn.netdata.cloud/docs/cloud/visualizations/kubernetes/) in Netdata Cloud, which
+[Start Kubernetes monitoring](https://learn.netdata.cloud/docs/cloud/visualize/kubernetes/) in Netdata Cloud, which
 comes with meaningful visualizations out of the box. 
 
-Read our guide, [_Kubernetes monitoring with Netdata_](/docs/guides/monitor/kubernetes-k8s-netdata.md), for a complete
-walkthrough of Netdata's Kubernetes monitoring capabilities, including a health map of every container in your
-infrastructure, aggregated resource utilization metrics, and application metrics.
+Read our guide, [_Kubernetes monitoring with Netdata: Overview and
+visualizations_](/docs/guides/monitor/kubernetes-k8s-netdata.md), for a complete walkthrough of Netdata's Kubernetes
+monitoring capabilities, including a health map of every container in your infrastructure, aggregated resource
+utilization metrics, and application metrics.
 
 ### Related reference documentation
 
-- [Netdata Cloud · Kubernetes monitoring](https://learn.netdata.cloud/docs/cloud/visualizations/kubernetes/)
+- [Netdata Cloud · Kubernetes monitoring](https://learn.netdata.cloud/docs/cloud/visualize/kubernetes/)
 - [Netdata Helm chart](https://github.com/netdata/helmchart)
 - [Netdata service discovery](https://github.com/netdata/agent-service-discovery/)