add CAIP-25 normref to eip-5792

EIPS/eip-5792.md

@@ -201,7 +201,8 @@ This method SHOULD return an error if the user has not already authorized a conn
 
 We expect the community to align on the definition of additional capabilities in separate ERCs over time.
 
-Note that in addition to, or instead of, querying the wallet directly for capabilities, the same capability objects MAY be exposed out-of-band, such as in a `sessionProperty.capabilities` object persisted in a CAIP-25-conformant wallet provider interface, or in a well-known location (such as a URL derived from an [EIP-6963](./eip-6963.md) `rdns` identifier). Provider abstractions MAY also cache capabilities from previous requests or otherwise inject them from out-of-band to facilitate better user experience.
+Note that in addition to, or instead of, querying the wallet directly for capabilities, the same capability objects MAY be exposed out-of-band, such as in a `sessionProperty.capabilities` object persisted in a [CAIP-25](https://github.com/ChainAgnostic/CAIPs/blob/ad0cfebc45a4b8368628340bf22aefb2a5edcab7/CAIPs/caip-25.md)-conformant wallet provider interface, or in a well-known location (such as a URL derived from an [EIP-6963](./eip-6963.md) `rdns` identifier).
+Provider abstractions MAY also cache capabilities from previous requests or otherwise inject them from out-of-band to facilitate better user experience.
 If any of these supplemental expressions of capabilities are contradicted by capabilities expressed in live wallet RPC responses, these latter values SHOULD be taken as the canonical and current expression of capabilities.
 
 #### `wallet_getCapabilities` RPC Specification