docs: verify changes

The following changes have been applied:

* small textual changes
* reordered the guides - verifying a contract after deploying a contract
  makes sense, but I think verifying a deployment makes more sense as
  the last thing you do with Ignition (after visualizing and tests)
* remove infura as a mentioned option due to NomicFoundation/hardhat-ignition#633
* renamed to `Verifying your deployment`

Author: kanej

docs/src/content/ignition/docs/guides/_dirinfo.yaml

@@ -3,8 +3,8 @@ section-title: Guides
 order:
   - /creating-modules
   - /deploy
-  - /verify
   - /visualize
   - /error-handling
   - /modifications
   - /tests
+  - /verify

docs/src/content/ignition/docs/guides/verify.md

@@ -1,14 +1,14 @@
-# Verifying your contracts
+# Verifying your deployment
 
-Once your module has been deployed to a live network, the next step is to verify its source code.
+Once your Ignition module is tested and ready, the next step is to deploy it to a live network and verify the source code of each of its contracts.
 
 Verifying a contract means making its source code public, along with the compiler settings you used, which allows anyone to compile it and compare the generated bytecode with the one that is deployed on-chain. Doing this is extremely important in an open platform like Ethereum.
 
-In this guide we'll explain how to do this with Hardhat Ignition in the [Etherscan](https://etherscan.io/) explorer.
+In this guide we'll explain how to do this with the [Etherscan](https://etherscan.io/) explorer.
 
 ## Getting an API key from Etherscan
 
-The first thing you need is an API key from Etherscan. To get one, go to [their site](https://etherscan.io/login), sign in (or create an account if you don't have one) and open the "API Keys" tab. Then click the "Add" button and give a name (like "Hardhat") to the API key you are creating. After that you'll see the newly created key in the list.
+The first thing you need is an API key from Etherscan. To get one, go to [their site](https://etherscan.io/login), sign in (or create an account if you don't have one) and open the "API Keys" tab. Then click the "Add" button and give a name to the API key you are creating (e.g. "Hardhat"). After that you'll see the newly created key in the list.
 
 Open your Hardhat config and add the API key you just created:
 
@@ -42,28 +42,29 @@ module.exports = {
 
 ::::
 
-## Deploying and verifying a contract in the Sepolia testnet
+## Deploying and verifying on the Sepolia testnet
 
-We are going to use the [Sepolia testnet](https://ethereum.org/en/developers/docs/networks/#sepolia) to deploy and verify our contract, so you need to add this network in your Hardhat config. Here we are using [Alchemy](https://alchemy.com/) to connect to the network, but you can use an alternative JSON-RPC URL like [Infura](https://infura.io/) if you want.
+We are going to use the [Sepolia testnet](https://ethereum.org/en/developers/docs/networks/#sepolia) to deploy and verify our Ignition module, so you need to add this network in your Hardhat config. Here we are using [Alchemy](https://alchemy.com/) to connect to the network.
 
-::::tabsgroup{options=Alchemy,Infura}
+::::tabsgroup{options=TypeScript,JavaScript}
 
-:::tab{value=Alchemy}
+:::tab{value=TypeScript}
 
-```js
+```ts
 // Go to https://alchemy.com, sign up, create a new App in
-// its dashboard, and replace "KEY" with its key
-const ALCHEMY_API_KEY = "KEY";
+// its dashboard, and set the Hardhat configuration variable
+// ALCHEMY_API_KEY to the key
+const ALCHEMY_API_KEY = vars.get("ALCHEMY_API_KEY");
 
-// Replace this private key with your Sepolia account private key
+// Replace this private key with your Sepolia test account private key
 // To export your private key from Coinbase Wallet, go to
 // Settings > Developer Settings > Show private key
 // To export your private key from Metamask, open Metamask and
 // go to Account Details > Export Private Key
 // Beware: NEVER put real Ether into testing accounts
-const SEPOLIA_PRIVATE_KEY = "YOUR SEPOLIA PRIVATE KEY";
+const SEPOLIA_PRIVATE_KEY = vars.get("SEPOLIA_PRIVATE_KEY");
 
-module.exports = {
+export default {
   // ...rest of your config...
   networks: {
     sepolia: {
@@ -76,26 +77,27 @@ module.exports = {
 
 :::
 
-:::tab{value=Infura}
+:::tab{value=JavaScript}
 
 ```js
-// Go to https://infura.io, sign up, create a new API key
-// in its dashboard, and replace "KEY" with it
-const INFURA_API_KEY = "KEY";
+// Go to https://alchemy.com, sign up, create a new App in
+// its dashboard, and set the Hardhat configuration variable
+// ALCHEMY_API_KEY to the key
+const ALCHEMY_API_KEY = vars.get("ALCHEMY_API_KEY");
 
-// Replace this private key with your Sepolia account private key
+// Replace this private key with your Sepolia test account private key
 // To export your private key from Coinbase Wallet, go to
 // Settings > Developer Settings > Show private key
 // To export your private key from Metamask, open Metamask and
 // go to Account Details > Export Private Key
 // Beware: NEVER put real Ether into testing accounts
-const SEPOLIA_PRIVATE_KEY = "YOUR SEPOLIA PRIVATE KEY";
+const SEPOLIA_PRIVATE_KEY = vars.get("SEPOLIA_PRIVATE_KEY");
 
 module.exports = {
   // ...rest of your config...
   networks: {
     sepolia: {
-      url: `https://sepolia.infura.io/v3/${INFURA_API_KEY}`,
+      url: `https://eth-sepolia.g.alchemy.com/v2/${ALCHEMY_API_KEY}`,
       accounts: [SEPOLIA_PRIVATE_KEY],
     },
   },
@@ -112,7 +114,7 @@ To deploy on Sepolia you need to send some Sepolia ether to the address that's g
 
 :::tip
 
-This guide assumes you are using the contracts and deployment module from the [quick start guide](/ignition/docs/getting-started#quick-start), but the steps are the same for any contract.
+This guide assumes you are using the contracts and Ignition module from the [quick start guide](/ignition/docs/getting-started#quick-start), but the steps are the same for any deployment.
 
 :::
 
@@ -147,7 +149,9 @@ npx hardhat ignition deploy ignition/modules/Apollo.js --network sepolia --verif
 
 ::::
 
-The `--verify` flag is optional, but it tells Hardhat Ignition to verify the contracts immediately after finishing the deployment. If you have an existing deployment and want to verify it, you can also run the `verify` task directly using the deployment ID:
+The `--verify` flag is optional, but it tells Hardhat Ignition to verify the contracts after a successful deployment.
+
+If you have an existing deployment and want to verify it, you can also run the `verify` task directly by passing the deployment ID:
 
 ```sh
 npx hardhat ignition verify chain-11155111
@@ -159,6 +163,6 @@ If you get an error saying that the address does not have bytecode, it probably
 
 :::
 
-After the task is successfully executed, you'll see a link to the publicly verified code of your contract.
+After the task has successfully executed, for each deployed contract you'll see a link to its publicly verified code.
 
 To learn more about verifying, read the [hardhat-verify](/hardhat-runner/plugins/nomicfoundation-hardhat-verify) documentation.