🐛 Make IPs match diagram

Signed-off-by: pemontto <939704+pemontto@users.noreply.github.com>
firezone · Oct 28, 2022 · 07d2dbc · 07d2dbc
1 parent 5ad4c8c
commit 07d2dbc
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/docs/docs/user-guides/use-cases/reverse-tunnel.mdx b/docs/docs/user-guides/use-cases/reverse-tunnel.mdx
@@ -26,15 +26,15 @@ Note `PersistentKeepalive` can also be set in on the
 
 Device A
 
-- `AllowedIPs = 10.3.2.2/32`: This is the IP or range of IPs of Device B
+- `AllowedIPs = 10.3.2.3/32`: This is the IP or range of IPs of Device B
 - `PersistentKeepalive = 25` If the device is behind a NAT, this ensures the
   device is able to keep the tunnel alive and continue to receive packets from
   the WireGuard interface. Usually a value of `25` is sufficient, but you may
   need to decrease this value depending on your environment.
 
 Device B
 
-- `AllowedIPs = 10.3.2.3/32`: This is the IP or range of IPs of Device A
+- `AllowedIPs = 10.3.2.2/32`: This is the IP or range of IPs of Device A
 - `PersistentKeepalive = 25`
 
 ## Admin Case - One to Many Nodes