clarify second hop issue in docs (#12)

README.md

@@ -14,14 +14,14 @@ Other Terraform providers have implemented similar functionality, but they eithe
 running PowerShell or utilize WinRM to execute PowerShell remotely. In many environments, this is not preferable or
 possible.
 
-The PowerShell module, which this and other providers rely on
-[DnsService](https://learn.microsoft.com/en-us/powershell/module/dnsserver/?view=windowsserver2022-ps)
-is using WinRM internally as the transport when talking to the DNS Server.
+This, and other similar providers are configuring Windows DNS servers using the PowerShell module
+[DnsService](https://learn.microsoft.com/en-us/powershell/module/dnsserver/?view=windowsserver2022-ps).
+This module uses WinRM internally when talking to the DNS Server.
 
-In an environment where the DNS server is running on a locked down Domain Controller with WinRM is disabled, one will thus
-run into problems with second hop WinRM. We have not been able to find a solution to making the second hop securely and easily.
+In an environment where the DNS server is running on a locked-down Domain Controller with WinRM disabled, one will thus
+run into problems with the second hop WinRM when going through a jump host. We have yet to find a solution to making the second WinRM hop secure and easily.
 
-This provider avoids the whole second hop problem by using SSH as the transport for the first hop when running PowerShell.
+This provider avoids the whole second hop concern by using SSH as the transport for the first hop when running PowerShell.
 
 
 ## Getting started

docs/index.md

@@ -22,15 +22,14 @@ Other Terraform providers have implemented similar functionality, but they eithe
 running PowerShell or utilize WinRM to execute PowerShell remotely. In many environments, this is not preferable or
 possible.
 
-The PowerShell module, which this and other providers rely on
-[DnsService](https://learn.microsoft.com/en-us/powershell/module/dnsserver/?view=windowsserver2022-ps)
-is using WinRM internally as the transport when talking to the DNS Server.
+This, and other similar providers are configuring Windows DNS servers using the PowerShell module
+[DnsService](https://learn.microsoft.com/en-us/powershell/module/dnsserver/?view=windowsserver2022-ps).
+This module uses WinRM internally when talking to the DNS Server.
 
-In an environment where the DNS server is running on a locked down Domain Controller with WinRM is disabled, one will thus 
-run into problems with second hop WinRM. We have not been able to find a solution to making the second hop securely and easily.
-
-This provider avoids the whole second hop problem by using SSH as the transport for the first hop when running PowerShell.
+In an environment where the DNS server is running on a locked-down Domain Controller with WinRM disabled, one will thus
+run into problems with the second hop WinRM when going through a jump host. We have yet to find a solution to making the second WinRM hop secure and easily.
 
+This provider avoids the whole second hop concern by using SSH as the transport for the first hop when running PowerShell.
 
 <!-- schema generated by tfplugindocs -->
 ## Schema