fix: improve formatting and clarity in README for better readability

Author: ErwanDecoster

README.md

@@ -9,9 +9,12 @@
 
 ### Environment Variables (Optional)
 
-Some features of the application require environment variables. This configuration is optional and only needed if you plan to work with Hello World pages. 
+Some features of the application require environment variables. This
+configuration is optional and only needed if you plan to work with Hello World
+pages.
 
-Create a `.env` file at the root of the project using the provided `.env.example` as a template:
+Create a `.env` file at the root of the project using the provided
+`.env.example` as a template:
 
 ```bash
 cp .env.example .env
@@ -34,7 +37,8 @@ To obtain your `VITE_REOWN_PROJECT_ID`, follow these steps:
    - Project name
    - Description (optional)
    - Website URL (optional)
-5. Once the project is created, copy the "Project ID" displayed in the project details
+5. Once the project is created, copy the "Project ID" displayed in the project
+   details
 6. Paste this ID in your `.env` file as the value for `VITE_REOWN_PROJECT_ID`
 
 ## 🚀 Getting Started
@@ -55,7 +59,8 @@ Start the development server:
 npm run dev
 ```
 
-The documentation site will be available at `http://localhost:3000` (or the port shown in your terminal).
+The documentation site will be available at `http://localhost:3000` (or the port
+shown in your terminal).
 
 ### Building for Production
 
@@ -67,7 +72,8 @@ npm run build
 
 ## 🤝 Contributing
 
-We welcome contributions to improve the iExec documentation! Please follow these steps to contribute:
+We welcome contributions to improve the iExec documentation! Please follow these
+steps to contribute:
 
 ### 1. Fork the Repository
 
@@ -78,12 +84,14 @@ Fork this repository and ensure you're working on the `main` branch:
 ### 2. Set Up Your Development Environment
 
 1. Clone your forked repository:
+
    ```bash
    git clone https://github.com/YOUR_USERNAME/documentation.git
    cd documentation
    ```
 
 2. Install dependencies:
+
    ```bash
    npm install
    ```
@@ -96,6 +104,7 @@ Fork this repository and ensure you're working on the `main` branch:
 ### 3. Make Your Changes
 
 1. Create a new branch for your feature/fix:
+
    ```bash
    git checkout -b feature/your-feature-name
    ```
@@ -106,12 +115,14 @@ Fork this repository and ensure you're working on the `main` branch:
 ### 4. Submit Your Changes
 
 1. Stage and commit your changes with a descriptive message:
+
    ```bash
    git add .
    git commit -m "Add: descriptive commit message"
    ```
 
 2. Push your changes to your forked repository:
+
    ```bash
    git push origin feature/your-feature-name
    ```
@@ -120,17 +131,21 @@ Fork this repository and ensure you're working on the `main` branch:
 
 ### 5. Review Process
 
-> **💡 Tips:**  
-> - You can open a draft pull request and mark it as "Ready for review" once you're satisfied with the preview
+> **💡 Tips:**
+>
+> - You can open a draft pull request and mark it as "Ready for review" once
+>   you're satisfied with the preview
 > - All pull requests are reviewed by our team before being merged
 > - Feel free to ask questions in the pull request if you need clarification
 
 ## 📄 License
 
-This project is part of the iExec ecosystem. Please refer to the main iExec repositories for licensing information.
+This project is part of the iExec ecosystem. Please refer to the main iExec
+repositories for licensing information.
 
 ## 🆘 Support
 
 - 📖 [Documentation](https://docs.iex.ec)
 - 💬 [Discord Community](https://discord.com/invite/pbt9m98wnU)
-- 🐛 [Issue Tracker](https://github.com/iExecBlockchainComputing/documentation/issues)
+- 🐛
+  [Issue Tracker](https://github.com/iExecBlockchainComputing/documentation/issues)