diff --git a/docs/reference/security/securing-communications/separating-node-client-traffic.asciidoc b/docs/reference/security/securing-communications/separating-node-client-traffic.asciidoc
index e911ad529c4..5dd1620c0e4 100644
--- a/docs/reference/security/securing-communications/separating-node-client-traffic.asciidoc
+++ b/docs/reference/security/securing-communications/separating-node-client-traffic.asciidoc
@@ -2,7 +2,7 @@
 [[separating-node-client-traffic]]
 === Separating node-to-node and client traffic
 
-Elasticsearch has the feature of so called {ref}/modules-transport.html#_tcp_transport_profiles[TCP transport profiles]
+Elasticsearch has the feature of so called {ref}/modules-transport.html[TCP transport profiles]
 that allows it to bind to several ports and addresses. {security} extends on this
 functionality to enhance the security of the cluster by enabling the separation
 of node-to-node transport traffic from client transport traffic. This is important
diff --git a/x-pack/docs/en/security/using-ip-filtering.asciidoc b/x-pack/docs/en/security/using-ip-filtering.asciidoc
index 817975c69de..86579f220f1 100644
--- a/x-pack/docs/en/security/using-ip-filtering.asciidoc
+++ b/x-pack/docs/en/security/using-ip-filtering.asciidoc
@@ -78,7 +78,7 @@ xpack.security.http.filter.enabled: true
 [float]
 === Specifying TCP transport profiles
 
-{ref}/modules-transport.html#_tcp_transport_profiles[TCP transport profiles]
+{ref}/modules-transport.html[TCP transport profiles]
 enable Elasticsearch to bind on multiple hosts. {security} enables you to apply
 different IP filtering on different profiles.