diff --git a/app/_src/policies/meshtrafficpermission.md b/app/_src/policies/meshtrafficpermission.md index 41e45215e..713096dda 100644 --- a/app/_src/policies/meshtrafficpermission.md +++ b/app/_src/policies/meshtrafficpermission.md @@ -16,7 +16,7 @@ it should not be mixed with [TrafficPermission](/docs/{{ page.version }}/policie | MeshService | ✅ | ❌ | ✅ | | MeshServiceSubset | ✅ | ❌ | ✅ | -If you don't understand this table you should read [matching docs](/docs/{{ page.version }}/policies/targetRef). +If you don't understand this table you should read [matching docs](/docs/{{ page.version }}/policies/targetref). ## Configuration diff --git a/app/_src/production/cp-deployment/zoneproxy-auth.md b/app/_src/production/cp-deployment/zoneproxy-auth.md index 1f351040d..e8d475679 100644 --- a/app/_src/production/cp-deployment/zoneproxy-auth.md +++ b/app/_src/production/cp-deployment/zoneproxy-auth.md @@ -312,4 +312,4 @@ can impersonate any service. ## Legacy Zone Ingress Token -Authenticating Zone Ingress using [separate Zone Ingress Token](/docs/1.8.x/security/zone-ingress-auth/) is still possible, but it is deprecated and will be removed in the future. +Authenticating Zone Ingress using [separate Zone Ingress Token](https://kuma.io/docs/1.8.x/security/zone-ingress-auth/) is still possible, but it is deprecated and will be removed in the future. diff --git a/app/docs/2.0.x/security/zoneproxy-auth.md b/app/docs/2.0.x/security/zoneproxy-auth.md index f19789a39..e2778a038 100644 --- a/app/docs/2.0.x/security/zoneproxy-auth.md +++ b/app/docs/2.0.x/security/zoneproxy-auth.md @@ -211,4 +211,4 @@ can impersonate any service. ## Legacy Zone Ingress Token -Authenticating Zone Ingress using [separate Zone Ingress Token](/docs/1.8.x/security/zone-ingress-auth/) is still possible, but it is deprecated and will be removed in the future. +Authenticating Zone Ingress using [separate Zone Ingress Token](https://kuma.io/docs/1.8.x/security/zone-ingress-auth/) is still possible, but it is deprecated and will be removed in the future.