fixes

Consensys · Jul 19, 2024 · 410f7b4 · 410f7b4
1 parent 81288e1
commit 410f7b4
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/docs/how-to/find-and-connect/improve-connectivity.md b/docs/how-to/find-and-connect/improve-connectivity.md
@@ -12,7 +12,7 @@ While Teku is good at finding peers, changes to your network configuration can h
 
 ## Advertise your public IP address
 
-If you are using a NAT, it's easier to get peers by advertising your public address to the network. Use the [`--p2p-advertised-ip`](../../reference/cli/index.md#p2p-advertised-ip) option to advertise the address publicly.
+If you are using a NAT, it's easier to get peers by advertising your public address to the network. Use the [`--p2p-advertised-ip`](../../reference/cli/index.md#p2p-advertised-ip-p2p-advertised-ips) option to advertise the address publicly.
 
 Additionally, if on a home network, [configure port forwarding](#configuring-ports) on your router.
 

diff --git a/docs/how-to/find-and-connect/specify-nat.md b/docs/how-to/find-and-connect/specify-nat.md
@@ -24,6 +24,6 @@ UPnP support is often disabled by default in networking firmware. If disabled by
 
 ## None
 
-Specify `NONE` to explicitly configure the external IP address and ports advertised using [`--p2p-advertised-ip`](../../reference/cli/index.md#p2p-advertised-ip) and [`--p2p-advertised-port`](../../reference/cli/index.md#p2p-advertised-port) for the P2P service.
+Specify `NONE` to explicitly configure the external IP address and ports advertised using [`--p2p-advertised-ip`](../../reference/cli/index.md#p2p-advertised-ip-p2p-advertised-ips) and [`--p2p-advertised-port`](../../reference/cli/index.md#p2p-advertised-port) for the P2P service.
 
 Manually configure your firewall to allow external hosts to create inbound connections to Teku.
diff --git a/docs/how-to/troubleshoot/network.md b/docs/how-to/troubleshoot/network.md
@@ -70,7 +70,7 @@ View the [Prysm guide](https://docs.prylabs.network/docs/prysm-usage/p2p-host-ip
 ### Advertised IP address issues
 
 A possible reason for incoming peers being unable to connect could be an incorrect address specified using the
-[`--p2p-advertised-ip`](../../reference/cli/index.md#p2p-advertised-ip) option. Teku auto-detects the address to use by
+[`--p2p-advertised-ip`](../../reference/cli/index.md#p2p-advertised-ip-p2p-advertised-ips) option. Teku auto-detects the address to use by
 default, so most users won't need to use this option. If you're experiencing issues with incoming peers despite having
 correct firewall and forwarding settings, this could potentially be the cause.