Update migration page and small fixes

src/content/chainlink-automation/guides/migrate-to-v2.mdx

@@ -23,8 +23,6 @@ If your upkeep is restricted to a single address calling it, you must give permi
 
 The Chainlink Automation App offers a streamlined migration process for upkeeps using registry versions 1.2 and later. To migrate upkeeps with older versions, follow the [manual migration process](#migrating-older-upkeeps-manually) instead.
 
-You can use the Chainlink Automation App to migrate one upkeep at a time, or [migrate multiple upkeeps using the block scanner](#migrating-upkeeps-using-block-scanner).
-
 1. Navigate to the Chainlink Automation App, select the supported blockchain you're using, and connect your wallet.
 
    <div class="remix-callout">
@@ -47,14 +45,33 @@ Upkeeps that are successfully migrated will show the following [transaction logs
 
 <ClickToZoom src="/images/automation/v2-migration/migration-txn.png" />
 
+### Migrating multiple upkeeps
+
+If you have multiple upkeeps to migrate, you can do so in the Chainlink Automation App.
+
+1. Click the link displays on your upkeeps dashboard. This link only displays if you have one or more upkeeps to migrate:
+
+   <ClickToZoom src="/images/automation/v2-migration/1-bulk-migration-ui.png" />
+
+1. Follow the prompts to approve and confirm the transactions to migrate your upkeep(s).
+
+   <ClickToZoom src="/images/automation/v2-migration/approve-migration.png" />
+
+### Updating permissions
+
+Your new upkeep has a new [unique forwarder](#unique-forwarder) to increase security for your upkeep. This address will be the unique `msg.sender` for your upkeep. If your upkeep is restricted to a single address calling it, you must give permission to the forwarder address. Otherwise, Automation will no longer be able to execute your function.
+
+1. The forwarder address becomes available after migrating your upkeep. You can find this in the Chainlink Automation App, within the upkeep's **Details** section:
+
+   <ClickToZoom src="/images/automation/v2-migration/forwarder-address.png" />
+
+1. Update your contract to use the forwarder address by following the instructions in the [Forwarder](/chainlink-automation/guides/forwarder) page.
+
 When the migration is complete:
 
 - Your balance is transferred to the new registry automatically.
-- The new upkeep details page shows the updated registry address and a forwarder address. The forwarder address is a new [unique forwarder](#unique-forwarder) to increase security for your upkeep. This address will be the unique `msg.sender` for your upkeep. If your upkeep is restricted to a single address calling it, you must give permission to the forwarder address. Otherwise, Automation will no longer be able to execute your function.
 - Read the [migration checklist](#migration-checklist) to understand further updates you may need to make in your contracts.
 
-<ClickToZoom src="/images/automation/v2-migration/details-with-forwarder.png" />
-
 ## Migrating upkeeps using block scanner
 
 To migrate one or more upkeeps using the scanner:
@@ -69,6 +86,13 @@ To migrate one or more upkeeps using the scanner:
 
 1. Execute the `migrateUpkeeps` function and confirm the transaction. When this transaction is confirmed, your upkeeps will be migrated to the latest registry, and each upkeep will have a [unique forwarder](#unique-forwarder) address.
 
+1. Update your contract to use the forwarder address by following the instructions in the [Forwarder](/chainlink-automation/guides/forwarder) page.
+
+When the migration is complete:
+
+- Your balance is transferred to the new registry automatically.
+- Read the [migration checklist](#migration-checklist) to understand further updates you may need to make in your contracts.
+
 ## Migrating older upkeeps manually
 
 For upkeeps on registry versions 1.0 and 1.1, you must migrate upkeeps manually:

src/content/chainlink-automation/overview/getting-started.mdx

@@ -65,7 +65,7 @@ Click the tabs below to use Chainlink Automation with each type of trigger:
 
       1. Navigate to the [Chainlink Automation app](https://automation.chain.link/) and connect to **Arbitrum Sepolia** in the top dropdown menu.
 
-      1. Connect your cryptocurrency wallet to the app if you haven't done so already. You may also need to fetch Arbitrum Sepolia testnet LINK [here](https://automation.chain.link/arbitrum-sepolia).
+      1. Connect your cryptocurrency wallet to the app if you haven't done so already. You may also need to fetch Arbitrum Sepolia testnet LINK [here](https://faucets.chain.link/arbitrum-sepolia).
 
       1. Click **Register new Upkeep** and select **Custom logic** trigger.
 
@@ -92,9 +92,9 @@ Click the tabs below to use Chainlink Automation with each type of trigger:
 
       1. Navigate to the [Chainlink Automation app](https://automation.chain.link/) and connect to **Arbitrum Sepolia** in the top dropdown menu.
 
-      1. Connect your cryptocurrency wallet to the app if you haven't done so already. You may also need to fetch Arbitrum Sepolia testnet LINK [here](https://automation.chain.link/arbitrum-sepolia).
+      1. Connect your cryptocurrency wallet to the app if you haven't done so already. You may also need to fetch Arbitrum Sepolia testnet LINK [here](https://faucets.chain.link/arbitrum-sepolia).
 
-      1. Click **Register new Upkeep** and select **log trigger**.
+      1. Click **Register new Upkeep** and select **Log trigger**.
 
       1. Under _Contract to automate_, enter <Address contractUrl="https://sepolia.arbiscan.io/address/0xe817e4A71C69C72C01B31906F9F8591FbaB6b448" />. This is a simple `iLogAutomation`-compatible example contract that increments a counter when a log is detected. View the source code [here](https://sepolia.arbiscan.io/address/0xe817e4A71C69C72C01B31906F9F8591FbaB6b448#code). Click **Next**.