aboutsummaryrefslogtreecommitdiffstatshomepage
diff options
context:
space:
mode:
authorJason A. Donenfeld <Jason@zx2c4.com>2021-10-21 00:14:32 -0600
committerJason A. Donenfeld <Jason@zx2c4.com>2021-10-21 01:51:40 -0600
commite0a59b207f17fc4deb03ece1da8b7e8aa1000f8a (patch)
tree81595ae93abb79701da4579c7324bb2fdb70aada
parentbuild: stop building for arm32 (diff)
downloadwireguard-windows-e0a59b207f17fc4deb03ece1da8b7e8aa1000f8a.tar.xz
wireguard-windows-e0a59b207f17fc4deb03ece1da8b7e8aa1000f8a.zip
docs: fix typo in netquirk
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
-rw-r--r--docs/netquirk.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/netquirk.md b/docs/netquirk.md
index 5c676f6f..d53c8cdb 100644
--- a/docs/netquirk.md
+++ b/docs/netquirk.md
@@ -30,4 +30,4 @@ Windows assigns a unique GUID to each new WireGuard adapter. The application tak
### Adapter Lifetime
-WireGuard's network adapter is created dynamically when a tunnel is started and destroyed when a tunnel is stopped. This means that additional filters, address families, or protocols should be bound to the adapter programmatically, possibly through use of dangerous script execution in thet configuration file or by way of automatic NDIS layer binding.
+WireGuard's network adapter is created dynamically when a tunnel is started and destroyed when a tunnel is stopped. This means that additional filters, address families, or protocols should be bound to the adapter programmatically, possibly through use of dangerous script execution in the configuration file or by way of automatic NDIS layer binding.