superfly · andie787 · Dec 11, 2023 · Dec 11, 2023
diff --git a/getting-started/troubleshooting.html.md b/getting-started/troubleshooting.html.md
@@ -29,7 +29,7 @@ fly settings autoupdate enable
 
 ### Check connectivity with fly doctor
 
-Run some basic connectivity test for things like Wireguard, IP addresses, and local Docker instance:
+Run some basic connectivity test for things like WireGuard, IP addresses, and local Docker instance:
 
 ```
 fly doctor

diff --git a/machines/working-with-machines.html.markerb b/machines/working-with-machines.html.markerb
@@ -53,7 +53,7 @@ If you successfully reach the API, it should respond with a `404 page not found`
 Set these environment variables to make the following commands easier to use.
 
 ```bash
-$ export FLY_API_HOSTNAME="https://api.machines.dev" # set to http://_api.internal:4280 when using Wireguard or `http://127.0.0.1:4280` when using 'flyctl proxy'
+$ export FLY_API_HOSTNAME="https://api.machines.dev" # set to http://_api.internal:4280 when using WireGuard or `http://127.0.0.1:4280` when using 'flyctl proxy'
 $ export FLY_API_TOKEN=$(fly auth token)
 ```
 

diff --git a/reference/architecture.html.md b/reference/architecture.html.md
@@ -27,4 +27,4 @@ Every server in our infrastructure runs a Rust-based proxy named `fly-proxy`. Th
 
 ### Backhaul
 
-If you have users in Dallas, and an available MicroVM in Chicago, we will accept traffic in Dallas, terminate TLS (unless you've disabled that handler), and then connect to your MicroVM over a Wireguard tunnel between datacenters. Wireguard allows us to pass along almost any kind of network connection with very little additional latency.
+If you have users in Dallas, and an available MicroVM in Chicago, we will accept traffic in Dallas, terminate TLS (unless you've disabled that handler), and then connect to your MicroVM over a WireGuard tunnel between datacenters. WireGuard allows us to pass along almost any kind of network connection with very little additional latency.
diff --git a/reference/deploy-tokens.html.md b/reference/deploy-tokens.html.md
@@ -17,4 +17,4 @@ To get started, generate a deploy token on the Tokens tab of your app dashboard.
 FLY_API_TOKEN=$(flyctl tokens create deploy) flyctl deploy
 ```
 
-Whereas API tokens (`fly auth token`) can manage all of your organizations' apps, deploy tokens are limited to a single application. Some organization-wide features like managing Wireguard tunnels are integral to deployments and are also accessible to deploy tokens.
+Whereas API tokens (`fly auth token`) can manage all of your organizations' apps, deploy tokens are limited to a single application. Some organization-wide features like managing WireGuard tunnels are integral to deployments and are also accessible to deploy tokens.
diff --git a/reference/machines.html.markerb b/reference/machines.html.markerb
@@ -26,7 +26,7 @@ This guide assumes that you have flyctl and cURL installed, and have authenticat
 
 ### Connecting via WireGuard
 
-This method requires more setup but gives you direct access to machines over the Wireguard VPN.
+This method requires more setup but gives you direct access to machines over the WireGuard VPN.
 
 First, follow the [instructions](/docs/reference/private-networking/#private-network-vpn) to set up a permanent WireGuard connection to your Fly network. We recommend WireGuard because you can directly test your machines from your local machine.
 
@@ -50,7 +50,7 @@ If you successfully reach the API, it should respond with a `404 page not found`
 
 ### Setting up the environment
 
-If you are using a Wireguard VPN or `fly proxy`,
+If you are using a WireGuard VPN or `fly proxy`,
 set these environment variables to make the following commands easier to use.
 
 ```bash

diff --git a/reference/private-networking.html.md b/reference/private-networking.html.md
@@ -93,7 +93,7 @@ Finally, you can discover all the apps in the organization by requesting the TXT
 |`regions.<appname>.internal`|none|region names<br/> where app is deployed|
 |`<appname>.internal`|app instances<br/> in any region|none
 |`_apps.internal`|none|names of all 6PN<br/> private networking apps<br/> in the same organization|
-|`_peer.internal`|none|names of all wireguard peers|
+|`_peer.internal`|none|names of all WireGuard peers|
 |`<peername>._peer.internal`|IPv6 of peer|none|
 |`_instances.internal`|none|IDs, apps, addresses, and regions<br>of all running instances<br>comma separated|
 |`<value>.<key>.kv._metadata.<appname>.internal`|IPv6 of Machines with matching [metadata](https://community.fly.io/t/dynamic-machine-metadata/13115)|none|
Original file line number	Diff line number	Diff line change
Expand Up		@@ -27,4 +27,4 @@ Every server in our infrastructure runs a Rust-based proxy named `fly-proxy`. Th

		### Backhaul

		If you have users in Dallas, and an available MicroVM in Chicago, we will accept traffic in Dallas, terminate TLS (unless you've disabled that handler), and then connect to your MicroVM over a Wireguard tunnel between datacenters. Wireguard allows us to pass along almost any kind of network connection with very little additional latency.
		If you have users in Dallas, and an available MicroVM in Chicago, we will accept traffic in Dallas, terminate TLS (unless you've disabled that handler), and then connect to your MicroVM over a WireGuard tunnel between datacenters. WireGuard allows us to pass along almost any kind of network connection with very little additional latency.