Remove specific number and change sd text

docs/guides/monitor/kubernetes-k8s-netdata.md

@@ -28,13 +28,13 @@ your k8s infrastructure.
 
 -   A [Helm chart](https://github.com/netdata/helmchart), which bootstraps a Netdata Agent pod on every node in your
     cluster, plus an additional parent pod for storing metrics and managing alarm notifications.
--   A [service discovery plugin](https://github.com/netdata/agent-service-discovery), which discovers and immediately
-    monitors 23 specific services, plus any endpoints covered by our [generic Prometheus
-    collector](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/prometheus), that might be running
-    inside of your cluster's pods. Service discovery happens without manual intervention as pods are created, destroyed,
-    or moved between nodes. [Compatible
-    services](https://github.com/netdata/helmchart#service-discovery-and-supported-services) include Nginx, Apache,
-    MySQL, CoreDNS, and much more.
+-   A [service discovery plugin](https://github.com/netdata/agent-service-discovery), which discovers and creates
+    configuration files for [compatible
+    applications](https://github.com/netdata/helmchart#service-discovery-and-supported-services) and any endpoints
+    covered by our [generic Prometheus
+    collector](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/prometheus). With these
+    configuration file, Netdata can monitor any of these applications as they run _inside_ of a pod. Service discovery
+    happens without manual intervention as pods are created, destroyed, or moved between nodes. 
 -   A [Kubelet collector](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/k8s_kubelet), which runs
     on each node in a k8s cluster to monitor the number of pods/containers, the volume of operations on each container,
     and more.
@@ -145,9 +145,9 @@ Thanks to Netdata's service discovery feature, you monitor containerized applica
 configuration or manual intervention. Service discovery is like a watchdog for created or deleted pods, recognizing the
 service they run based on the image name and port and immediately attempting to apply a logical default configuration.
 
-Service configuration supports [23
-services](https://github.com/netdata/helmchart#service-discovery-and-supported-services), plus any endpoints covered by
-our [generic Prometheus collector](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/prometheus),
+Service configuration supports [popular
+applications](https://github.com/netdata/helmchart#service-discovery-and-supported-services), plus any endpoints covered
+by our [generic Prometheus collector](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/prometheus),
 which are automatically added or removed from Netdata as soon as the pods are created or destroyed.
 
 You can find these service discovery sections near the bottom of the menu. The names for these sections follow a