From 2374285f45247d2281afe61d8815c58f55724e84 Mon Sep 17 00:00:00 2001
From: Bill Burke <bburke@redhat.com>
Date: Fri, 27 May 2016 16:37:49 -0400
Subject: [PATCH] sessions

---
 topics/sessions/offline.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/topics/sessions/offline.adoc b/topics/sessions/offline.adoc
index c8bb88aaa1..0de396844d 100644
--- a/topics/sessions/offline.adoc
+++ b/topics/sessions/offline.adoc
@@ -24,7 +24,7 @@ Offline tokens can also be revoked by setting a <<fake/../../sessions/revocation
 To be able to issue an offline token, users need to have the role mapping for the realm-level role `offline_access`.
 Clients also need to have that role in their scope.
 
-The client can request offline token by adding the parameter `scope=offline_access` when sending authorization request to {{book.project.name}.
+The client can request offline token by adding the parameter `scope=offline_access` when sending authorization request to {{book.project.name}}.
 The {{book.project.name}} OIDC client adapter automatically adds this parameter when you use it to access secured URL of your application (ie.
 http://localhost:8080/customer-portal/secured?scope=offline_access ). The Direct Access Grant and Service Accounts also
 support offline tokens if you include `scope=offline_access` in the body of the authentication request.