fix docs

Author: labrenbe

docs/modules/druid/examples/getting_started/druid.yaml

@@ -23,13 +23,13 @@ spec:
       default:
         replicas: 1
     roleConfig:
-      listenerClass: external-stable # This exposes your Stacklet outside of Kubernetes. Remove this configuration if this is not desired
+      listenerClass: external-stable # This exposes this role outside of Kubernetes. Remove this configuration if this is not desired
   coordinators:
     roleGroups:
       default:
         replicas: 1
     roleConfig:
-      listenerClass: external-stable # This exposes your Stacklet outside of Kubernetes. Remove this configuration if this is not desired
+      listenerClass: external-stable # This exposes this role outside of Kubernetes. Remove this configuration if this is not desired
   historicals:
     roleGroups:
       default:
@@ -43,7 +43,7 @@ spec:
       default:
         replicas: 1
     roleConfig:
-      listenerClass: external-stable # This exposes your Stacklet outside of Kubernetes. Remove this configuration if this is not desired
+      listenerClass: external-stable # This exposes this role outside of Kubernetes. Remove this configuration if this is not desired
 ---
 apiVersion: v1
 kind: Secret

docs/modules/druid/pages/usage-guide/listenerclass.adoc

@@ -4,8 +4,8 @@
 Apache Druid offers a web UI and an API, both are exposed by the `router` role.
 The `broker` and `coordinator` roles expose additional API endpoints.
 
-The operator deploys a xref:listener-operator:listener.adoc[Listener] for the the `router`, `broker` and `coordinator` roles.
-The listener defaults to only being accessible from within the Kubernetes cluster, but this can be changed by configuring a listener class
+The operator deploys a xref:listener-operator:listener.adoc[Listener] for the `router`, `broker` and `coordinator` roles.
+The Listener defaults to only being accessible from within the Kubernetes cluster, but this can be changed by configuring a ListenerClass
 for specific roles:
 
 [source,yaml]