diff --git a/articles/modules/ROOT/pages/tls-ssl-configuration-for-specific-ciphers.adoc b/articles/modules/ROOT/pages/tls-ssl-configuration-for-specific-ciphers.adoc
index c273415b..032a836f 100644
--- a/articles/modules/ROOT/pages/tls-ssl-configuration-for-specific-ciphers.adoc
+++ b/articles/modules/ROOT/pages/tls-ssl-configuration-for-specific-ciphers.adoc
@@ -5,7 +5,7 @@
 :tags: ssl, tls, cipher, security, unix, operations
 :category: security
 
-Per documentation: `dbms.ssl.policy.<policyname>.ciphers` is by default set to the Java platform default allowed cipher suites, which can also be explicitly set to any specific ciphers (separated by ",") to further restrict list of allowed ciphers, thus enabling us to enforce a particular single strong cipher (if needed) and remove any doubt about which cipher gets negotiated and chosen.
+Per documentation: `dbms.ssl.policy.<policyname>.ciphers` is by default set to the Java platform default allowed cipher suites, which can also be explicitly set to any specific ciphers (separated by ",") to further restrict list of allowed ciphers, thus enabling us to enforce a particular single [strong cipher](https://stellastra.com/cipher-suite) (if needed) and remove any doubt about which cipher gets negotiated and chosen.
 
 Also, alternatively and/or additionally, we can also disable ciphers by using the instructions referenced here: https://lightbend.github.io/ssl-config/CipherSuites.html   
 where as an example, you would add the following into neo4j.conf: