docs: use flowing verse on debug page explaining DNS server failures (#45141)

Co-authored-by: Simon Lamon <32477463+silamon@users.noreply.github.com>

Author: robotsnh

source/more-info/unsupported/dns_server.markdown

@@ -5,28 +5,23 @@ description: "More information on why issues with a DNS server marks the install
 
 ## The issue
 
-Home Assistant requires a working DNS server to function. Without one it may be
-unable to provide functionality like checking and executing updates, showing
-documentation, reach external services required by add-ons and integrations, etc.
+Home Assistant requires a working DNS server to function. Without one, it may be unable to provide functionality like checking and executing updates, showing documentation, reaching external services required by add-ons and integrations, and other tasks that depend on internet access.
 
 ## The solution
 
-The easiest solution is to re-enable the fallback DNS option by executing the following
-command in the CLI:
+The easiest solution is to re-enable the fallback DNS option by executing the following command in the CLI:
 
 ```sh
 ha dns options --fallback=true
 ```
 
-Alternatively review your system issues by executing the following command in the
-CLI:
+Alternatively review your system issues by executing the following command in the CLI:
 
 ```sh
 ha resolution info
 ```
 
-You will see one or more issues with a context of `dns_server`. For each such issue,
-take the following actions based on the issue type.
+You will see one or more issues with a context of `dns_server`. For each such issue, take the following actions based on the issue type.
 
 ### `dns_server_failed`
 
@@ -36,23 +31,14 @@ take the following actions based on the issue type.
 
 ### `dns_server_ipv6_error`
 
-If you see this that means the application you are using for DNS is not handling
-A and AAAA requests correctly. You can test this by executing the following commands:
+If you see this, that means the application you are using for DNS is not handling A and AAAA requests correctly. You can test this by executing the following commands:
 
 ```sh
 server="<IP address of DNS server>"
 dig "@$server" _checkdns.home-assistant.io +noall +comments +answer A
 dig "@$server" _checkdns.home-assistant.io +noall +comments +answer AAAA
 ```
 
-A DNS server handling A and AAAA requests correctly will respond with status `NOERROR`
-for both of those queries even though there are no answers for the AAAA request.
-A DNS server mishandling this request will only return a `NOERROR` response for
-the first one and will return `NXDOMAIN`, `REFUSED`, `SERVFAIL` or some other error
-status for the second.
-
-It is important to use a DNS server that handles this situation correctly since
-Home Assistant uses alpine for many of its containers. Alpine follows the DNS spec
-and will treat the entire domain as if it can't be resolved if it receives an error
-status for either query. Home Assistant will run into many unexpected issues in
-this situation, particularly around updates and installing software.
+A DNS server handling A and AAAA requests correctly will respond with status `NOERROR` for both of those queries even though there are no answers for the AAAA request. A DNS server mishandling this request will only return a `NOERROR` response for the first one and will return `NXDOMAIN`, `REFUSED`, `SERVFAIL` or some other error status for the second.
+
+It is important to use a DNS server that handles this situation correctly since Home Assistant uses Alpine Linux for many of its containers. Alpine follows the DNS spec and will treat the entire domain as if it can't be resolved if it receives an error status for either query. Home Assistant will run into many unexpected issues in this situation, particularly around updates and installing software.