diff --git a/docs/src/main/asciidoc/discovery-kubernetes-native.adoc b/docs/src/main/asciidoc/discovery-kubernetes-native.adoc
index 5cb34e55..4485a680 100644
--- a/docs/src/main/asciidoc/discovery-kubernetes-native.adoc
+++ b/docs/src/main/asciidoc/discovery-kubernetes-native.adoc
@@ -3,7 +3,7 @@
 Kubernetes itself is capable of (server side) service discovery (see: https://kubernetes.io/docs/concepts/services-networking/service/#discovering-services).
 Using native kubernetes service discovery ensures compatibility with additional tooling, like: istio https://istio.io (service mesh, capable of load balancing, ribbon, circuit breaker, failover and much more).
 
-The caller service just needs to refer to names resolvable in particular kubernetes cluster then. Simplest implementation might use the spring `RestTemplate` referring to fully qualified domain name (FQDN) `http://<service-name>.<namespace>.svc.<cluster>.local:<service-port>`.
+The caller service just needs to refer to names resolvable in particular kubernetes cluster then. Simplest implementation might use the spring `RestTemplate` referring to fully qualified domain name (FQDN) `http://{service-name}.{namespace}.svc.{cluster}.local:{service-port}`.
 
 Additionally, hystrix can be used for: