From ec7930545fbc598c94ef40b3ef2601ddc6fb79e3 Mon Sep 17 00:00:00 2001
From: Chinmay Patel <chinmay@chinmay.ca>
Date: Tue, 4 Aug 2020 10:15:10 -0400
Subject: [PATCH] Clarity on the JSON object conversion for validation.

---
 docs/signedCredentials.rst | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/docs/signedCredentials.rst b/docs/signedCredentials.rst
index 13a4ca23..410d3923 100644
--- a/docs/signedCredentials.rst
+++ b/docs/signedCredentials.rst
@@ -107,6 +107,9 @@ Taking a look at the newly created credential, we can indeed see that the ``subj
       creator: 'did:jolo:b2d5d8d6cc140033419b54a237a5db51710439f9f462d1fc98f698eca7ce9777#keys-1'
       ...
   }
+  
+.. note:: Most likely, this credential will be generated locally and will be passed to the other party to validate the credential. In order to pass the credential in a JSON format, we can convert the local credential using `emailAddressSignedCredential.toJSON()`.
+
 
 Validate a signature on a signed credential
 #############################################