refactor: clean up whitespace and improve documentation clarity

Author: Le-Caignec

src/components/TokenSymbol.vue

@@ -11,14 +11,14 @@ const userStore = useUserStore();
 // Computed property to get the correct token symbol based on selected chain
 const tokenSymbol = computed(() => {
   const currentChainId = userStore.getCurrentChainId();
-  
+
   // Bellecour (0x86) uses xRLC, Arbitrum (42161) uses RLC
   if (currentChainId === 0x86) {
     return 'xRLC';
   } else if (currentChainId === 42161) {
     return 'RLC';
   }
-  
+
   // Default fallback
   return 'RLC';
 });

src/get-started/protocol/worker/manage-access.md

@@ -41,17 +41,17 @@ iexec order init --workerpool
 Edit the `workerpoolorder` part in `iexec.json` to set the conditions to use
 your workerpool:
 
-| key                 | description                                                                          |
-| ------------------- | ------------------------------------------------------------------------------------ |
-| `workerpool`        | workerpool address                                                                   |
-| `workerpoolprice`   | price to charge the requester for each execution of the app (in nano <TokenSymbol />)                |
-| `volume`            | number of authorized uses, each use decreases this number                            |
-| `tag`               | restrict usage to a specific runtime such as **Scone** or **Gramine** TEE frameworks |
-| `category`          | Order category, will define the deal `workClockTimeRef` and its deadlines            |
-| `trust`             | Trust level of the execution, impacts the number of replicates                       |
-| `apprestrict`       | restrict the workerpool usage to a specifig app (1)                                  |
-| `datasetrestrict`   | restrict the workerpool usage to a specific dataset (1)                              |
-| `requesterrestrict` | restrict the workerpool usage to a specific requester (1)                            |
+| key                 | description                                                                           |
+| ------------------- | ------------------------------------------------------------------------------------- |
+| `workerpool`        | workerpool address                                                                    |
+| `workerpoolprice`   | price to charge the requester for each execution of the app (in nano <TokenSymbol />) |
+| `volume`            | number of authorized uses, each use decreases this number                             |
+| `tag`               | restrict usage to a specific runtime such as **Scone** or **Gramine** TEE frameworks  |
+| `category`          | Order category, will define the deal `workClockTimeRef` and its deadlines             |
+| `trust`             | Trust level of the execution, impacts the number of replicates                        |
+| `apprestrict`       | restrict the workerpool usage to a specifig app (1)                                   |
+| `datasetrestrict`   | restrict the workerpool usage to a specific dataset (1)                               |
+| `requesterrestrict` | restrict the workerpool usage to a specific requester (1)                             |
 
 1. the restriction is disabled by default with
    0x0000000000000000000000000000000000000000.

src/get-started/protocol/worker/quick-start.md

@@ -14,12 +14,13 @@ The iExec Worker participates in a workerpool by computing tasks purchased by
 requesters on the iExec marketplace. The iExec Worker must connect to the iExec
 Core Scheduler of the workerpool to actively participate in the computation.
 
-A worker will be rewarded with <TokenSymbol /> for every properly computed tasks.
+A worker will be rewarded with <TokenSymbol /> for every properly computed
+tasks.
 
 Please note that:
 
-- your wallet must be loaded with <TokenSymbol />. Some <TokenSymbol /> must be deposited to your iExec
-  account in order to stake for incoming tasks.
+- your wallet must be loaded with <TokenSymbol />. Some <TokenSymbol /> must be
+  deposited to your iExec account in order to stake for incoming tasks.
 - your computer needs at least 2 CPUs.
 
 ## Start a worker
@@ -33,12 +34,13 @@ configuration documentation of the
 For security reason, it is **highly recommended** to launch your worker in a
 virtual machine.
 
-After having loaded some <TokenSymbol /> and deposited them to your iExec account, you can
-start your worker.
+After having loaded some <TokenSymbol /> and deposited them to your iExec
+account, you can start your worker.
 
 When the worker initialization process is complete, the worker will be started
 and you will get something like: **You worker is all set**. Your worker will now
-be able to compute some tasks coming from the iExec network to earn some <TokenSymbol />s.
+be able to compute some tasks coming from the iExec network to earn some
+<TokenSymbol />s.
 
 ## Wallet restriction
 

src/guides/use-iapp/getting-started.md

@@ -66,7 +66,7 @@ orders:
 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
-[Build & Deploy guide](/build-iapp/guides/build-&-deploy) in the Build iApp
+[Build & Deploy guide](/guides/build-iapp/build-&-deploy) in the Build iApp
 section.
 
 ## Detailed Guides

src/guides/use-iapp/how-to-pay-executions.md

@@ -120,10 +120,10 @@ const result = await dataProtectorCore.processProtectedData({
 
 ::: tip
 
-If your voucher doesn't have enough <TokenSymbol /> to cover the deal, the SDK will
-automatically get the required amount to your iExec account. Ensure that your
-voucher is authorized to access your iExec account and that your account has
-sufficient funds for this transfer to proceed.
+If your voucher doesn't have enough <TokenSymbol /> to cover the deal, the SDK
+will automatically get the required amount to your iExec account. Ensure that
+your voucher is authorized to access your iExec account and that your account
+has sufficient funds for this transfer to proceed.
 
 :::
 

src/guides/use-iapp/how-to-pay/how-to-pay-for-web3mail.md

@@ -52,8 +52,8 @@ contract to debit your account if the voucher balance is insufficient. This
 ensures that if the voucher alone doesn't cover the execution cost, the
 remaining balance is automatically deducted from your account.
 
-For additional information on using <TokenSymbol /> for fallback payment in Web3Mail, refer
-to the **Using <TokenSymbol /> with Web3Mail** section.
+For additional information on using <TokenSymbol /> for fallback payment in
+Web3Mail, refer to the **Using <TokenSymbol /> with Web3Mail** section.
 
 ### Step 4: Execute Web3Mail's SendEmail Function
 
@@ -75,9 +75,9 @@ const sendEmail = await web3mail.sendEmail({
 
 ## Using <TokenSymbol /> for Web3Mail
 
-If you choose to use <TokenSymbol /> to cover the computational cost of Web3Mail (or if you
-need to cover data access costs such as retrieving the recipient's email
-address), follow these steps:
+If you choose to use <TokenSymbol /> to cover the computational cost of Web3Mail
+(or if you need to cover data access costs such as retrieving the recipient's
+email address), follow these steps:
 
 ### Install the iExec SDK
 
@@ -97,9 +97,14 @@ const iexec = new IExec({ ethProvider: window.ethereum });
 
 ### Purchase RLC
 
-Obtain RLC tokens from a supported cryptocurrency exchange. For detailed information on how to buy RLC tokens, see our [RLC Token guide](/get-started/rlc) which covers all available DEX and CEX supported.
+Obtain RLC tokens from a supported cryptocurrency exchange. For detailed
+information on how to buy RLC tokens, see our
+[RLC Token guide](/get-started/rlc) which covers all available DEX and CEX
+supported.
 
-For detailed instructions on how to bridge RLC tokens between networks, see our [Bridge guide](/get-started/tooling-and-explorers/bridge) which covers all supported networks and bridging methods.
+For detailed instructions on how to bridge RLC tokens between networks, see our
+[Bridge guide](/get-started/tooling-and-explorers/bridge) which covers all
+supported networks and bridging methods.
 
 ### Deposit <TokenSymbol />
 
@@ -109,7 +114,8 @@ Deposit the <TokenSymbol /> into your iExec account using the command:
 iexec.account.deposit(RLC_amount);
 ```
 
-This converts <TokenSymbol /> into sRLC, used as proof of funds for task execution.
+This converts <TokenSymbol /> into sRLC, used as proof of funds for task
+execution.
 
 ### Check sRLC Balance
 

src/guides/use-iapp/how-to-pay/how-to-pay-for-web3telegram.md

@@ -1,8 +1,8 @@
 ---
 title: How to Pay for Web3Telegram
 description:
-  Learn how to pay for Web3Telegram's confidential computing power using vouchers
-  and RLC for secure, blockchain-based email communication.
+  Learn how to pay for Web3Telegram's confidential computing power using
+  vouchers and RLC for secure, blockchain-based email communication.
 ---
 
 # How to Pay for Web3Telegram
@@ -52,8 +52,8 @@ contract to debit your account if the voucher balance is insufficient. This
 ensures that if the voucher alone doesn't cover the execution cost, the
 remaining balance is automatically deducted from your account.
 
-For additional information on using <TokenSymbol /> for fallback payment in Web3Telegram,
-refer to the **Using <TokenSymbol /> with Web3Telegram** section.
+For additional information on using <TokenSymbol /> for fallback payment in
+Web3Telegram, refer to the **Using <TokenSymbol /> with Web3Telegram** section.
 
 ### Step 4: Execute Web3Telegram's `sendTelegram` Function
 
@@ -81,9 +81,9 @@ const sendTelegram = await web3telegram.sendTelegram({
 
 ## Using <TokenSymbol /> for Web3Telegram
 
-If you choose to use <TokenSymbol /> to cover the computational cost of Web3Telegram (or if
-you need to cover data access costs such as retrieving the recipient's Chat Id),
-follow these steps:
+If you choose to use <TokenSymbol /> to cover the computational cost of
+Web3Telegram (or if you need to cover data access costs such as retrieving the
+recipient's Chat Id), follow these steps:
 
 ### Install the iExec SDK
 
@@ -103,9 +103,14 @@ const iexec = new IExec({ ethProvider: window.ethereum });
 
 ### Purchase RLC
 
-Obtain RLC tokens from a supported cryptocurrency exchange. For detailed information on how to buy RLC tokens, see our [RLC Token guide](/get-started/rlc) which covers all available DEX and CEX supported.
+Obtain RLC tokens from a supported cryptocurrency exchange. For detailed
+information on how to buy RLC tokens, see our
+[RLC Token guide](/get-started/rlc) which covers all available DEX and CEX
+supported.
 
-For detailed instructions on how to bridge RLC tokens between networks, see our [Bridge guide](/get-started/tooling-and-explorers/bridge) which covers all supported networks and bridging methods.
+For detailed instructions on how to bridge RLC tokens between networks, see our
+[Bridge guide](/get-started/tooling-and-explorers/bridge) which covers all
+supported networks and bridging methods.
 
 ### Deposit <TokenSymbol />
 
@@ -115,7 +120,8 @@ Deposit the <TokenSymbol /> into your iExec account using the command:
 iexec.account.deposit(RLC_amount);
 ```
 
-This converts <TokenSymbol /> into sRLC, used as proof of funds for task execution.
+This converts <TokenSymbol /> into sRLC, used as proof of funds for task
+execution.
 
 ### Check sRLC Balance
 

src/guides/use-iapp/introduction.md

@@ -53,7 +53,8 @@ When a deal is triggered, the following sequence occurs:
 7. **Result Generation**: Computation results are generated
 8. **Result Delivery**: Results are returned to the requester through the
    network
-9. **Payment Settlement**: <TokenSymbol /> tokens are distributed to all participants
+9. **Payment Settlement**: <TokenSymbol /> tokens are distributed to all
+   participants
 
 ### Network Architecture Diagram
 
@@ -70,8 +71,8 @@ When a deal is triggered, the following sequence occurs:
 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**: <TokenSymbol /> tokens are distributed to all participants
-   based on completed tasks
+7. **Payment Distribution**: <TokenSymbol /> 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

src/references/dataProtector/dataProtectorCore/processProtectedData.md

@@ -153,10 +153,10 @@ const processProtectedDataResponse =
 
 ::: tip
 
-If your voucher doesn't have enough <TokenSymbol /> to cover the deal, the SDK will
-automatically get the required amount to your iExec account. Ensure that your
-voucher is authorized to access your iExec account and that your account has
-sufficient funds for this transfer to proceed.
+If your voucher doesn't have enough <TokenSymbol /> to cover the deal, the SDK
+will automatically get the required amount to your iExec account. Ensure that
+your voucher is authorized to access your iExec account and that your account
+has sufficient funds for this transfer to proceed.
 
 :::
 

src/references/dataProtector/types.md

@@ -17,8 +17,8 @@ Types in DataProtector.
 
 ### datasetprice: <span class="text-yellow">`string`</span>
 
-- Price (in n<TokenSymbol />) to charge the user specified in `requesterrestrict` for each
-  use of this `protectedData`
+- Price (in n<TokenSymbol />) to charge the user specified in
+  `requesterrestrict` for each use of this `protectedData`
 
 ### volume: <span class="text-yellow">`string`</span>