From ac15e58573e463854ae3c924fe5e1e891c3d197f Mon Sep 17 00:00:00 2001
From: Aleksandr Arefev <39635005+alexarefev@users.noreply.github.com>
Date: Thu, 16 Nov 2023 09:32:33 +0300
Subject: [PATCH] doc update

---
 documentation/Troubleshooting.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/documentation/Troubleshooting.md b/documentation/Troubleshooting.md
index 83ad08c06..6fda16e77 100644
--- a/documentation/Troubleshooting.md
+++ b/documentation/Troubleshooting.md
@@ -934,7 +934,7 @@ spec:
 
 ### Case 1
 
-**Symptoms**: A pod can't resolve the non-FQDN. Check inside the pod looks the following:
+**Symptoms**: A pod can't resolve a short name. Check inside the pod looks the following:
 
 ```
 $ nslookup kubernetes.default
@@ -947,7 +947,7 @@ Address:        172.30.0.10:53
 
 **Root cause**: Images with `busybox` utility that represents `nslookup` command could have issues with `search` directives in `/etc/resolv.conf`.
 
-**Solution**: Use FQDN instead of that consists of `service` and `namespace` only, e.g.: `kubernetes.default.svc.cluster.local`. In some cases addition `bind-tools` package fixes the issue with short names resolving. More information: 
+**Solution**: Use FQDN instead of short name that consists of `service` and `namespace` only, e.g.: `kubernetes.default.svc.cluster.local` instead of `kubernetes.default`. In some cases addition `bind-tools` package fixes the issue with short names resolving. More information: 
 * [https://github.com/docker-library/busybox/issues/48](https://github.com/docker-library/busybox/issues/48)
 * [https://stackoverflow.com/questions/65181012/does-alpine-have-known-dns-issue-within-kubernetes](https://stackoverflow.com/questions/65181012/does-alpine-have-known-dns-issue-within-kubernetes)