fix reference compilation (#140)

two approvals. editorial. open for a week. non-controvertial.

Co-authored-by: Kristina Yasuda <[email protected]>

openid-4-verifiable-presentations-1_0.md

@@ -238,7 +238,7 @@ This specification defines a new mechanism for the cases when the Wallet wants t
 allow the Verifier to generate a request that matches the technical capabilities of that Wallet.
 To enable this, the Authorization Request can contain a `request_uri_method` parameter with the value `post`
 that signals to the Wallet that it can make an HTTP POST request to the Verifier's `request_uri`
-endpoint with information about its capabilities as defined in {#request_uri_method_post}. The Wallet MAY continue with JAR
+endpoint with information about its capabilities as defined in (#request_uri_method_post). The Wallet MAY continue with JAR
 when it receives `request_uri_method` parameter with the value `post` but does not support this feature.
 
 The Verifier articulates requirements of the Credential(s) that are requested using `presentation_definition` and `presentation_definition_uri` parameters that contain a Presentation Definition JSON object as defined in Section 5 of [@!DIF.PresentationExchange]. Wallet implementations MUST process Presentation Definition JSON object and select candidate Verifiable Credential(s) using the evaluation process described in Section 8 of [@!DIF.PresentationExchange] unless implementing only a credential profile that provides rules on how to evaluate and process [@!DIF.PresentationExchange].