fix format

Author: aelmanaa

src/content/quickstarts/automated-portfolio-manager.mdx

@@ -19,16 +19,25 @@ A live demo is available at https://automated-portfolio-manager.vercel.app.
 
 The example contract supports dynamic asset management using tokens that adhere to the ERC20 standard. For this demonstration, Mimic Tokens representing gold (mXAU), Wrapped Bitcoin (mWBTC), and Ethereum (mETH) are used as the underlying assets. These tokens are automatically bought or sold to mirror changes in crypto market sentiment and gold volatility (GVZ) to ensure the portfolio adjusts to evolving market conditions. This functionality demonstrates how blockchain and Chainlink technologies can be used to create a dynamic investment strategy that adapts to global financial movements in real time.
 
-**Note**: In a real-world use case, you can integrate the portfolio rebalancing mechanism with any DeFi protocol, such as a swapping mechanism or investments in ERC-4626 vaults. 
+**Note**: In a real-world use case, you can integrate the portfolio rebalancing mechanism with any DeFi protocol, such as a swapping mechanism or investments in ERC-4626 vaults.
 
 <ClickToZoom src="/images/quickstarts/automated-portfolio-manager/Automated_Portfolio_Manager_Concept.webp" />
 
 <Aside type="caution" title="Disclaimer">
-This tutorial represents an example of using a Chainlink product or service and is provided to help you understand how to interact with Chainlink's systems and services so that you can integrate them into your own. This template is provided "AS IS" and "AS AVAILABLE" without warranties of any kind, has not been audited, and may be missing key checks or error handling to make the usage of the product more clear. Do not use the code in this example in a production environment without completing your own audits and application of best practices. Neither Chainlink Labs, the Chainlink Foundation, nor Chainlink node operators are responsible for unintended outputs that are generated due to errors in code.
+  This tutorial represents an example of using a Chainlink product or service and is provided to help you understand how
+  to interact with Chainlink's systems and services so that you can integrate them into your own. This template is
+  provided "AS IS" and "AS AVAILABLE" without warranties of any kind, has not been audited, and may be missing key
+  checks or error handling to make the usage of the product more clear. Do not use the code in this example in a
+  production environment without completing your own audits and application of best practices. Neither Chainlink Labs,
+  the Chainlink Foundation, nor Chainlink node operators are responsible for unintended outputs that are generated due
+  to errors in code.
 </Aside>
 
 <Aside type="caution" title="Disclaimer">
-The rebalancing strategy and logic outlined in this tutorial are solely for educational purposes and have not been backtested. This content is not meant to be financial advice and should not be interpreted as such. The example is intended to demonstrate the potential of Chainlink products. Users are strongly advised to perform their own due diligence before making any financial decisions.
+  The rebalancing strategy and logic outlined in this tutorial are solely for educational purposes and have not been
+  backtested. This content is not meant to be financial advice and should not be interpreted as such. The example is
+  intended to demonstrate the potential of Chainlink products. Users are strongly advised to perform their own due
+  diligence before making any financial decisions.
 </Aside>
 
 ## Table of Content
@@ -113,6 +122,7 @@ Run the following script to deploy your `OffchainDataFetcher` contract on Ethere
 ```bash
 forge script script/DeployOffChainDataFetcher.s.sol --rpc-url $RPC_URL_SEPOLIA --private-key $PRIVATE_KEY --broadcast --verify -vvvv
 ```
+
 </Accordion>
 
 <Accordion title="Add the contract to your Functions subscription and configure it" number={2}>
@@ -207,9 +217,11 @@ forge script script/DeployAutomatedPortfolioManager.s.sol --rpc-url $RPC_URL_SEP
    cp .env.example .env.local
    ```
 1. Open your `.env.local` file and add your Sepolia RPC URL:
+
    ```
    NEXT_PUBLIC_SEPOLIA_RPC_URL=your_sepolia_rpc_url
    ```
+
    You can use the same RPC URL you used for contract deployment or get one from providers like [Alchemy](https://www.alchemy.com/) or [Infura](https://www.infura.io/).
 
 1. Run the dApp locally:

src/content/quickstarts/automation-station.mdx

@@ -1,7 +1,7 @@
 ---
 title: "Direct Staking Guide for Third-Party Integrators"
 description: "A guide for third-party integrators to integrate with direct staking solutions that allow users to stake L1 assets from L2 networks using Chainlink CCIP."
-excerpt: "Learn how to integrate with direct staking solutions using Chainlink CCIP. This guide covers fast stake and slow stake implementations, fee estimation, allowance management, and cross-chain tracking using the chainlink-csr repository with Lido as an example."
+excerpt: "Learn how to integrate with direct staking solutions using Chainlink CCIP Programmable Token Transfers. This comprehensive integration guide covers fast stake (instant swaps via liquidity pools) and slow stake (cross-chain bridging) implementations, CCIP fee estimation and encoding, ERC-20 token allowance management, cross-chain transaction tracking, and error handling patterns. Includes hands-on tutorial with Lido wstETH staking on Base Mainnet, TypeScript utilities from chainlink-csr repository, and production-ready reference implementations for third-party integrators building offchain components for liquid staking protocols."
 githubSourceCodeUrl: "https://github.com/Aphyla/chainlink-csr"
 image: "QuickStarts-CCIP-Liquid-Staking.webp"
 products: ["ccip"]

src/content/quickstarts/ccip-direct-staking.mdx

@@ -8,7 +8,6 @@ time: "10 minutes"
 requires: "Wallet with gas token & ERC-677 LINK"
 ---
 
-
 import { Aside } from "@components"
 
 ## Overview

src/content/quickstarts/chainlink-hardhat-starter-kit.mdx

@@ -55,7 +55,7 @@ Deploying smart contracts onchain requires a wallet and ETH. The ETH pays for th
 
    ![Screenshot showing the network selection menu in MetaMask. The Sepolia Test Network is selected.](/images/getting-started/selectSepolia.webp)
 
-1. Go to [faucets.chain.link](https://faucets.chain.link/sepolia) and follow the steps to send testnet ETH to your MetaMask wallet address. After the faucet completes the transaction, you should have testnet ETH in your MetaMask wallet on the Sepolia testnet. Optionally, you can get testnet ETH from one of the [alternative faucets](https://faucetlink.to/sepolia). 
+1. Go to [faucets.chain.link](https://faucets.chain.link/sepolia) and follow the steps to send testnet ETH to your MetaMask wallet address. After the faucet completes the transaction, you should have testnet ETH in your MetaMask wallet on the Sepolia testnet. Optionally, you can get testnet ETH from one of the [alternative faucets](https://faucetlink.to/sepolia).
 
 Now that you configured your wallet and funded it with testnet ETH, you can write, compile, and deploy your contract.
 

src/content/quickstarts/deploy-your-first-contract.mdx

@@ -130,22 +130,22 @@ The [`EthBalanceMonitor` contract](https://github.com/smartcontractkit/documenta
 
 Functions with an asterisk (`*`) denote features that only the owner can change. Click on each function to learn more about its parameters and design patterns:
 
-| Function Name                | Description                                                                            |
-| ---------------------------- | -------------------------------------------------------------------------------------- |
-| `setWatchList`\*             | Addresses to watch minimum balance and how much to top it up.                          |
-| `setForwarderAddress`\* | Updates your upkeep's forwarder address, which is available after you create your upkeep.                   |
-| `setMinWaitPeriodSeconds`\*  | Updates the global minimum period between top ups.                                     |
-| `topUp`                      | Used by `performUpkeep`. This function will only trigger top up if conditions are met. |
+| Function Name               | Description                                                                               |
+| --------------------------- | ----------------------------------------------------------------------------------------- |
+| `setWatchList`\*            | Addresses to watch minimum balance and how much to top it up.                             |
+| `setForwarderAddress`\*     | Updates your upkeep's forwarder address, which is available after you create your upkeep. |
+| `setMinWaitPeriodSeconds`\* | Updates the global minimum period between top ups.                                        |
+| `topUp`                     | Used by `performUpkeep`. This function will only trigger top up if conditions are met.    |
 
 Below are the feed functions in `EthBalanceMonitor`:
 
-| Read Function Name         | Description                                                                                                                         |
-| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
-| `getUnderfundedAddresses`  | View function used in `checkUpkeep` to find underfunded balances.                                                                   |
-| `getForwarderAddress` | Views the upkeep's forwarder address.                                                                                                 |
-| `getMinWaitPeriodSeconds`  | Views the global minimum period between top ups.                                                                                    |
-| `getWatchList`             | Views addresses to watch minimum balance and how much to top it up.                                                                 |
-| `getAccountInfo`           | Provides information about the specific target address, including the last time it was topped up. This function is _external only_. |
+| Read Function Name        | Description                                                                                                                         |
+| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
+| `getUnderfundedAddresses` | View function used in `checkUpkeep` to find underfunded balances.                                                                   |
+| `getForwarderAddress`     | Views the upkeep's forwarder address.                                                                                               |
+| `getMinWaitPeriodSeconds` | Views the global minimum period between top ups.                                                                                    |
+| `getWatchList`            | Views addresses to watch minimum balance and how much to top it up.                                                                 |
+| `getAccountInfo`          | Provides information about the specific target address, including the last time it was topped up. This function is _external only_. |
 
 ### `setWatchList` Function
 
@@ -163,9 +163,9 @@ Only the owner can `setWatchList`. Each of the parameters should be set with dis
 
 #### Parameters
 
-| Name                    | Description                                        |
-| ----------------------- | -------------------------------------------------- |
-| `forwarderAddress`      | Unique forwarder address used to secure your upkeep |
+| Name               | Description                                         |
+| ------------------ | --------------------------------------------------- |
+| `forwarderAddress` | Unique forwarder address used to secure your upkeep |
 
 Only the `forwarderAddress` can `performUpkeep`. Your upkeep's forwarder address can be found on the [Chainlink Automation app](https://automation.chain.link/) after you create the upkeep. Only the owner can set a new `forwarderAddress` after deployment.
 

src/content/quickstarts/eth-balance-monitor.mdx

@@ -11,8 +11,8 @@ requires: "Wallet with gas token & ERC-677 LINK"
 import { Aside } from "@components"
 
 <Aside type="caution" title="Polygon testnet change">
-The Mumbai network has stopped producing blocks, so example code will not function on this network. Check again soon
-for updates about future testnet support on Polygon.
+  The Mumbai network has stopped producing blocks, so example code will not function on this network. Check again soon
+  for updates about future testnet support on Polygon.
 </Aside>
 
 ## Overview

src/content/quickstarts/functions-demo-app.mdx

@@ -83,11 +83,11 @@ For demo purposes, use Sepolia for this tutorial. Create a block explorer API ke
    - The private key for your deployer account. If your deployer account is in MetaMask, [export your private key from MetaMask](https://support.metamask.io/hc/en-us/articles/360015289632-How-to-export-an-account-s-private-key).
    - The block explorer API key from Etherscan that you [created earlier](#create-a-block-explorer-api-key).
 
-   | Parameter         | Description                                                                             | Example                                                |
-   | ----------------- | --------------------------------------------------------------------------------------- | ------------------------------------------------------ |
+   | Parameter         | Description                                                                             | Example                                             |
+   | ----------------- | --------------------------------------------------------------------------------------- | --------------------------------------------------- |
    | `NETWORK_RPC_URL` | The RPC URL for the network you want to deploy to.                                      | `https://eth-sepolia.g.alchemy.com/v2/your-api-key` |
-   | `PRIVATE_KEY`     | The private key of the account you want to deploy from. <br/> Add `0x` before your key. | `0xabc123abc123abc123abc123abc123...`                  |
-   | `EXPLORER_KEY`    | The block explorer API key needed for contract verification.                            | `ABC123ABC123ABC123ABC123ABC123ABC1`                   |
+   | `PRIVATE_KEY`     | The private key of the account you want to deploy from. <br/> Add `0x` before your key. | `0xabc123abc123abc123abc123abc123...`               |
+   | `EXPLORER_KEY`    | The block explorer API key needed for contract verification.                            | `ABC123ABC123ABC123ABC123ABC123ABC1`                |
 
 1. In the `contracts` directory, create a `.env` file for your contract environment variables:
 
@@ -148,35 +148,35 @@ Install [GNU make](https://www.gnu.org/software/make/) if you do not already hav
 
 ### macOS
 
-   1. The Xcode command line tools include `make`. If you've previously installed Xcode, skip to step 2 to verify your installation. Otherwise, open a Terminal window and run:
-      ```sh
-      xcode-select --install
-      ```
-      Alternatively, if you prefer to [use Homebrew](https://formulae.brew.sh/formula/make), be aware that GNU `make` is installed as `gmake`.
-   1.  Verify your `make` installation:
-         ```sh
-         make
-         ```
-         If `make` is installed successfully, you will get the following output:
-         ```sh
-         make: *** No targets specified or no makefile found. Stop.
-         ```
+1. The Xcode command line tools include `make`. If you've previously installed Xcode, skip to step 2 to verify your installation. Otherwise, open a Terminal window and run:
+   ```sh
+   xcode-select --install
+   ```
+   Alternatively, if you prefer to [use Homebrew](https://formulae.brew.sh/formula/make), be aware that GNU `make` is installed as `gmake`.
+1. Verify your `make` installation:
+   ```sh
+   make
+   ```
+   If `make` is installed successfully, you will get the following output:
+   ```sh
+   make: *** No targets specified or no makefile found. Stop.
+   ```
 
 ### Windows
 
-   1. If you're using WSL, open an Ubuntu terminal and run:
-      ```sh
-      sudo apt install make
-      ```
-   1. [Edit your path variable to include `make`](https://help.ubuntu.com/community/EnvironmentVariables#Persistent_environment_variables).
-   1. Verify your `make` installation:
-      ```sh
-      make
-      ```
-      If `make` is installed successfully, you will get the following output:
-      ```sh
-      make: *** No targets specified or no makefile found. Stop.
-      ```
+1.  If you're using WSL, open an Ubuntu terminal and run:
+    ```sh
+    sudo apt install make
+    ```
+1.  [Edit your path variable to include `make`](https://help.ubuntu.com/community/EnvironmentVariables#Persistent_environment_variables).
+1.  Verify your `make` installation:
+    ```sh
+    make
+    ```
+    If `make` is installed successfully, you will get the following output:
+    ```sh
+    make: *** No targets specified or no makefile found. Stop.
+    ```
 
 Install contract dependencies if changes have been made to contracts:
 
@@ -232,10 +232,10 @@ Set environment variables to run the UI and then view it locally.
 
 1. Prepare your UI environment variables. These are needed for each time you want to run the UI:
 
-   | Item                                   | Value                                                                                                                                                                                                                                 |
-   | -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-   | `UI_GIVEAWAY_MANAGER_CONTRACT_ADDRESS` | The address of the Giveaway Contract Manager contract that you [deployed earlier](#deploy-contract)                                                                                                                                   |
-   | `UI_LINK_TOKEN_CONTRACT_ADDRESS`       | For Ethereum Sepolia: <CopyText text="0x779877A7B0D9E8603169DdbD7836e478b4624789" code/> <br/> See all [LINK token contract addresses](/resources/link-token-contracts)                                                                 |
+   | Item                                   | Value                                                                                                                                                                                                                                           |
+   | -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+   | `UI_GIVEAWAY_MANAGER_CONTRACT_ADDRESS` | The address of the Giveaway Contract Manager contract that you [deployed earlier](#deploy-contract)                                                                                                                                             |
+   | `UI_LINK_TOKEN_CONTRACT_ADDRESS`       | For Ethereum Sepolia: <CopyText text="0x779877A7B0D9E8603169DdbD7836e478b4624789" code/> <br/> See all [LINK token contract addresses](/resources/link-token-contracts)                                                                         |
    | `UI_KEEPER_REGISTRY_CONTRACT_ADDRESS`  | For Ethereum Sepolia: <CopyText text="0xE16Df59B887e3Caa439E0b29B42bA2e7976FD8b2" code/> <br/> This app currently supports Automation v1.2. See all [Automation registry contract addresses](/chainlink-automation/overview/supported-networks) |
 
 1. Navigate to the `/client/packages/ui` directory, and run these commands to set up your UI environment variables. Do not use quotes to assign values:

src/content/quickstarts/giveaway.mdx

@@ -122,7 +122,7 @@ Instead, you can call the methods by passing its name as a parameter for the rel
 If the subtask and/or args are not passed directly, they will be interactively inquired during the CLI command execution.
 
 <Aside type="note">
-<p>Arguments for methods called with CLI should be provided as a valid JSON string.</p>
+  <p>Arguments for methods called with CLI should be provided as a valid JSON string.</p>
 </Aside>
 
 To get a list of all available methods (subtasks) and their arguments for a specific service, you can use: