diff --git a/docs/src/main/asciidoc/tls-registry-reference.adoc b/docs/src/main/asciidoc/tls-registry-reference.adoc
index 86f9a23cc39b6..390d66e3c14c2 100644
--- a/docs/src/main/asciidoc/tls-registry-reference.adoc
+++ b/docs/src/main/asciidoc/tls-registry-reference.adoc
@@ -28,7 +28,15 @@ endif::no-reactive-routes[]
 .
 
 As a result, applications that use the TLS Registry can be ready to handle secure communications out of the box.
-TLS Registry also provides features like automatic certificate reloading, Let's Encrypt (ACME) integration, Kubernetes Cert-Manager support, and compatibility with various keystore formats, such as PKCS12, PEM, and JKS.
+
+TLS Registry also provides automatic certificate reloading
+ifndef::no-lets-encrypt[]
+, integration with Let's Encrypt (ACME)
+endif::no-lets-encrypt[]
+ifndef::no-kubernetes-secrets-or-cert-manager[]
+, support for Kubernetes Cert-Manager,
+endif::no-kubernetes-secrets-or-cert-manager[]
+and compatibility with various keystore formats, such as PKCS12, PEM, and JKS.
 
 [[using-the-tls-registry]]
 == Using the TLS registry