Merge pull request ipfs#848 from ipfs/add/estuary-to-minty-docs

Adds Estuary link, shuffles around in alpha order. [ciskip]

Author: johnnymatthews

docs/how-to/mint-nfts-with-ipfs.md

@@ -38,9 +38,9 @@ Using the CID, anyone can fetch a copy of the data from the IPFS network as long
 
 Of course, there may be some cases in which you do want to change the metadata for an NFT after it's been published. That's no problem! You'll just need to add support to your smart contract for updating the URI for a token after it's been issued. That will let you change the URI to a new IPFS URI while still leaving a record of the initial version in the blockchain's transaction history. This provides accountability and makes it clear to everyone what was changed, when, and by whom.
 
-## Minty 
+## Minty
 
-To help explain how NFTs and IPFS can work together, we've created Minty - a simple command-line application to automatically _mint_ an NFT and pin it to IPFS using [Pinata](https://pinata.cloud) or [nft.storage](https://nft.storage).
+To help explain how NFTs and IPFS can work together, we've created Minty - a simple command-line application to automatically _mint_ an NFT and pin it to IPFS using [Estuary](https://estuary.tech/), [nft.storage](https://nft.storage), or [Pinata](https://pinata.cloud).
 
 Production NFT platforms are a fairly complex thing. As with any modern web application, there are lots of decisions to make surrounding the tech stack, user interface conventions, API design, and so on. Blockchain-enabled d-apps also need to interact with user wallets such as [Metamask](https://metamask.io), further increasing their complexity.