Acquire tokens renaming and "'"unicode symbol (#6)

* refactor: rename move-funds to acquire testnet tokens

* fix: unicode ' in protocol page

docs/move-funds.md → docs/acquire-testnet-tokens.md

@@ -1,11 +1,11 @@
 ---
-title: Move Funds to UniFi
-slug: /move-funds
+title: Acquire Testnet Tokens
+slug: /acquire-testnet-tokens
 ---
 
-# Moving Funds to UniFi
+# Acquire Testnet Tokens
 
-This guide will help you move your funds from the L1 Testnet to UniFi Rollup. Follow the steps below to get started.
+This guide will help you acquire UniFi Testnet tokens. Follow the steps below to get started.
 
 ## 1. Install a Compatible Wallet
 
@@ -17,7 +17,7 @@ To interact with UniFi Rollup, you need an Ethereum wallet like MetaMask or any
 
 ## 2. Add the L2 Testnet to MetaMask
 
-To connect to the UniFi Helder Testnet, follow these steps:
+To connect to the UniFi Testnet, follow these steps:
 
 1. Open MetaMask and click on the network dropdown.
 2. Select **Add network** → **Add a network manually**.

docs/developers/rollup/smart-contracts/deploy-foundry.md

@@ -7,7 +7,7 @@ slug: /developers/rollup/smart-contracts/foundry
 
 Before you begin, ensure you've:
 
-1. [Set up your wallet and have bridged UniFi tokens successfully](../../../move-funds.md).
+1. [Set up your wallet and have acquired Testnet tokens](../../../acquire-testnet-tokens.md).
 2. Downloaded and installed Foundry:
 
    ```bash

docs/developers/rollup/smart-contracts/deploy-hardhat.md

@@ -7,7 +7,7 @@ slug: /developers/rollup/smart-contracts/hardhat
 
 Before you begin, ensure you:
 
-1. [Set up your wallet and have bridged UniFi tokens successfully](../../../move-funds.md).
+1. [Set up your wallet and acquired Tesntet tokens](../../../acquire-testnet-tokens.md).
 2. [Set up your Hardhat environment](https://hardhat.org/tutorial/setting-up-the-environment#2.-setting-up-the-environment).
 
 ## Create a Hardhat project

docs/intro.md

@@ -30,6 +30,6 @@ making it an ideal solution for those seeking scalability without sacrificing de
 
 ### Get Started with UniFi Rollup
 
-To begin using UniFi, start by moving your testnet tokens using the [Move Funds to UniFi guide](/move-funds).
+To begin using UniFi, start by [acquiring Testnet tokens](/acquire-testnet-tokens).
 
 By leveraging UniFi's Ethereum-based rollup, users can enjoy an efficient, decentralized, and unified experience while contributing to the long-term health of the Ethereum ecosystem.

docs/protocol/overview.md

@@ -16,7 +16,7 @@ The flow begins with users submitting **rollup transactions** to **UniFi Sequenc
 **Preconfirmations** are essentially "soft promises" from the sequencers that the transactions will be included in the next L1 block. These preconfirmations come with economic guarantees backed by penalties (slashing conditions) to ensure sequencer reliability. If a sequencer fails to include a transaction it has preconfirmed, it risks being slashed.
 
 ### 2️⃣ Block Proposal
-Once the sequencer has aggregated enough transactions, it bundles them into a **block**. This block is then **proposed** to UniFi’s **Rollup Contract** on the Ethereum L1. At this stage, no execution is performed. Ethereum validators simply record the block’s ordered transactions on the L1, and only transaction validation is performed on a contract level. It’s important to note that Ethereum validators are responsible for the order of inclusion of these **proposed block** transactions in the L1 chain, which is where the "based"-ness of UniFi comes into play.
+Once the sequencer has aggregated enough transactions, it bundles them into a **block**. This block is then **proposed** to UniFi's **Rollup Contract** on the Ethereum L1. At this stage, no execution is performed. Ethereum validators simply record the block's ordered transactions on the L1, and only transaction validation is performed on a contract level. It's important to note that Ethereum validators are responsible for the order of inclusion of these **proposed block** transactions in the L1 chain, which is where the "based"-ness of UniFi comes into play.
 
 ### 3️⃣ Block Insertion
 When a proposed block is successfully included in the Ethereum L1 chain, the **UniFi Client** listens for this event. The client:
@@ -31,8 +31,8 @@ The last step is to prove to the L1 that the block has been executed correctly o
 
 To generate a proof, provers create a **Proof of Block (PoB)** statement themselves, which they send over to an **Intel TDX TEE** for attestation. The TEE acts as a trusted computation enclave that uses the PoB to securely re-execute the block's transactions and verify the state transitions. Once the re-execution completes:
 
-- The TEE generates an **attestation** that ensures the L2 block’s integrity.
-- The attestation and cryptographic proof are submitted to UniFi’s L1 contract on Ethereum.
+- The TEE generates an **attestation** that ensures the L2 block's integrity.
+- The attestation and cryptographic proof are submitted to UniFi's L1 contract on Ethereum.
 - The L1 contract verifies the proof, ensuring that the state transitions are valid and match the ordered transactions.
 - Once verified, the block is considered **proven**, and the L1 state is updated to reflect this.
 

sidebars.js

@@ -36,7 +36,7 @@ const sidebars = {
       ]
     },
 
-    "move-funds",
+    "acquire-testnet-tokens",
     "bridge-ui",
   ],
   developersSidebar: [