diff --git a/nats-on-kubernetes/nats-external-nlb.md b/nats-on-kubernetes/nats-external-nlb.md
index 7f62ff8..e2bcca9 100644
--- a/nats-on-kubernetes/nats-external-nlb.md
+++ b/nats-on-kubernetes/nats-external-nlb.md
@@ -5,7 +5,7 @@ with NATS for external access, sometimes due to policy it might
 help to use one.  If that is the case, then one option would be
 to use an L4 load balancer that has raw tcp support.
 
-In the example below, you can find how to use a [AWS Network Load Balancer](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/introduction.html)
+In the example below, you can find how to use an [AWS Network Load Balancer](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/introduction.html)
 to connect externally to a cluster that has TLS setup.
 
 ```sh
@@ -42,5 +42,5 @@ nats-nlb   LoadBalancer   10.100.67.123   a18b60a948fc611eaa7840286c60df32-9e96a
 $ nats-pub -s nats://a18b60a948fc611eaa7840286c60df32-9e96a2af4b5675ec.elb.us-east-2.amazonaws.com:4222 -creds nsc/nkeys/creds/KO/A/test.creds test.foo bar
 ```
 
-Also, it would be recommended to disable [no_advertise](https://docs.nats.io/nats-server/configuration/clustering/cluster_config) 
+Also, it would be recommended to disable [no_advertise](nats-server/configuration/clustering/cluster_config.md) 
 to avoid gossiping internal addresses from pods in Kubernetes to NATS clients.