fix format

aimen-djari · aimen-djari · commit 0f0ab4b37987 · 2025-08-12T23:55:48.000+01:00
diff --git a/src/use-iapp/getting-started.md b/src/use-iapp/getting-started.md
@@ -6,14 +6,17 @@ description:
 
 # 🚀 Getting Started with iApps
 
-Welcome to the world of secure, privacy-preserving computation! This guide gives you a high-level overview of how to use iApps on the iExec network.
+Welcome to the world of secure, privacy-preserving computation! This guide gives
+you a high-level overview of how to use iApps on the iExec network.
 
 ## Prerequisites
 
 Before you begin, make sure you have:
 
 - A Web3 wallet (MetaMask, WalletConnect, etc.)
-- Some RLC tokens for paying computation fees (or access to free vouchers through learning programs) - [Learn about RLC tokens](/overview/rlc) and [how to bridge them](/overview/tooling-and-explorers/bridge)
+- Some RLC tokens for paying computation fees (or access to free vouchers
+  through learning programs) - [Learn about RLC tokens](/overview/rlc) and
+  [how to bridge them](/overview/tooling-and-explorers/bridge)
   - **Note**: On Arbitrum, you'll need AETH (Arbitrum ETH) instead of RLC
 - Basic understanding of blockchain transactions
 - iExec SDK installed
@@ -44,33 +47,49 @@ Ready to dive in? Let's get started with finding and executing your first iApp!
 
 Using iApps involves these main steps:
 
-1. **Find iApps** - Browse available applications in the [iExec Explorer](/overview/tooling-and-explorers/iexec-explorer)
+1. **Find iApps** - Browse available applications in the
+   [iExec Explorer](/overview/tooling-and-explorers/iexec-explorer)
 2. **Prepare Data** - Set up any required protected data or inputs
 3. **Execute** - Run the iApp
 4. **Get Results** - Retrieve your computation results
 
 ### Understanding Orders
 
-iApps are executed through a marketplace system where different actors publish orders:
+iApps are executed through a marketplace system where different actors publish
+orders:
+
 - **App orders** - Published by developers with pricing and availability
-- **Workerpool orders** - Published by computation providers with capacity and pricing  
-- **Dataset orders** - Published by data owners with access conditions and pricing
+- **Workerpool orders** - Published by computation providers with capacity and
+  pricing
+- **Dataset orders** - Published by data owners with access conditions and
+  pricing
 
-When you execute an iApp, the system matches your request with available orders from all three categories. For a deeper understanding of how orders work and how to manage them, see the [Manage Orders guide](/build-iapp/guides/manage-access#manage-orders) in the Build iApp section.
+When you execute an iApp, the system matches your request with available orders
+from all three categories. For a deeper understanding of how orders work and how
+to manage them, see the
+[Manage Orders guide](/build-iapp/guides/manage-access#manage-orders) in the
+Build iApp section.
 
 ## Detailed Guides
 
 For step-by-step instructions, check out these guides:
 
-- **[Find iApps](./guides/find-iapps.md)** - How to discover and evaluate available applications
-- **[Different Ways to Execute](./guides/different-ways-to-execute.md)** - iExec cli, lib, and other execution methods
-- **[Use iApps with Protected Data](./guides/use-iapp-with-protected-data.md)** - Working with sensitive data securely
-- **[Add Inputs to Execution](./guides/add-inputs-to-execution.md)** - How to provide data and parameters to iApps
-- **[How to Pay for Executions](./guides/how-to-pay-executions.md)** - Understanding costs and payment options
+- **[Find iApps](./guides/find-iapps.md)** - How to discover and evaluate
+  available applications
+- **[Different Ways to Execute](./guides/different-ways-to-execute.md)** - iExec
+  cli, lib, and other execution methods
+- **[Use iApps with Protected Data](./guides/use-iapp-with-protected-data.md)** -
+  Working with sensitive data securely
+- **[Add Inputs to Execution](./guides/add-inputs-to-execution.md)** - How to
+  provide data and parameters to iApps
+- **[How to Pay for Executions](./guides/how-to-pay-executions.md)** -
+  Understanding costs and payment options
 
 ## Quick Start
 
-Ready to jump in? Start with our [Find iApps guide](./guides/find-iapps.md) to discover what's available, then follow the execution guides for detailed instructions.
+Ready to jump in? Start with our [Find iApps guide](./guides/find-iapps.md) to
+discover what's available, then follow the execution guides for detailed
+instructions.
 
 <script setup>
 import ImageViewer from '../components/ImageViewer.vue';
diff --git a/src/use-iapp/guides/add-inputs-to-execution.md b/src/use-iapp/guides/add-inputs-to-execution.md
@@ -11,16 +11,18 @@ iApps can accept various types of inputs to customize their behavior and provide
 necessary data for processing. This guide covers all the different ways to add
 inputs to your iApp executions using various iExec tools and SDKs.
 
-::: tip ENS Addresses 
+<!-- prettier-ignore-start -->
+::: tip ENS Addresses
 **ENS (Ethereum Name Service)** is a naming system for
 Ethereum addresses that allows you to use human-readable names instead of long
 hexadecimal addresses. For example, instead of using `0x1234567890abcdef...`,
 you can use `debug-v8-learn.main.pools.iexec.eth`.
 
 In the examples below, we use `debug-v8-learn.main.pools.iexec.eth` which is
 iExec's official debug workerpool ENS address. This workerpool is specifically
-designed for testing and development purposes on the Bellecour testnet. 
+designed for testing and development purposes on the Bellecour testnet.
 :::
+<!-- prettier-ignore-end -->
 
 ## Types of Inputs
 
@@ -230,21 +232,18 @@ const datasetOrders = await orderbookModule.fetchDatasetOrderbook({
   dataset: '0x123abc...', // Filter by specific dataset
 });
 ```
+
 const workerpoolOrders = await orderbookModule.fetchWorkerpoolOrderbook({
-  workerpool: 'debug-v8-learn.main.pools.iexec.eth', // Filter by specific workerpool ENS
-});
+workerpool: 'debug-v8-learn.main.pools.iexec.eth', // Filter by specific
+workerpool ENS });
 
-const taskId = await orderModule.matchOrders({
-  requestorder: requestOrder,
-  apporder: appOrders[0],
-  datasetorder: datasetOrders[0],
-  workerpoolorder: workerpoolOrders[0],
-  inputFiles: [
-    'https://raw.githubusercontent.com/user/repo/main/config.json',
-    'https://example.com/public-data.csv',
-  ],
-});
-```
+const taskId = await orderModule.matchOrders({ requestorder: requestOrder,
+apporder: appOrders[0], datasetorder: datasetOrders[0], workerpoolorder:
+workerpoolOrders[0], inputFiles: [
+'https://raw.githubusercontent.com/user/repo/main/config.json',
+'https://example.com/public-data.csv', ], });
+
+````
 
 ### Using SDK CLI
 
@@ -257,7 +256,7 @@ iexec app run 0x456def... --protectedData 0x123abc... --inputFiles "https://exam
 
 # Multiple input files (space-separated)
 iexec app run 0x456def... --protectedData 0x123abc... --inputFiles "https://example.com/config.json" --inputFiles "https://example.com/template.html"
-```
+````
 
 ### Using DataProtector
 
diff --git a/src/use-iapp/guides/different-ways-to-execute.md b/src/use-iapp/guides/different-ways-to-execute.md
@@ -10,16 +10,18 @@ There are multiple ways to execute iApps on the iExec network. This guide covers
 the basic execution methods. For advanced features like protected data,
 arguments, and input files, see the dedicated guides.
 
-::: tip ENS Addresses 
+<!-- prettier-ignore-start -->
+::: tip ENS Addresses
 **ENS (Ethereum Name Service)** is a naming system for
 Ethereum addresses that allows you to use human-readable names instead of long
 hexadecimal addresses. For example, instead of using `0x1234567890abcdef...`,
 you can use `debug-v8-learn.main.pools.iexec.eth`.
 
 In the examples below, we use `debug-v8-learn.main.pools.iexec.eth` which is
 iExec's official debug workerpool ENS address. This workerpool is specifically
-designed for testing and development purposes on the Bellecour testnet. 
+designed for testing and development purposes on the Bellecour testnet.
 :::
+<!-- prettier-ignore-end -->
 
 ## Method 1: Using the iExec SDK Library
 
@@ -77,7 +79,8 @@ iexec app run 0x456def...
 The iApp Generator CLI provides a streamlined way to execute iApps, especially
 for developers who have built their own iApps.
 
-> **Note**: For installation instructions, see the [iApp Generator Getting Started guide](/build-iapp/iapp-generator/getting-started).
+> **Note**: For installation instructions, see the
+> [iApp Generator Getting Started guide](/build-iapp/iapp-generator/getting-started).
 
 ### Basic Execution
 
diff --git a/src/use-iapp/guides/find-iapps.md b/src/use-iapp/guides/find-iapps.md
@@ -11,8 +11,10 @@ available iApps on the iExec network.
 
 ## Using the iExec Explorer
 
-The [iExec Explorer](/overview/tooling-and-explorers/iexec-explorer) is the primary tool for
-discovering iApps. For detailed instructions on how to browse and filter iApps, see the [📱 iApps Listing section](/overview/tooling-and-explorers/iexec-explorer#📱-iapps-listing).
+The [iExec Explorer](/overview/tooling-and-explorers/iexec-explorer) is the
+primary tool for discovering iApps. For detailed instructions on how to browse
+and filter iApps, see the
+[📱 iApps Listing section](/overview/tooling-and-explorers/iexec-explorer#📱-iapps-listing).
 
 ### What to Look For
 
@@ -23,7 +25,9 @@ When evaluating an iApp, check these key details:
 - **Usage Statistics**: How often is it used?
 - **Orders Availability**: Are there active orders available for execution?
 
-> **Note**: Detailed descriptions and specific requirements are not available in the iExec explorer. You may need to check the developer's documentation, community forums, or contact the developer directly for this information.
+> **Note**: Detailed descriptions and specific requirements are not available in
+> the iExec explorer. You may need to check the developer's documentation,
+> community forums, or contact the developer directly for this information.
 
 ## Using the iExec CLI
 
diff --git a/src/use-iapp/introduction.md b/src/use-iapp/introduction.md
@@ -7,39 +7,52 @@ description:
 
 # 📝 Introduction to Using iApps
 
-In the iExec network, multiple actors work together in a coordinated process to ensure secure, decentralized computation. Here's how the ecosystem operates:
+In the iExec network, multiple actors work together in a coordinated process to
+ensure secure, decentralized computation. Here's how the ecosystem operates:
 
 ### Key Actors in the Network
 
 - **👤 Requesters**: Users who need computation performed on protected data
-- **🏭 Workerpool Managers**: Operators who manage groups of workers and coordinate task execution
+- **🏭 Workerpool Managers**: Operators who manage groups of workers and
+  coordinate task execution
 - **⚙️ Workers**: Individual machines that execute the actual computations
-- **👨‍💻 iApp Developers**: Developers who create and deploy applications to the iExec marketplace
+- **👨‍💻 iApp Developers**: Developers who create and deploy applications to the
+  iExec marketplace
 - **🔐 Data Providers**: Users who own and protect the data being processed
 
 ### Network Assets
 
 - **📱 iApps**: Applications that process the data securely
 - **💾 Data**: Protected information that needs to be processed
 - **⚡ Computational Power**: Processing resources provided by workers
-- **💰 PoCo**: Proof of Contribution system that matches all actors through marketplace
+- **💰 PoCo**: Proof of Contribution system that matches all actors through
+  marketplace
 
 ### Network Coordination
 
-The iExec network coordinates all actors through the PoCo (Proof of Contribution) system, which automatically matches requesters with the appropriate applications, data, and computational resources based on availability, requirements, and pricing.
+The iExec network coordinates all actors through the PoCo (Proof of
+Contribution) system, which automatically matches requesters with the
+appropriate applications, data, and computational resources based on
+availability, requirements, and pricing.
 
 ### Deal Execution Flow
 
 When a deal is triggered, the following sequence occurs:
 
 1. **Request Creation**: Requester submits a computation request with parameters
-2. **Resource Matching**: PoCo system matches the request with available applications, data, and computational resources
-3. **Deal Creation**: When compatible resources are found, a deal is created containing multiple tasks
-4. **Task Distribution**: Selected workerpool manager distributes tasks to their workers
-5. **Secure Execution**: Workers download the iApp and execute it in TEE environments
-6. **Data Processing**: iApp processes protected data without accessing raw content
+2. **Resource Matching**: PoCo system matches the request with available
+   applications, data, and computational resources
+3. **Deal Creation**: When compatible resources are found, a deal is created
+   containing multiple tasks
+4. **Task Distribution**: Selected workerpool manager distributes tasks to their
+   workers
+5. **Secure Execution**: Workers download the iApp and execute it in TEE
+   environments
+6. **Data Processing**: iApp processes protected data without accessing raw
+   content
 7. **Result Generation**: Computation results are generated
-8. **Result Delivery**: Results are returned to the requester through the network
+8. **Result Delivery**: Results are returned to the requester through the
+   network
 9. **Payment Settlement**: RLC tokens are distributed to all participants
 
 ### Network Architecture Diagram
@@ -48,15 +61,21 @@ When a deal is triggered, the following sequence occurs:
 
 ### Detailed Interaction Flow
 
-1. **Request Submission**: Requester creates a request specifying the iApp, Protected Data, etc.
+1. **Request Submission**: Requester creates a request specifying the iApp,
+   Protected Data, etc.
 2. **PoCo Processing**: PoCo system validates the request and matches resources
 3. **Deal Creation**: When resources are matched, PoCo creates a deal
-4. **Secure Environment Setup**: Workers initialize TEE environments and download the iApp
-5. **Data Access**: iApp requests access to protected data through secure channels
+4. **Secure Environment Setup**: Workers initialize TEE environments and
+   download the iApp
+5. **Data Access**: iApp requests access to protected data through secure
+   channels
 6. **Computation**: iApp processes data within the TEE, maintaining privacy
-7. **Payment Distribution**: RLC tokens are distributed to all participants based on completed tasks
+7. **Payment Distribution**: RLC tokens are distributed to all participants
+   based on completed tasks
 
-This decentralized architecture ensures that no single entity has control over the entire process, while the use of TEEs guarantees that sensitive data remains protected throughout the computation.
+This decentralized architecture ensures that no single entity has control over
+the entire process, while the use of TEEs guarantees that sensitive data remains
+protected throughout the computation.
 
 ## Getting Started
 
