/docs/reference/glossary/service-registry.md

[SataQiu]

Source File: /docs/reference/glossary/service-registry.md Diff:

 diff --git a/content/en/docs/reference/glossary/service-registry.md b/content/en/docs/reference/glossary/service-registry.md
index 5f6791f94..829d1aa98 100644
--- a/content/en/docs/reference/glossary/service-registry.md
+++ b/content/en/docs/reference/glossary/service-registry.md
@@ -2,12 +2,12 @@
 title: Service Registry
 ---

-Istio maintains an internal service registry containing the set of [services](#service),
-and their corresponding [service endpoints](#service-endpoint), running in a service mesh.
-Istio uses the service registry to generate [Envoy](#envoy) configuration.
+Istio maintains an internal service registry containing the set of [services](/docs/reference/glossary/#service),
+and their corresponding [service endpoints](/docs/reference/glossary/#service-endpoint), running in a service mesh.
+Istio uses the service registry to generate [Envoy](/docs/reference/glossary/#envoy) configuration.

 Istio does not provide [service discovery](https://en.wikipedia.org/wiki/Service_discovery),
-although most services are automatically added to the registry by [Pilot](#pilot)
+although most services are automatically added to the registry by [Pilot](/docs/reference/glossary/#pilot)
 adapters that reflect the discovered services of the underlying platform (Kubernetes, Consul, plain DNS).
 Additional services can also be registered manually using a
 [`ServiceEntry`](/docs/concepts/traffic-management/#service-entries) configuration.

[AsCat]

/accept

[mesher-bot]

Thank you @AsCat, this issue had been assigned to you.

[AsCat]

/pushed