Add suggestions

Co-authored-by: Sebastian Bernauer <sebastian.bernauer@stackable.de>

Author: Maleware

docs/modules/hbase/pages/troubleshooting/index.adoc

@@ -1,18 +1,19 @@
 = Troubleshooting
 
-== Hbase access with kerberos authentication
+== HBase access with Kerberos authentication
 
-Currently, xref:zookeeper:index.adoc[Zookeeper] is not secured with authentication. This means, if an application tries to connect to Hbase, it would ask the zookeeper quorum to figure the correct nodes to talk to. In a Java world, you would define a `Client` which would carry the kerberos requirements.
+Currently, xref:zookeeper:index.adoc[Zookeeper] stacklets can only be secured using mutual TLS.
+This means, if an application tries to connect to HBase, it would contact Zookeeper to figure the correct HBase nodes to talk to.
+In a Java world, you would define a `Client` which would carry the Kerberos requirements.
 
-However, those requirements might be passed through and thus your client ( e.g. xref:spark-k8s:usage-guide:operations:applications.adoc[SparkApplications] ) would try to authenticate with kerberos at the corresponding Zookeeper endpoint. This will result in a kerberos ( authentication ) error.
+However, those requirements might be passed through and thus your client (e.g. xref:spark-k8s:usage-guide:operations:applications.adoc[SparkApplications]) would try to authenticate with Kerberos at the corresponding Zookeeper endpoint.
+This will result in a Kerberos ( authentication ) error.
 
-To prevent this, you can set a jvm argument like ( again e.g. SparkApplications )
+To prevent this, you can set a JVM argument like this (again e.g. SparkApplications) in all Pods which would like to talk to HBase:
 
 [source,yaml]
 ----
 jvmArgumentOverrides:
-    add:
-        - "-Dzookeeper.sasl.client=false"
+  add:
+    - "-Dzookeeper.sasl.client=false"
 ----
-
-in all pods which would like to talk to Hbase.