diff --git a/securing_apps/book-product.json b/securing_apps/book-product.json
index a366037184..caf9c07f60 100755
--- a/securing_apps/book-product.json
+++ b/securing_apps/book-product.json
@@ -12,10 +12,10 @@
     "title": "Securing Applications and Services Guide",
     "project": {
       "name": "Red Hat Single Sign-On",
-      "version": "7.1.0",
+      "version": "7.1",
       "versionMvn": "2.4.0.Final-redhat-1",
       "doc_base_url": "https://access.redhat.com/documentation/en/red-hat-single-sign-on/",
-      "doc_info_version_url": "7.1-Beta"
+      "doc_info_version_url": "7.1"
     },
     "community": false,
     "product": true,
diff --git a/securing_apps/topics/oidc/java/client-authentication.adoc b/securing_apps/topics/oidc/java/client-authentication.adoc
index a3a2a82406..d23507fd0a 100644
--- a/securing_apps/topics/oidc/java/client-authentication.adoc
+++ b/securing_apps/topics/oidc/java/client-authentication.adoc
@@ -22,7 +22,7 @@ This is based on the https://tools.ietf.org/html/rfc7523[RFC7523] specification.
 
 * The client must have the private key and certificate. For  {{book.project.name}} this is available through the traditional `keystore` file, which is either available on the client application's classpath or somewhere on the file system.
 
-* Once the client application is started, it allows to download it's public key in https://self-issued.info/docs/draft-ietf-jose-json-web-key.html[JWKS] format using a URL such as \http://myhost.com/myapp/k_jwks, assuming that \http://myhost.com/myapp is the base URL of your client application. This URL can be used by {{book.project.name}} (see below).
+* Once the client application is started, it allows to download its public key in https://self-issued.info/docs/draft-ietf-jose-json-web-key.html[JWKS] format using a URL such as \http://myhost.com/myapp/k_jwks, assuming that \http://myhost.com/myapp is the base URL of your client application. This URL can be used by {{book.project.name}} (see below).
 
 * During authentication, the client generates a JWT token and signs it with its private key and sends it to {{book.project.name}} in
 the particular backchannel request (for example, code-to-token request) in the `client_assertion` parameter.
diff --git a/securing_apps/topics/oidc/java/fuse/install-feature.adoc b/securing_apps/topics/oidc/java/fuse/install-feature.adoc
index c020882162..32b26d0941 100644
--- a/securing_apps/topics/oidc/java/fuse/install-feature.adoc
+++ b/securing_apps/topics/oidc/java/fuse/install-feature.adoc
@@ -70,7 +70,7 @@ cd /path-to-fuse/jboss-fuse-6.3.0.redhat-198
 unzip -q /path-to-adapter-zip/keycloak-fuse-adapter-dist-2.5.4.Final.zip
 {% endif %}
 {% if book.product %}
-unzip -q /path-to-adapter-zip/rh-sso-{{book.project.version}}-fuse-adapter.zip
+unzip -q /path-to-adapter-zip/rh-sso-7.1.0-fuse-adapter.zip
 {% endif %}
 ----
 . Start Fuse and run these commands in the fuse/karaf terminal: