Update draft-parecki-oauth-client-id-metadata-document.md

Co-authored-by: Emelia Smith <[email protected]>

Author: aaronpk

draft-parecki-oauth-client-id-metadata-document.md

@@ -226,7 +226,7 @@ This enables clients to avoid sending the user to a dead end, by only redirectin
 
 In addition to the security considerations in OAuth 2.0 Core {{RFC6749}}, and OAuth 2.0 Threat Model and Security Considerations {{RFC6819}}, and {{I-D.draft-ietf-oauth-security-topics}} the additional considerations apply.
 
-## Client ID Metadata Documents for Development Purposes
+## Client ID Metadata Documents for Development Purposes {#documents_for_development}
 
 When developing applications against a service that uses Client ID Metadata Documents, developers often encounter the issue of "how do I serve a Client ID Metadata Document at a https URL whilst developing my application?".