diff --git a/topics/enforcer/js-adapter.adoc b/topics/enforcer/js-adapter.adoc
index 41ad068153..3fa54f34d1 100755
--- a/topics/enforcer/js-adapter.adoc
+++ b/topics/enforcer/js-adapter.adoc
@@ -2,7 +2,7 @@
 ==== JavaScript Integration
 
 The {{book.project.name}} Server comes with a JavaScript library you can use to interact with a resource server protected by a policy enforcer.
-This library is based on the {{book.external_link.keycloakjsadapter.link}}[{{book.project.name}} {{book.external_link.keycloakjsadapter.name}}], which can be integrated to allow your client to obtain permissions from a {{book.project.name}} Server.
+This library is based on the link:{{book.external_link.keycloakjsadapter.link}}[{{book.project.name}} {{book.external_link.keycloakjsadapter.name}}], which can be integrated to allow your client to obtain permissions from a {{book.project.name}} Server.
 
 You can obtain this library from a running a {{book.project.name}} Server instance by including the following `script` tag in your web page:
 
diff --git a/topics/getting-started/overview.adoc b/topics/getting-started/overview.adoc
index 5466df3d66..158af6ebef 100644
--- a/topics/getting-started/overview.adoc
+++ b/topics/getting-started/overview.adoc
@@ -9,7 +9,7 @@ To unpack this file run the _unzip_ or _gunzip_ and _tar_ utilities. Throughout
 the demo distribution is referenced as *${KEYCLOAK_DEMO_SERVER_DIR}*.
 
 [NOTE]
-This guide assumes that you are already familiar with {{book.project.name}} and that you are able to install and boot a {{book.project.name}} Server. For more information, see the {{book.external_link.keycloakgettingstarted.link}}[{{book.external_link.keycloakgettingstarted.name}}] tutorials.
+This guide assumes that you are already familiar with {{book.project.name}} and that you are able to install and boot a {{book.project.name}} Server. For more information, see the link:{{book.external_link.keycloakgettingstarted.link}}[{{book.external_link.keycloakgettingstarted.name}}] tutorials.
 
 Ensure you have a {{book.project.name}} instance running; the default configuration is http://localhost:8080/auth[http://localhost:8080/auth]. After logging in to the
 Administration Console, a page similar to this one is displayed: