Apply suggestions from code review

Co-authored-by: Jeff Boruszak <[email protected]>

website/content/docs/services/discovery/dns-forwarding/enable.mdx

@@ -413,7 +413,7 @@ The configuration informs the macOS resolver daemon to forward all `.consul` TLD
 
 ## Next steps
 
-This guide helped you configure your node DNS to forward requests to Consul.
+This instructions on this page helped you configure your node to forward DNS requests to Consul.
 
 To learn more on how to query Consul DNS once forwarding is enabled, refer to [DNS forwarding workflow](/consul/docs/services/discovery/dns-forwarding#workflow).
 

website/content/docs/services/discovery/dns-forwarding/index.mdx

@@ -19,21 +19,23 @@ When configured with default values, Consul exposes the DNS interface on port `8
 
 Instead of running Consul with an administrative or root account, you can forward appropriate queries to Consul, running on an unprivileged port, from another DNS server or using port redirect.
 
-There are two possible configurations for DNS forwarding:
+There are two configurations for a node's DNS forwarding behavior:
  - **Conditional DNS forwarding**: the local DNS servers are configured to forward to Consul only queries relative to the `.consul` zone. All other queries are still served via the default DNS server in the node.
- - **DNS forwarding**: Consul serves all DNS queries and forwards to a remote DNS server the ones outside `.consul` domain.
+ - **Full DNS forwarding**: Consul serves all DNS queries and forwards to a remote DNS server the ones outside `.consul` domain.
 
 ### Conditional DNS forwarding
 
-We recommend the conditional DNS forwarding approach. 
+We recommend the conditional DNS forwarding approach. This configuration lowers the Consul agent's resource consumption by limiting the number of DNS requests it handles. 
 
 ![Consul DNS conditional forwarding - Only .consul requests are routed to Consul](/img/consul-dns-conditional-forwarding.png)
 
 In this configuration, Consul only serves queries relative to the `.consul` domain. There is no unnecessary load on Consul servers to serve queries from different domains.
 
+This behavior is not enabled by default.
+
 ### DNS forwarding
 
-This approach can be useful in scenarios where the Consul agent nodes have low resources, and you want to avoid the overhead of running a local DNS server. In this configuration, Consul serves all DNS queries for all domains and forwards the ones outside the `.consul` domain to one or more configured forwarder servers.
+This approach can be useful in scenarios where the Consul agent's node is allocated limited resources and you want to avoid the overhead of running a local DNS server. In this configuration, Consul serves all DNS queries for all domains and forwards the ones outside the `.consul` domain to one or more configured forwarder servers.
 
 ![Consul DNS forwarding - All requests are routed to Consul](/img/consul-dns-forwarding.png)
 
@@ -176,7 +178,7 @@ error (no valid DS) resolving
 
 </CodeBlockConfig>
 
-This indicates that `DNSSEC` is not disabled properly.
+This error indicates that `DNSSEC` is not disabled properly.
 
-If you see errors about network connections, verify that there are no firewall
+If you receive errors about network connections, verify that there are no firewall
 or routing problems between the servers running BIND and Consul.