diff --git a/index.bs b/index.bs
index 5b0785b..b286c37 100644
--- a/index.bs
+++ b/index.bs
@@ -160,6 +160,8 @@ OAuth and OIDC require the Client application to identify itself to the OP and R
 [client identifier](https://tools.ietf.org/html/rfc6749#section-2.2) (Client ID). Solid applications
 SHOULD use a URI that can be dereferenced as a [Client ID Document](#clientids-document).
 
+Issue(78):
+
 ## Client ID Document ## {#clientids-document}
 
 When a Client Identifier is dereferenced, the resource MUST be serialized as an `application/ld+json` document
@@ -201,6 +203,8 @@ This example uses [JSON-LD ](https://www.w3.org/TR/json-ld11/) for the Client ID
     </pre>
 </div>
 
+Issue(95):
+
 ### JSON-LD context ### {#jsonld-context}
 
 This specification defines a JSON-LD context for use with OIDC Client ID Documents. This context is
@@ -248,6 +252,10 @@ The WebID Profile Document MUST include one or more statements matching the OIDC
 
 Issue(80):
 
+Issue(92):
+
+Issue(91):
+
 ### OIDC Issuer Discovery via Link Headers ### {#oidc-issuer-discovery-link-headers}
 
 A server hosting a WebID Profile Document MAY transmit the `http://www.w3.org/ns/solid/terms#oidcIssuer`
@@ -330,6 +338,10 @@ With the `webid` scope, the DPoP-bound OIDC ID Token payload MUST contain these
     </pre>
 </div>
 
+Issue(26):
+
+Issue(47):
+
 ### ID Token Validation ### {#id-token-validation}
 
 An ID Token must be validated according to [OIDC.Core, Section 3.1.3.7](https://openid.net/specs/openid-connect-core-1_0.html#IDTokenValidation)