From 5dee13007baa906f9411ab1813045000f80e0045 Mon Sep 17 00:00:00 2001
From: NathanB_Amaron <46598074+Nathan-Beirens-Amaron@users.noreply.github.com>
Date: Fri, 15 Feb 2019 14:43:02 +0100
Subject: [PATCH] Update client-registration.adoc

Add missing ',' to avoid confusion.
---
 securing_apps/topics/client-registration.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/securing_apps/topics/client-registration.adoc b/securing_apps/topics/client-registration.adoc
index 95e449759f..8d11cecaf7 100644
--- a/securing_apps/topics/client-registration.adoc
+++ b/securing_apps/topics/client-registration.adoc
@@ -61,7 +61,7 @@ Authorization: bearer eyJhbGciOiJSUz...
 When you create a client through the Client Registration Service the response will include a registration access token.
 The registration access token provides access to retrieve the client configuration later, but also to update or delete the client.
 The registration access token is included with the request in the same way as a bearer token or initial access token.
-Registration access tokens are only valid once when it's used the response will include a new token. 
+Registration access tokens are only valid once, when it's used the response will include a new token. 
 
 If a client was created outside of the Client Registration Service it won't have a registration access token associated with it.
 You can create one through the admin console. This can also be useful if you loose the token for a particular client.