Update get kibana guide in troubleshooting docs (#87075)

docs/reference/tab-widgets/troubleshooting/data/diagnose-unassigned-shards.asciidoc

@@ -25,9 +25,9 @@ In order to diagnose the unassigned shards, follow the next steps:
 
 NOTE:
 If the name of your deployment is disabled your {kib} instances might be
-unhealthy, in which case please contact https://support.elastic.co[Elastic Support],
-or your deployment doesn't include {kib}, in which case all you need to do is 
-{cloud}/ec-access-kibana.html[enable Kibana first].
+unhealthy, in which case please contact https://support.elastic.co[Elastic Support].
+If your deployment doesn't include {kib}, all you need to do is 
+{cloud}/ec-access-kibana.html[enable it first].
 
 . Open your deployment's side navigation menu (placed under the Elastic logo in the upper left corner)
 and go to **Dev Tools > Console**.

docs/reference/tab-widgets/troubleshooting/data/enable-cluster-allocation.asciidoc

@@ -18,9 +18,9 @@ We'll achieve this by inspecting the system-wide `cluster.routing.allocation.ena
 
 NOTE:
 If the name of your deployment is disabled your {kib} instances might be
-unhealthy, in which case please contact https://support.elastic.co[Elastic Support],
-or your deployment doesn't include {kib}, in which case all you need to do is 
-{cloud}/ec-access-kibana.html[enable Kibana first].
+unhealthy, in which case please contact https://support.elastic.co[Elastic Support].
+If your deployment doesn't include {kib}, all you need to do is 
+{cloud}/ec-access-kibana.html[enable it first].
 
 . Open your deployment's side navigation menu (placed under the Elastic logo in the upper left corner)
 and go to **Dev Tools > Console**.

docs/reference/tab-widgets/troubleshooting/data/enable-index-allocation.asciidoc

@@ -36,9 +36,9 @@ assignemnt of the shards to `all`.
 
 NOTE:
 If the name of your deployment is disabled your {kib} instances might be
-unhealthy, in which case please contact https://support.elastic.co[Elastic Support],
-or your deployment doesn't include {kib}, in which case all you need to do is 
-{cloud}/ec-access-kibana.html[enable Kibana first].
+unhealthy, in which case please contact https://support.elastic.co[Elastic Support].
+If your deployment doesn't include {kib}, all you need to do is 
+{cloud}/ec-access-kibana.html[enable it first].
 
 . Open your deployment's side navigation menu (placed under the Elastic logo in the upper left corner)
 and go to **Dev Tools > Console**.

docs/reference/tab-widgets/troubleshooting/data/increase-cluster-shard-limit.asciidoc

@@ -39,9 +39,9 @@ We'll achieve this by inspecting the system-wide `cluster.routing.allocation.tot
 
 NOTE:
 If the name of your deployment is disabled your {kib} instances might be
-unhealthy, in which case please contact https://support.elastic.co[Elastic Support],
-or your deployment doesn't include {kib}, in which case all you need to do is 
-{cloud}/ec-access-kibana.html[enable Kibana first].
+unhealthy, in which case please contact https://support.elastic.co[Elastic Support].
+If your deployment doesn't include {kib}, all you need to do is 
+{cloud}/ec-access-kibana.html[enable it first].
 
 . Open your deployment's side navigation menu (placed under the Elastic logo in the upper left corner)
 and go to **Dev Tools > Console**.

docs/reference/tab-widgets/troubleshooting/data/migrate-to-data-tiers-routing-guide.asciidoc

@@ -16,9 +16,9 @@ the index templates and ILM policies if needed.
 
 NOTE:
 If the name of your deployment is disabled your {kib} instances might be
-unhealthy, in which case please contact https://support.elastic.co[Elastic Support],
-or your deployment doesn't include {kib}, in which case all you need to do is 
-{cloud}/ec-access-kibana.html[enable Kibana first].
+unhealthy, in which case please contact https://support.elastic.co[Elastic Support].
+If your deployment doesn't include {kib}, all you need to do is 
+{cloud}/ec-access-kibana.html[enable it first].
 
 . Open your deployment's side navigation menu (placed under the Elastic logo in the upper left corner)
 and go to **Dev Tools > Console**.

docs/reference/tab-widgets/troubleshooting/data/total-shards-per-node.asciidoc

@@ -39,9 +39,9 @@ indices that have shards unassigned.
 
 NOTE:
 If the name of your deployment is disabled your {kib} instances might be
-unhealthy, in which case please contact https://support.elastic.co[Elastic Support],
-or your deployment doesn't include {kib}, in which case all you need to do is 
-{cloud}/ec-access-kibana.html[enable Kibana first].
+unhealthy, in which case please contact https://support.elastic.co[Elastic Support].
+If your deployment doesn't include {kib}, all you need to do is 
+{cloud}/ec-access-kibana.html[enable it first].
 
 . Open your deployment's side navigation menu (placed under the Elastic logo in the upper left corner)
 and go to **Dev Tools > Console**.