Link schema examples on spec

Signed-off-by: ehanoc <[email protected]>

ARCs/arc-0052.md

@@ -109,7 +109,7 @@ The function should check if the data, before and after decoding, isn't a regula
   - `keyIndex`: The key index to be used for key derivation.
   - `metadata`: Object to describe the type of data that is being signed. It should specify the encoding used (i.e msgpack, cbor, etc) and a schema so that the wallet can decode it to show the user.
     - `encoding`: The encoding used for the data
-    - `schema`: The schema of the data in the form of a JSON schema. The schemas are an powerful tool for wallet providers to be able to enforce the type and format of the data that is being signed. 
+    - `schema`: The schema of the data in the form of a JSON schema. The schemas are an powerful tool for wallet providers to be able to enforce the type and format of the data that is being signed. You can check schema examples [here](../assets/arc-0052/schemas/)
 - **returns**: Byte array containing the signature. The signature is encoded as a 64-byte array (32 + 32 bytes). It holds a compressed point R + the integer s (confirming that the signer knows the msg and the privKey).
   - Throws error if data doesn't match the schema