From 535a61e2a130a8124dfc528766c5ba3ce6a6a12d Mon Sep 17 00:00:00 2001 From: Jamil Date: Thu, 7 Mar 2024 10:57:38 -0800 Subject: [PATCH] chore(docs): Fix typo in Deploy -> Configure DNS (#4034) --- website/src/app/kb/deploy/dns/readme.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/website/src/app/kb/deploy/dns/readme.mdx b/website/src/app/kb/deploy/dns/readme.mdx index 8d91e9131..50a39c1a6 100644 --- a/website/src/app/kb/deploy/dns/readme.mdx +++ b/website/src/app/kb/deploy/dns/readme.mdx @@ -50,9 +50,9 @@ further below. ## Configuring Client DNS upstream resolvers -Upstream DNS in Client can be configured with the servers of your choosing so -that all queries on Client devices will be forwarded to the servers you specify -for all non-Firezone resources. +Upstream DNS in all Clients can be configured with the servers of your choosing +so that all queries on Client devices will be forwarded to the servers you +specify for all non-Firezone resources. Go to `Settings` -> `DNS` and enter IPv4 and/or IPv6 servers to use as fallback resolvers. Firezone Clients will use these servers in the order they are defined @@ -63,8 +63,8 @@ for any query that doesn't match a Resource the user has access to. DNS-over-HTTPS upstream servers are not supported yet. -If no custom resolvers are configured, Firezone Clients will fall back to their -default system resolver, typically set by the DHCP server of their local +If no custom resolvers are configured, Firezone Clients will fall back to the +default system resolvers, typically set by the DHCP server of their local network.