From 8186f5e311de0ece49dd989a81136f76a13ffaf7 Mon Sep 17 00:00:00 2001 From: Zentex Date: Tue, 3 Feb 2026 22:31:23 +0530 Subject: [PATCH] Fix typos in signatureMint.md documentation - Fixed 'signaute' -> 'signature' in image alt text - Fixed "recover's" -> "recovers" (incorrect apostrophe) --- contracts/prebuilts/token/signatureMint.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/contracts/prebuilts/token/signatureMint.md b/contracts/prebuilts/token/signatureMint.md index e30ba9d0f..ea7ec02f8 100644 --- a/contracts/prebuilts/token/signatureMint.md +++ b/contracts/prebuilts/token/signatureMint.md @@ -17,7 +17,7 @@ Any external party can then present a smart contract implementing the 'signature The following diagram illustrates how the 'signature minting' flow looks like. For example, consider a webapp like [wombo.art](https://www.wombo.art/) which lets a user generate artwork on its website. Once a user has generated artwork on the wombo website, wombo can allow the user to mint their generated artwork as an NFT on wombo's own contract, where wombo can ensure that what the user will mint on wombo's contract is the intended generated artwork. -![signaute-minting-diagram-1.png](/assets/signature-minting-diag-1.png) +![signature-minting-diagram-1.png](/assets/signature-minting-diag-1.png) ### Why we're developing `Signature Minting` @@ -91,7 +91,7 @@ function mintWithSignature(MintRequest calldata req, bytes calldata signature) e | req | The payload / mint request. | | signature | The signature produced by an account signing the mint request. | -The contract implementing the 'signature minting' mechanism first recover's the address of the signer from the given payload i.e. `req` and the `signature`, and verifies that an authorized address has signed off this incoming mint request. +The contract implementing the 'signature minting' mechanism first recovers the address of the signer from the given payload i.e. `req` and the `signature`, and verifies that an authorized address has signed off this incoming mint request. Once verified, tokens are minted according to the information specified in the payload.