From bb96aac415d32114065bb5b506790dc1a7fdb5c7 Mon Sep 17 00:00:00 2001
From: Le-Caignec <robinlecaignec@yahoo.fr>
Date: Thu, 14 Aug 2025 14:22:55 +0200
Subject: [PATCH 01/27] refactor: update links in navigation and index, remove
 obsolete build iApp guide

---
 .vitepress/config.mts          |  2 +-
 src/guides/build-iapp/index.md | 42 ----------------------------------
 src/index.md                   |  4 ++--
 3 files changed, 3 insertions(+), 45 deletions(-)
 delete mode 100644 src/guides/build-iapp/index.md

diff --git a/.vitepress/config.mts b/.vitepress/config.mts
index 3aa45736..cf397fc8 100644
--- a/.vitepress/config.mts
+++ b/.vitepress/config.mts
@@ -99,7 +99,7 @@ export default defineConfig({
     // https://vitepress.dev/reference/default-theme-config
     nav: [
       { text: 'Get Started', link: '/get-started/welcome' },
-      { text: 'Guides', link: '/guides/build-iapp/' },
+      { text: 'Guides', link: '/guides/build-iapp/build-&-deploy' },
       { text: 'References', link: '/references/dataProtector' },
       {
         component: 'ChainSelector',
diff --git a/src/guides/build-iapp/index.md b/src/guides/build-iapp/index.md
deleted file mode 100644
index b9fc823a..00000000
--- a/src/guides/build-iapp/index.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Build iApp Guides
-description: Complete guide collection for building privacy-first iApps on iExec
----
-
-# 🛠️ Build iApp Guides
-
-Welcome to the complete collection of guides for building privacy-first
-applications on iExec. These guides will walk you through every aspect of
-creating, testing, and deploying confidential iApps.
-
-## 🚀 Getting Started
-
-- **[Build & Deploy](/guides/build-iapp/build-&-deploy)** - Your first iApp in
-  15 minutes
-- **[Inputs and Outputs](/guides/build-iapp/inputs-and-outputs)** - Handle data
-  flow in TEE environment
-- **[Debugging](/guides/build-iapp/debugging)** - Troubleshoot execution issues
-
-## 🔐 Access Control & Management
-
-- **[Manage Access](/guides/build-iapp/manage-access)** - Control who can use
-  your iApp
-- **[How to Get and Decrypt Results](/guides/build-iapp/how-to-get-and-decrypt-results)** -
-  Retrieve and use outputs
-
-## 🧪 Advanced Features
-
-- **[Using TDX (Experimental)](/guides/build-iapp/using-tdx)** - Next-gen TEE
-  technology
-
-## 📚 What's Next?
-
-After mastering these guides, explore:
-
-- **[iApp Generator](/references/iapp-generator)** - Complete development
-  toolkit
-- **[What is an iApp?](/get-started/overview/what-is-iapp)** - Core concepts and
-  TEE overview
-
-Ready to build your first privacy-preserving application? Start with the
-[Build & Deploy](/guides/build-iapp/build-&-deploy) guide!
diff --git a/src/index.md b/src/index.md
index 8d7bf0ac..6124f3d5 100644
--- a/src/index.md
+++ b/src/index.md
@@ -25,13 +25,13 @@ features:
     details:
       Secure your data with advanced encryption and control access while
       maintaining privacy using DataProtector
-    link: /get-started/overview/what-is-protected-data
+    link: /guides/manage-data/manage-access
   - icon: 🤖
     title: Build iApps
     details:
       Create decentralized applications that run on confidential computing
       infrastructure with our iApp Generator
-    link: /get-started/overview/what-is-iapp
+    link: /guides/build-iapp/build-&-deploy
   - icon: ⚡
     title: Use iApps
     details:

From 31c836ac0a1d9560ccb4f8625f34c82df6daf039 Mon Sep 17 00:00:00 2001
From: Le-Caignec <robinlecaignec@yahoo.fr>
Date: Thu, 14 Aug 2025 14:27:48 +0200
Subject: [PATCH 02/27] refactor: update payment link in index to point to
 executions guide

---
 src/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/index.md b/src/index.md
index 6124f3d5..b894152e 100644
--- a/src/index.md
+++ b/src/index.md
@@ -43,7 +43,7 @@ features:
     details:
       Create revenue streams from your data while maintaining full control and
       privacy
-    link: /guides/use-iapp/how-to-pay/how-to-pay-for-web3mail
+    link: /guides/use-iapp/how-to-pay-executions
   - icon: 🧠
     title: Protocols
     details:

From 864defbfcde53e086642c72d7a95a65e87d0ae11 Mon Sep 17 00:00:00 2001
From: Le-Caignec <robinlecaignec@yahoo.fr>
Date: Thu, 14 Aug 2025 14:30:50 +0200
Subject: [PATCH 03/27] chore: remove obsolete build iApp guide

---
 src/build-iapp/guides/build-&-deploy.md | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 delete mode 100644 src/build-iapp/guides/build-&-deploy.md

diff --git a/src/build-iapp/guides/build-&-deploy.md b/src/build-iapp/guides/build-&-deploy.md
deleted file mode 100644
index e69de29b..00000000

From f35b3c6e982d8497a87eb394a86205d51d23ca39 Mon Sep 17 00:00:00 2001
From: Le-Caignec <robinlecaignec@yahoo.fr>
Date: Thu, 14 Aug 2025 15:09:57 +0200
Subject: [PATCH 04/27] feat: enhance iApp deployment guide with chain
 selection and dynamic steps

Updated the deployment process to support multiple chains by introducing a conditional template for Arbitrum and Bellecour. Added dynamic steps and completion items for each chain to improve user experience during deployment.
---
 src/guides/build-iapp/build-&-deploy.md | 270 +++++++++++++++++-------
 1 file changed, 190 insertions(+), 80 deletions(-)

diff --git a/src/guides/build-iapp/build-&-deploy.md b/src/guides/build-iapp/build-&-deploy.md
index a655b1ad..c037f4b1 100644
--- a/src/guides/build-iapp/build-&-deploy.md
+++ b/src/guides/build-iapp/build-&-deploy.md
@@ -194,86 +194,31 @@ After your tests pass and the package is built, you can deploy your iApp to a
 supported network. During deployment, you'll enter your DockerHub credentials,
 specify your app version, and push both standard and TEE-compatible images:
 
-<CLIDemo
-  initialCommand="iapp deploy"
-  asciiText="Deploy"
-  :steps="[
-    {
-      showAt: 2,
-      question: 'Using chain bellecour',
-      answer: '',
-      showTyping: false,
-      isComplete: true
-    },
-    {
-      showAt: 3,
-      question: 'Using saved walletPrivateKey (from iapp.config.json)',
-      answer: '',
-      showTyping: false,
-      isComplete: true
-    },
-    {
-      showAt: 4,
-      completeAt: 6,
-      question: 'What is your username on DockerHub? (It will be used to properly tag the Docker image)',
-      answer: 'bob',
-      showTyping: true,
-      isComplete: false
-    },
-    {
-      showAt: 6,
-      completeAt: 8,
-      question: 'What is your DockerHub access token?',
-      answer: '**********************',
-      showTyping: true,
-      isComplete: false
-    },
-    {
-      showAt: 8,
-      completeAt: 10,
-      question: 'What is the version of your iApp?',
-      answer: '0.0.1',
-      showTyping: true,
-      isComplete: false
-    },
-    {
-      showAt: 10,
-      question: 'Docker image built (sha256:a53fc4c480f482c384a13266ea2cb6cc5572733c866c44a5f604f4bfab3a744a) and tagged bob/hello-world:0.0.1',
-      answer: '',
-      showTyping: false,
-      isComplete: true
-    },
-    {
-      showAt: 11,
-      question: 'Pushed image bob/hello-world:0.0.1 on dockerhub',
-      answer: '',
-      showTyping: false,
-      isComplete: true
-    },
-    {
-      showAt: 12,
-      question: 'Pushed TEE image bob/hello-world:0.0.1-tee-scone-5.9.1-v16-debug-ce3a01d9c5d7 on dockerhub',
-      answer: '',
-      showTyping: false,
-      isComplete: true
-    },
-    {
-      showAt: 13,
-      question: 'TEE app deployed',
-      answer: '',
-      showTyping: false,
-      isComplete: true
-    }
-  ]"
-  :completionStep="14"
-  :completionMessage="'Deployment of your iApp completed successfully:'"
-  :completionItems="[
-    '└ Docker image: bob/hello-world:0.0.1-tee-scone-5.9.1-v16-debug-ce3a01d9c5d7',
-    '└ iApp address: 0x1f80DCebc2EAAff0Db7156413C43B7e88D189923'
-  ]"
-  :successMessage="'Run iapp run 0x1f80DCebc2EAAff0Db7156413C43B7e88D189923 to execute your iApp on an iExec TEE worker'"
-  :autoRestart="true"
-/>
+<template v-if="selectedChain === 42161">
+  <CLIDemo
+    initialCommand="iapp deploy --chain arbitrum-mainnet"
+    asciiText="Deploy"
+    :steps="arbitrumSteps"
+    :completionStep="15"
+    :completionMessage="'Deployment of your iApp completed successfully:'"
+    :completionItems="arbitrumCompletionItems"
+    :successMessage="'Run iapp run 0x1f80DCebc2EAAff0Db7156413C43B7e88D189923 to execute your iApp on an iExec TEE worker'"
+    :autoRestart="true"
+  />
+</template>
+
+<template v-else>
+  <CLIDemo
+    initialCommand="iapp deploy"
+    asciiText="Deploy"
+    :steps="bellecourSteps"
+    :completionStep="14"
+    :completionMessage="'Deployment of your iApp completed successfully:'"
+    :completionItems="bellecourCompletionItems"
+    :successMessage="'Run iapp run 0x1f80DCebc2EAAff0Db7156413C43B7e88D189923 to execute your iApp on an iExec TEE worker'"
+    :autoRestart="true"
+  />
+</template>
 
 ## Real Examples
 
@@ -359,4 +304,169 @@ for month in range(12):
 
 <script setup>
 import CLIDemo from '@/components/CLIDemo.vue';
+import { computed } from 'vue';
+import useUserStore from '@/stores/useUser.store';
+
+const userStore = useUserStore();
+const selectedChain = computed(() => userStore.getCurrentChainId());
+
+const arbitrumSteps = [
+  {
+    showAt: 2,
+    question: 'Using chain arbitrum-mainnet',
+    answer: '',
+    showTyping: false,
+    isComplete: true
+  },
+  {
+    showAt: 3,
+    question: 'This method requires sending blockchain transactions, transaction fees will be applied. Would you like to continue?',
+    answer: 'Yes',
+    options: [
+      { label: 'Yes', selected: true },
+      { label: 'no', selected: false }
+    ],
+    highlighted: false,
+    showTyping: false,
+    isComplete: false
+  },
+  {
+    showAt: 4,
+    question: 'Using saved walletPrivateKey (from iapp.config.json)',
+    answer: '',
+    showTyping: false,
+    isComplete: true
+  },
+  {
+    showAt: 5,
+    completeAt: 7,
+    question: 'What is your username on DockerHub? (It will be used to properly tag the Docker image)',
+    answer: 'bob',
+    showTyping: true,
+    isComplete: false
+  },
+  {
+    showAt: 7,
+    completeAt: 9,
+    question: 'What is your DockerHub access token?',
+    answer: '**********************',
+    showTyping: true,
+    isComplete: false
+  },
+  {
+    showAt: 9,
+    completeAt: 11,
+    question: 'What is the version of your iApp?',
+    answer: '0.0.1',
+    showTyping: true,
+    isComplete: false
+  },
+  {
+    showAt: 11,
+    question: 'Docker image built (sha256:a53fc4c480f482c384a13266ea2cb6cc5572733c866c44a5f604f4bfab3a744a) and tagged bob/hello-world:0.0.1',
+    answer: '',
+    showTyping: false,
+    isComplete: true
+  },
+  {
+    showAt: 12,
+    question: 'Pushed image bob/hello-world:0.0.1 on dockerhub',
+    answer: '',
+    showTyping: false,
+    isComplete: true
+  },
+  {
+    showAt: 13,
+    question: 'Pushed TEE image bob/hello-world:0.0.1-tee-scone-5.9.1-v16-debug-ce3a01d9c5d7 on dockerhub',
+    answer: '',
+    showTyping: false,
+    isComplete: true
+  },
+  {
+    showAt: 14,
+    question: 'TEE app deployed',
+    answer: '',
+    showTyping: false,
+    isComplete: true
+  }
+];
+
+const bellecourSteps = [
+  {
+    showAt: 2,
+    question: 'Using chain bellecour',
+    answer: '',
+    showTyping: false,
+    isComplete: true
+  },
+  {
+    showAt: 3,
+    question: 'Using saved walletPrivateKey (from iapp.config.json)',
+    answer: '',
+    showTyping: false,
+    isComplete: true
+  },
+  {
+    showAt: 4,
+    completeAt: 6,
+    question: 'What is your username on DockerHub? (It will be used to properly tag the Docker image)',
+    answer: 'bob',
+    showTyping: true,
+    isComplete: false
+  },
+  {
+    showAt: 6,
+    completeAt: 8,
+    question: 'What is your DockerHub access token?',
+    answer: '**********************',
+    showTyping: true,
+    isComplete: false
+  },
+  {
+    showAt: 8,
+    completeAt: 10,
+    question: 'What is the version of your iApp?',
+    answer: '0.0.1',
+    showTyping: true,
+    isComplete: false
+  },
+  {
+    showAt: 10,
+    question: 'Docker image built (sha256:a53fc4c480f482c384a13266ea2cb6cc5572733c866c44a5f604f4bfab3a744a) and tagged bob/hello-world:0.0.1',
+    answer: '',
+    showTyping: false,
+    isComplete: true
+  },
+  {
+    showAt: 11,
+    question: 'Pushed image bob/hello-world:0.0.1 on dockerhub',
+    answer: '',
+    showTyping: false,
+    isComplete: true
+  },
+  {
+    showAt: 12,
+    question: 'Pushed TEE image bob/hello-world:0.0.1-tee-scone-5.9.1-v16-debug-ce3a01d9c5d7 on dockerhub',
+    answer: '',
+    showTyping: false,
+    isComplete: true
+  },
+  {
+    showAt: 13,
+    question: 'TEE app deployed',
+    answer: '',
+    showTyping: false,
+    isComplete: true
+  }
+];
+
+const arbitrumCompletionItems = [
+  '└ Docker image: bob/hello-world:0.0.1-tee-scone-5.9.1-v16-debug-ce3a01d9c5d7',
+  '└ iApp address: 0x1f80DCebc2EAAff0Db7156413C43B7e88D189923'
+];
+
+const bellecourCompletionItems = [
+  '└ Docker image: bob/hello-world:0.0.1-tee-scone-5.9.1-v16-debug-ce3a01d9c5d7',
+  '└ iApp address: 0x1f80DCebc2EAAff0Db7156413C43B7e88D189923'
+];
 </script>

From 2c795553492d486eab1e25bab4e8ba58ec26a19d Mon Sep 17 00:00:00 2001
From: Le-Caignec <robinlecaignec@yahoo.fr>
Date: Thu, 14 Aug 2025 16:42:53 +0200
Subject: [PATCH 05/27] fix: update badges in processProtectedData
 documentation

Modified the documentation to include a ChainNotSupportedBadge for the useVoucher parameter and corrected the formatting for the app parameter. Added a script section for badge imports to enhance clarity and maintainability.
---
 src/components/ChainNotSupportedBadge.vue     | 29 +++++++++++++++++++
 .../dataProtectorCore/processProtectedData.md | 10 +++++--
 2 files changed, 37 insertions(+), 2 deletions(-)
 create mode 100644 src/components/ChainNotSupportedBadge.vue

diff --git a/src/components/ChainNotSupportedBadge.vue b/src/components/ChainNotSupportedBadge.vue
new file mode 100644
index 00000000..1bea99e8
--- /dev/null
+++ b/src/components/ChainNotSupportedBadge.vue
@@ -0,0 +1,29 @@
+<script setup>
+import { computed } from 'vue';
+import { VPBadge } from 'vitepress/theme';
+import useUserStore from '@/stores/useUser.store';
+
+const userStore = useUserStore();
+
+// Check if Arbitrum is selected (Arbitrum chain ID is 42161)
+const isArbitrumSelected = computed(() => {
+  return userStore.chainId === 42161;
+});
+
+// Only show the badge when Arbitrum is selected
+const shouldShow = computed(() => isArbitrumSelected.value);
+</script>
+
+<template>
+  <VPBadge
+    v-if="shouldShow"
+    type="warning"
+    text="Not Supported for this Chain"
+    style="
+      color: var(--vp-c-orange-1);
+      background-color: hsla(0, 100%, 50%, 8%);
+      margin-top: 1px;
+      margin-right: 4px;
+    "
+  />
+</template>
diff --git a/src/references/dataProtector/dataProtectorCore/processProtectedData.md b/src/references/dataProtector/dataProtectorCore/processProtectedData.md
index de1ca5b0..6289ba4d 100644
--- a/src/references/dataProtector/dataProtectorCore/processProtectedData.md
+++ b/src/references/dataProtector/dataProtectorCore/processProtectedData.md
@@ -64,7 +64,7 @@ const processProtectedDataResponse =
   });
 ```
 
-### app <RequiredBadge /> {#app-param}
+### app <RequiredBadge />
 
 **Type:** `AddressOrENS`
 
@@ -128,7 +128,7 @@ const processProtectedDataResponse =
   });
 ```
 
-### useVoucher <OptionalBadge />
+### useVoucher <ChainNotSupportedBadge /> <OptionalBadge />
 
 **Type:** `boolean`  
 **Default:** `false`
@@ -495,3 +495,9 @@ include a file named **content**, which corresponds to the protected data
 processed during the task.
 
 :::
+
+<script setup>
+import RequiredBadge from '@/components/RequiredBadge.vue'
+import OptionalBadge from '@/components/OptionalBadge.vue'
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
+</script>

From 9904b8c7f6d65dffbb70004bb6f043a3db971522 Mon Sep 17 00:00:00 2001
From: Le-Caignec <robinlecaignec@yahoo.fr>
Date: Thu, 14 Aug 2025 17:18:36 +0200
Subject: [PATCH 06/27] fix: update background color for ChainNotSupportedBadge

Adjusted the background color of the ChainNotSupportedBadge component to improve visibility and consistency with design standards.
---
 src/components/ChainNotSupportedBadge.vue | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/components/ChainNotSupportedBadge.vue b/src/components/ChainNotSupportedBadge.vue
index 1bea99e8..27737ebc 100644
--- a/src/components/ChainNotSupportedBadge.vue
+++ b/src/components/ChainNotSupportedBadge.vue
@@ -21,7 +21,7 @@ const shouldShow = computed(() => isArbitrumSelected.value);
     text="Not Supported for this Chain"
     style="
       color: var(--vp-c-orange-1);
-      background-color: hsla(0, 100%, 50%, 8%);
+      background-color: hsla(0, 100%, 70%, 8%);
       margin-top: 1px;
       margin-right: 4px;
     "

From 57eee4b3aee8baf87490dcfeefdedda6fd1c31b5 Mon Sep 17 00:00:00 2001
From: Le-Caignec <robinlecaignec@yahoo.fr>
Date: Thu, 14 Aug 2025 17:18:43 +0200
Subject: [PATCH 07/27] docs: update README and enhance data protection
 documentation

Added explanations for TDX vs SGX, a recap of Workerpool addresses for chains, and noted ENS support on Bellecour in the README. Enhanced various data protection documentation files by importing RequiredBadge and OptionalBadge components for better clarity and consistency.
---
 README.md                                                  | 3 +++
 src/components/ChainNotSupportedBadge.vue                  | 2 +-
 src/guides/manage-data/manage-access.md                    | 5 +++++
 .../advanced/apps-whitelist/addAppToAddOnlyAppWhitelist.md | 4 ++++
 .../advanced/apps-whitelist/getUserAddOnlyAppWhitelist.md  | 4 ++++
 .../dataProtector/dataProtectorCore/getGrantedAccess.md    | 4 ++++
 .../dataProtector/dataProtectorCore/getProtectedData.md    | 4 ++++
 .../dataProtectorCore/getResultFromCompletedTask.md        | 7 +++++++
 .../dataProtector/dataProtectorCore/grantAccess.md         | 5 +++++
 .../dataProtector/dataProtectorCore/protectData.md         | 2 ++
 .../dataProtector/dataProtectorCore/revokeAllAccess.md     | 5 +++++
 .../dataProtector/dataProtectorCore/revokeOneAccess.md     | 4 ++++
 .../dataProtector/dataProtectorCore/transferOwnership.md   | 4 ++++
 .../dataProtectorSharing/collection/addToCollection.md     | 5 +++++
 .../dataProtectorSharing/collection/removeCollection.md    | 4 ++++
 .../collection/removeProtectedDataFromCollection.md        | 4 ++++
 .../dataProtectorSharing/consume/consumeProtectedData.md   | 2 ++
 .../dataProtectorSharing/read/getCollectionOwners.md       | 4 ++++
 .../read/getCollectionSubscriptions.md                     | 4 ++++
 .../dataProtectorSharing/read/getCollectionsByOwner.md     | 5 +++++
 .../read/getProtectedDataInCollections.md                  | 4 ++++
 .../read/getProtectedDataPricingParams.md                  | 4 ++++
 .../dataProtector/dataProtectorSharing/read/getRentals.md  | 4 ++++
 .../renting/removeProtectedDataFromRenting.md              | 4 ++++
 .../dataProtectorSharing/renting/rentProtectedData.md      | 4 ++++
 .../renting/setProtectedDataToRenting.md                   | 4 ++++
 .../dataProtectorSharing/selling/buyProtectedData.md       | 5 +++++
 .../selling/removeProtectedDataForSale.md                  | 4 ++++
 .../selling/setProtectedDataForSale.md                     | 4 ++++
 .../subscription/removeProtectedDataFromSubscription.md    | 4 ++++
 .../subscription/setProtectedDataToSubscription.md         | 4 ++++
 .../subscription/setSubscriptionParams.md                  | 4 ++++
 .../subscription/subscribeToCollection.md                  | 4 ++++
 src/references/web3mail/methods/fetchMyContacts.md         | 4 ++++
 src/references/web3mail/methods/fetchUserContacts.md       | 4 ++++
 src/references/web3mail/methods/sendEmail.md               | 5 +++++
 src/references/web3telegram/methods/fetchMyContacts.md     | 4 ++++
 src/references/web3telegram/methods/fetchUserContacts.md   | 4 ++++
 src/references/web3telegram/methods/sendTelegram.md        | 6 ++++++
 39 files changed, 160 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index cedd359a..d189c831 100644
--- a/README.md
+++ b/README.md
@@ -192,3 +192,6 @@ for input parameters:
 - migrate github SDK doc here
 - migrate pay-per-task page into a guide
 - check pages (introduction & getting-started) for use-iapp guide
+- explain TDX vs SGX
+- Give recap of Workerpool address fo chains
+- Talk about ENS on Bellecour(it's not supported on arbitrum)
diff --git a/src/components/ChainNotSupportedBadge.vue b/src/components/ChainNotSupportedBadge.vue
index 27737ebc..bae437a2 100644
--- a/src/components/ChainNotSupportedBadge.vue
+++ b/src/components/ChainNotSupportedBadge.vue
@@ -21,7 +21,7 @@ const shouldShow = computed(() => isArbitrumSelected.value);
     text="Not Supported for this Chain"
     style="
       color: var(--vp-c-orange-1);
-      background-color: hsla(0, 100%, 70%, 8%);
+      background-color: hsla(15, 100%, 40%, 8%);
       margin-top: 1px;
       margin-right: 4px;
     "
diff --git a/src/guides/manage-data/manage-access.md b/src/guides/manage-data/manage-access.md
index 7486e25e..d0d0deb1 100644
--- a/src/guides/manage-data/manage-access.md
+++ b/src/guides/manage-data/manage-access.md
@@ -228,3 +228,8 @@ steps:
   [schemas and dataset types](/guides/manage-data/handle-schemas-dataset-types)
 - **Monetize data**: Explore
   [data monetization strategies](/guides/manage-data/monetize-protected-data)
+
+<script setup>
+import RequiredBadge from '@/components/RequiredBadge.vue'
+import OptionalBadge from '@/components/OptionalBadge.vue'
+</script>
diff --git a/src/references/dataProtector/advanced/apps-whitelist/addAppToAddOnlyAppWhitelist.md b/src/references/dataProtector/advanced/apps-whitelist/addAppToAddOnlyAppWhitelist.md
index e56acb39..f6e93993 100644
--- a/src/references/dataProtector/advanced/apps-whitelist/addAppToAddOnlyAppWhitelist.md
+++ b/src/references/dataProtector/advanced/apps-whitelist/addAppToAddOnlyAppWhitelist.md
@@ -96,3 +96,7 @@ import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
 See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+
+<script setup>
+import RequiredBadge from '@/components/RequiredBadge.vue'
+</script>
diff --git a/src/references/dataProtector/advanced/apps-whitelist/getUserAddOnlyAppWhitelist.md b/src/references/dataProtector/advanced/apps-whitelist/getUserAddOnlyAppWhitelist.md
index 9472a2b3..fe34dafb 100644
--- a/src/references/dataProtector/advanced/apps-whitelist/getUserAddOnlyAppWhitelist.md
+++ b/src/references/dataProtector/advanced/apps-whitelist/getUserAddOnlyAppWhitelist.md
@@ -59,3 +59,7 @@ import { type GetUserAppWhitelistResponse } from '@iexec/dataprotector';
 // Child types
 import { type AddOnlyAppWhitelist } from '@iexec/dataprotector';
 ```
+
+<script setup>
+import OptionalBadge from '@/components/OptionalBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorCore/getGrantedAccess.md b/src/references/dataProtector/dataProtectorCore/getGrantedAccess.md
index 2ee47134..a2755b91 100644
--- a/src/references/dataProtector/dataProtectorCore/getGrantedAccess.md
+++ b/src/references/dataProtector/dataProtectorCore/getGrantedAccess.md
@@ -217,3 +217,7 @@ smaller than the page size.
 **Type:** GrantedAccess
 
 See [`GrantedAccess`](../types.md#grantedaccess)
+
+<script setup>
+import OptionalBadge from '@/components/OptionalBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorCore/getProtectedData.md b/src/references/dataProtector/dataProtectorCore/getProtectedData.md
index a25f42ae..b8578125 100644
--- a/src/references/dataProtector/dataProtectorCore/getProtectedData.md
+++ b/src/references/dataProtector/dataProtectorCore/getProtectedData.md
@@ -191,3 +191,7 @@ import { type ProtectedData } from '@iexec/dataprotector';
 ```
 
 See [`ProtectedData`](../types.md#protecteddata)
+
+<script setup>
+import OptionalBadge from '@/components/OptionalBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorCore/getResultFromCompletedTask.md b/src/references/dataProtector/dataProtectorCore/getResultFromCompletedTask.md
index 121b5152..3ee3eacc 100644
--- a/src/references/dataProtector/dataProtectorCore/getResultFromCompletedTask.md
+++ b/src/references/dataProtector/dataProtectorCore/getResultFromCompletedTask.md
@@ -134,3 +134,10 @@ import { type GetResultFromCompletedTaskResponse } from '@iexec/dataprotector';
 `ArrayBuffer`
 
 The actual content of the protected file.
+
+```
+
+<script setup>
+import RequiredBadge from '@/components/RequiredBadge.vue'
+import OptionalBadge from '@/components/OptionalBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorCore/grantAccess.md b/src/references/dataProtector/dataProtectorCore/grantAccess.md
index cfa8e79f..effb7a4f 100644
--- a/src/references/dataProtector/dataProtectorCore/grantAccess.md
+++ b/src/references/dataProtector/dataProtectorCore/grantAccess.md
@@ -250,3 +250,8 @@ The result of this method confirms the new access grant. It consists of a JSON
 `grantedAccess` object.
 
 [`GrantedAccess`](../types.md#grantedaccess)
+
+<script setup>
+import RequiredBadge from '@/components/RequiredBadge.vue'
+import OptionalBadge from '@/components/OptionalBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorCore/protectData.md b/src/references/dataProtector/dataProtectorCore/protectData.md
index 16c798f3..1f047598 100644
--- a/src/references/dataProtector/dataProtectorCore/protectData.md
+++ b/src/references/dataProtector/dataProtectorCore/protectData.md
@@ -439,4 +439,6 @@ To further check your data was correctly created, you can inspect it on the
 <script setup>
 // Assets
 import explorerDatasetImage from '@/assets/explorer-dataset-example.png';
+import RequiredBadge from '@/components/RequiredBadge.vue'
+import OptionalBadge from '@/components/OptionalBadge.vue'
 </script>
diff --git a/src/references/dataProtector/dataProtectorCore/revokeAllAccess.md b/src/references/dataProtector/dataProtectorCore/revokeAllAccess.md
index becf31c3..3275ea34 100644
--- a/src/references/dataProtector/dataProtectorCore/revokeAllAccess.md
+++ b/src/references/dataProtector/dataProtectorCore/revokeAllAccess.md
@@ -141,3 +141,8 @@ import { type RevokedAccess } from '@iexec/dataprotector';
 ```
 
 [`RevokedAccess[]`](../types.md#revokedaccess)
+
+<script setup>
+import RequiredBadge from '@/components/RequiredBadge.vue'
+import OptionalBadge from '@/components/OptionalBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorCore/revokeOneAccess.md b/src/references/dataProtector/dataProtectorCore/revokeOneAccess.md
index 866de9fe..5ff6909a 100644
--- a/src/references/dataProtector/dataProtectorCore/revokeOneAccess.md
+++ b/src/references/dataProtector/dataProtectorCore/revokeOneAccess.md
@@ -89,3 +89,7 @@ import { type RevokedAccess } from '@iexec/dataprotector';
 ```
 
 [`RevokedAccess`](../types.md#revokedaccess)
+
+<script setup>
+import RequiredBadge from '@/components/RequiredBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorCore/transferOwnership.md b/src/references/dataProtector/dataProtectorCore/transferOwnership.md
index 9ce7f33b..41d89eed 100644
--- a/src/references/dataProtector/dataProtectorCore/transferOwnership.md
+++ b/src/references/dataProtector/dataProtectorCore/transferOwnership.md
@@ -103,3 +103,7 @@ The ETH address of the new owner of the `protectedData`.
 
 The ID of the transaction that happened on iExec's side chain. You may view
 details on the transaction using the [iExec explorer](https://explorer.iex.ec).
+
+<script setup>
+import RequiredBadge from '@/components/RequiredBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorSharing/collection/addToCollection.md b/src/references/dataProtector/dataProtectorSharing/collection/addToCollection.md
index 05ccde21..72249928 100644
--- a/src/references/dataProtector/dataProtectorSharing/collection/addToCollection.md
+++ b/src/references/dataProtector/dataProtectorSharing/collection/addToCollection.md
@@ -164,3 +164,8 @@ import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
 See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+
+<script setup>
+import RequiredBadge from '@/components/RequiredBadge.vue'
+import OptionalBadge from '@/components/OptionalBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorSharing/collection/removeCollection.md b/src/references/dataProtector/dataProtectorSharing/collection/removeCollection.md
index 64a24b3f..b34454ab 100644
--- a/src/references/dataProtector/dataProtectorSharing/collection/removeCollection.md
+++ b/src/references/dataProtector/dataProtectorSharing/collection/removeCollection.md
@@ -68,3 +68,7 @@ import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
 See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+
+<script setup>
+import RequiredBadge from '@/components/RequiredBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorSharing/collection/removeProtectedDataFromCollection.md b/src/references/dataProtector/dataProtectorSharing/collection/removeProtectedDataFromCollection.md
index fde983da..f6f24e95 100644
--- a/src/references/dataProtector/dataProtectorSharing/collection/removeProtectedDataFromCollection.md
+++ b/src/references/dataProtector/dataProtectorSharing/collection/removeProtectedDataFromCollection.md
@@ -74,3 +74,7 @@ import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
 See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+
+<script setup>
+import RequiredBadge from '@/components/RequiredBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorSharing/consume/consumeProtectedData.md b/src/references/dataProtector/dataProtectorSharing/consume/consumeProtectedData.md
index 944a7198..aefeedce 100644
--- a/src/references/dataProtector/dataProtectorSharing/consume/consumeProtectedData.md
+++ b/src/references/dataProtector/dataProtectorSharing/consume/consumeProtectedData.md
@@ -8,6 +8,8 @@ description:
 
 <script setup>
 import { Icon } from '@iconify/vue';
+import RequiredBadge from '@/components/RequiredBadge.vue'
+import OptionalBadge from '@/components/OptionalBadge.vue'
 </script>
 
 # consumeProtectedData
diff --git a/src/references/dataProtector/dataProtectorSharing/read/getCollectionOwners.md b/src/references/dataProtector/dataProtectorSharing/read/getCollectionOwners.md
index f8bc117b..9bf0320c 100644
--- a/src/references/dataProtector/dataProtectorSharing/read/getCollectionOwners.md
+++ b/src/references/dataProtector/dataProtectorSharing/read/getCollectionOwners.md
@@ -68,3 +68,7 @@ Type ↗️</a>
 
 `true` if you (logged-in user) have an active subscription to one of the
 collections.
+
+<script setup>
+import OptionalBadge from '@/components/OptionalBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorSharing/read/getCollectionSubscriptions.md b/src/references/dataProtector/dataProtectorSharing/read/getCollectionSubscriptions.md
index 40f15f26..ce3e0c97 100644
--- a/src/references/dataProtector/dataProtectorSharing/read/getCollectionSubscriptions.md
+++ b/src/references/dataProtector/dataProtectorSharing/read/getCollectionSubscriptions.md
@@ -104,3 +104,7 @@ import { type CollectionSubscription } from '@iexec/dataprotector';
 
 <a href="https://github.com/iExecBlockchainComputing/dataprotector-sdk/blob/c83e30e6ce8b55ecf8a35ecb4eb1014cd4ecefe9/packages/sdk/src/lib/types/sharingTypes.ts" target="_blank">See
 Type ↗️</a>
+
+<script setup>
+import OptionalBadge from '@/components/OptionalBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorSharing/read/getCollectionsByOwner.md b/src/references/dataProtector/dataProtectorSharing/read/getCollectionsByOwner.md
index 06970e70..e8ae57ca 100644
--- a/src/references/dataProtector/dataProtectorSharing/read/getCollectionsByOwner.md
+++ b/src/references/dataProtector/dataProtectorSharing/read/getCollectionsByOwner.md
@@ -87,3 +87,8 @@ import type {
 
 <a href="https://github.com/iExecBlockchainComputing/dataprotector-sdk/blob/c83e30e6ce8b55ecf8a35ecb4eb1014cd4ecefe9/packages/sdk/src/lib/types/sharingTypes.ts" target="_blank">See
 Type ↗️</a>
+
+<script setup>
+import RequiredBadge from '@/components/RequiredBadge.vue'
+import OptionalBadge from '@/components/OptionalBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorSharing/read/getProtectedDataInCollections.md b/src/references/dataProtector/dataProtectorSharing/read/getProtectedDataInCollections.md
index 1e77e275..503afa0d 100644
--- a/src/references/dataProtector/dataProtectorSharing/read/getProtectedDataInCollections.md
+++ b/src/references/dataProtector/dataProtectorSharing/read/getProtectedDataInCollections.md
@@ -227,3 +227,7 @@ import type {
 
 <a href="https://github.com/iExecBlockchainComputing/dataprotector-sdk/blob/c83e30e6ce8b55ecf8a35ecb4eb1014cd4ecefe9/packages/sdk/src/lib/types/sharingTypes.ts" target="_blank">See
 Type ↗️</a>
+
+<script setup>
+import OptionalBadge from '@/components/OptionalBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorSharing/read/getProtectedDataPricingParams.md b/src/references/dataProtector/dataProtectorSharing/read/getProtectedDataPricingParams.md
index 68e53d18..7cafca5b 100644
--- a/src/references/dataProtector/dataProtectorSharing/read/getProtectedDataPricingParams.md
+++ b/src/references/dataProtector/dataProtectorSharing/read/getProtectedDataPricingParams.md
@@ -63,3 +63,7 @@ import type { SubscriptionParams, RentingParams } from '@iexec/dataprotector';
 
 <a href="https://github.com/iExecBlockchainComputing/dataprotector-sdk/blob/c83e30e6ce8b55ecf8a35ecb4eb1014cd4ecefe9/packages/sdk/src/lib/types/sharingTypes.ts" target="_blank">See
 Type ↗️</a>
+
+<script setup>
+import RequiredBadge from '@/components/RequiredBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorSharing/read/getRentals.md b/src/references/dataProtector/dataProtectorSharing/read/getRentals.md
index 7fe042ce..9d4377de 100644
--- a/src/references/dataProtector/dataProtectorSharing/read/getRentals.md
+++ b/src/references/dataProtector/dataProtectorSharing/read/getRentals.md
@@ -101,3 +101,7 @@ import type { ProtectedDataRental } from '@iexec/dataprotector';
 
 <a href="https://github.com/iExecBlockchainComputing/dataprotector-sdk/blob/c83e30e6ce8b55ecf8a35ecb4eb1014cd4ecefe9/packages/sdk/src/lib/types/sharingTypes.ts" target="_blank">See
 Type ↗️</a>
+
+<script setup>
+import OptionalBadge from '@/components/OptionalBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorSharing/renting/removeProtectedDataFromRenting.md b/src/references/dataProtector/dataProtectorSharing/renting/removeProtectedDataFromRenting.md
index 7bc1b923..701e756d 100644
--- a/src/references/dataProtector/dataProtectorSharing/renting/removeProtectedDataFromRenting.md
+++ b/src/references/dataProtector/dataProtectorSharing/renting/removeProtectedDataFromRenting.md
@@ -64,3 +64,7 @@ import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
 See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+
+<script setup>
+import RequiredBadge from '@/components/RequiredBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorSharing/renting/rentProtectedData.md b/src/references/dataProtector/dataProtectorSharing/renting/rentProtectedData.md
index d717bfbb..8d023c85 100644
--- a/src/references/dataProtector/dataProtectorSharing/renting/rentProtectedData.md
+++ b/src/references/dataProtector/dataProtectorSharing/renting/rentProtectedData.md
@@ -137,3 +137,7 @@ import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
 See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+
+<script setup>
+import RequiredBadge from '@/components/RequiredBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorSharing/renting/setProtectedDataToRenting.md b/src/references/dataProtector/dataProtectorSharing/renting/setProtectedDataToRenting.md
index c430fbfb..2f50f299 100644
--- a/src/references/dataProtector/dataProtectorSharing/renting/setProtectedDataToRenting.md
+++ b/src/references/dataProtector/dataProtectorSharing/renting/setProtectedDataToRenting.md
@@ -116,3 +116,7 @@ import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
 See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+
+<script setup>
+import RequiredBadge from '@/components/RequiredBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorSharing/selling/buyProtectedData.md b/src/references/dataProtector/dataProtectorSharing/selling/buyProtectedData.md
index 7a8bd0c9..c50c5435 100644
--- a/src/references/dataProtector/dataProtectorSharing/selling/buyProtectedData.md
+++ b/src/references/dataProtector/dataProtectorSharing/selling/buyProtectedData.md
@@ -162,3 +162,8 @@ import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
 See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+
+<script setup>
+import RequiredBadge from '@/components/RequiredBadge.vue'
+import OptionalBadge from '@/components/OptionalBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorSharing/selling/removeProtectedDataForSale.md b/src/references/dataProtector/dataProtectorSharing/selling/removeProtectedDataForSale.md
index 73b7b71a..568a45bd 100644
--- a/src/references/dataProtector/dataProtectorSharing/selling/removeProtectedDataForSale.md
+++ b/src/references/dataProtector/dataProtectorSharing/selling/removeProtectedDataForSale.md
@@ -60,3 +60,7 @@ import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
 See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+
+<script setup>
+import RequiredBadge from '@/components/RequiredBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorSharing/selling/setProtectedDataForSale.md b/src/references/dataProtector/dataProtectorSharing/selling/setProtectedDataForSale.md
index 7d0081d9..76d7cdde 100644
--- a/src/references/dataProtector/dataProtectorSharing/selling/setProtectedDataForSale.md
+++ b/src/references/dataProtector/dataProtectorSharing/selling/setProtectedDataForSale.md
@@ -87,3 +87,7 @@ import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
 See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+
+<script setup>
+import RequiredBadge from '@/components/RequiredBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorSharing/subscription/removeProtectedDataFromSubscription.md b/src/references/dataProtector/dataProtectorSharing/subscription/removeProtectedDataFromSubscription.md
index a093cdb0..035f5f64 100644
--- a/src/references/dataProtector/dataProtectorSharing/subscription/removeProtectedDataFromSubscription.md
+++ b/src/references/dataProtector/dataProtectorSharing/subscription/removeProtectedDataFromSubscription.md
@@ -75,3 +75,7 @@ import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
 See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+
+<script setup>
+import RequiredBadge from '@/components/RequiredBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorSharing/subscription/setProtectedDataToSubscription.md b/src/references/dataProtector/dataProtectorSharing/subscription/setProtectedDataToSubscription.md
index 34673ef0..2576461a 100644
--- a/src/references/dataProtector/dataProtectorSharing/subscription/setProtectedDataToSubscription.md
+++ b/src/references/dataProtector/dataProtectorSharing/subscription/setProtectedDataToSubscription.md
@@ -64,3 +64,7 @@ import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
 See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+
+<script setup>
+import RequiredBadge from '@/components/RequiredBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorSharing/subscription/setSubscriptionParams.md b/src/references/dataProtector/dataProtectorSharing/subscription/setSubscriptionParams.md
index 0d360eda..a414c15f 100644
--- a/src/references/dataProtector/dataProtectorSharing/subscription/setSubscriptionParams.md
+++ b/src/references/dataProtector/dataProtectorSharing/subscription/setSubscriptionParams.md
@@ -112,3 +112,7 @@ import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
 See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+
+<script setup>
+import RequiredBadge from '@/components/RequiredBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorSharing/subscription/subscribeToCollection.md b/src/references/dataProtector/dataProtectorSharing/subscription/subscribeToCollection.md
index 2ea2eac2..624bf2a5 100644
--- a/src/references/dataProtector/dataProtectorSharing/subscription/subscribeToCollection.md
+++ b/src/references/dataProtector/dataProtectorSharing/subscription/subscribeToCollection.md
@@ -133,3 +133,7 @@ import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
 See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+
+<script setup>
+import RequiredBadge from '@/components/RequiredBadge.vue'
+</script>
diff --git a/src/references/web3mail/methods/fetchMyContacts.md b/src/references/web3mail/methods/fetchMyContacts.md
index 5b90ff02..2df575e3 100644
--- a/src/references/web3mail/methods/fetchMyContacts.md
+++ b/src/references/web3mail/methods/fetchMyContacts.md
@@ -65,3 +65,7 @@ import { type Contact } from '@iexec/web3mail';
 ```
 
 [`Contact[]`](/references/dataProtector/types#contact)
+
+<script setup>
+import OptionalBadge from '@/components/OptionalBadge.vue'
+</script>
diff --git a/src/references/web3mail/methods/fetchUserContacts.md b/src/references/web3mail/methods/fetchUserContacts.md
index f030a46f..e128c857 100644
--- a/src/references/web3mail/methods/fetchUserContacts.md
+++ b/src/references/web3mail/methods/fetchUserContacts.md
@@ -85,3 +85,7 @@ import { type Contact } from '@iexec/web3mail';
 ```
 
 [`Contract[]`](/references/dataProtector/types#contact)
+
+<script setup>
+import RequiredBadge from '@/components/RequiredBadge.vue'
+</script>
diff --git a/src/references/web3mail/methods/sendEmail.md b/src/references/web3mail/methods/sendEmail.md
index 02cce046..fc9d7e0d 100644
--- a/src/references/web3mail/methods/sendEmail.md
+++ b/src/references/web3mail/methods/sendEmail.md
@@ -390,3 +390,8 @@ For any other errors, you'll get a `WorkflowError` error in the form of:
   errorCause: <Original error>
 }
 ```
+
+<script setup>
+import RequiredBadge from '@/components/RequiredBadge.vue'
+import OptionalBadge from '@/components/OptionalBadge.vue'
+</script>
diff --git a/src/references/web3telegram/methods/fetchMyContacts.md b/src/references/web3telegram/methods/fetchMyContacts.md
index 9cfaec5f..ae976356 100644
--- a/src/references/web3telegram/methods/fetchMyContacts.md
+++ b/src/references/web3telegram/methods/fetchMyContacts.md
@@ -65,3 +65,7 @@ import { type Contact } from '@iexec/web3telegram';
 ```
 
 [`Contact[]`](/references/dataProtector/types#contact)
+
+<script setup>
+import OptionalBadge from '@/components/OptionalBadge.vue'
+</script>
diff --git a/src/references/web3telegram/methods/fetchUserContacts.md b/src/references/web3telegram/methods/fetchUserContacts.md
index 8cf0011d..815514a3 100644
--- a/src/references/web3telegram/methods/fetchUserContacts.md
+++ b/src/references/web3telegram/methods/fetchUserContacts.md
@@ -85,3 +85,7 @@ import { type Contact } from '@iexec/web3telegram';
 ```
 
 [`Contract[]`](/references/dataProtector/types#contact)
+
+<script setup>
+import OptionalBadge from '@/components/OptionalBadge.vue'
+</script>
diff --git a/src/references/web3telegram/methods/sendTelegram.md b/src/references/web3telegram/methods/sendTelegram.md
index 88f43340..90a0c6bf 100644
--- a/src/references/web3telegram/methods/sendTelegram.md
+++ b/src/references/web3telegram/methods/sendTelegram.md
@@ -293,3 +293,9 @@ import { type SendTelegramResponse } from '@iexec/web3telegram';
 This uniquely identifies the telegram task on the iExec side chain. You can view
 the status of the `sendTelegram` method by monitoring the task on the
 [iExec Explorer](https://explorer.iex.ec/bellecour).
+
+```
+
+<script setup>
+import OptionalBadge from '@/components/OptionalBadge.vue'
+</script>

From f13ac50009d3fc3ba2840c6261459e376d95da73 Mon Sep 17 00:00:00 2001
From: Le-Caignec <robinlecaignec@yahoo.fr>
Date: Thu, 14 Aug 2025 17:27:12 +0200
Subject: [PATCH 08/27] docs: add ChainNotSupportedBadge to payment guides and
 methods

Updated the payment guides for Web3Mail, Web3Telegram, and execution methods to include the ChainNotSupportedBadge for the useVoucher section. Enhanced clarity by importing the badge component in relevant script sections.
---
 src/guides/use-iapp/how-to-pay-executions.md                | 6 +++++-
 src/guides/use-iapp/how-to-pay/how-to-pay-for-web3mail.md   | 3 ++-
 .../use-iapp/how-to-pay/how-to-pay-for-web3telegram.md      | 3 ++-
 .../dataProtectorCore/getResultFromCompletedTask.md         | 1 +
 src/references/web3mail/methods/sendEmail.md                | 3 ++-
 src/references/web3telegram/methods/sendTelegram.md         | 5 ++---
 6 files changed, 14 insertions(+), 7 deletions(-)

diff --git a/src/guides/use-iapp/how-to-pay-executions.md b/src/guides/use-iapp/how-to-pay-executions.md
index db41b230..86f7a76b 100644
--- a/src/guides/use-iapp/how-to-pay-executions.md
+++ b/src/guides/use-iapp/how-to-pay-executions.md
@@ -86,7 +86,7 @@ iexec account show
 iexec account deposit 100
 ```
 
-## Method 2: Paying with Vouchers
+## Method 2: Paying with Vouchers <ChainNotSupportedBadge />
 
 Vouchers are pre-funded payment instruments that simplify the payment process
 and can be shared with others.
@@ -493,3 +493,7 @@ Now that you understand payment methods:
 - Learn about [Adding Inputs to Execution](./add-inputs-to-execution.md)
 - Explore [Using iApps with Protected Data](./use-iapp-with-protected-data.md)
 - Review the pricing information above for detailed cost analysis
+
+<script setup>
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
+</script>
diff --git a/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3mail.md b/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3mail.md
index f74b1ee4..dea0db5f 100644
--- a/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3mail.md
+++ b/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3mail.md
@@ -16,7 +16,7 @@ messages, ensuring secure and decentralized email exchanges.
 This guide explains how to pay for Web3Mail's computing power using **vouchers**
 and **xRLC**, detailing the steps for each method.
 
-## Using Vouchers for Web3Mail
+## Using Vouchers for Web3Mail <ChainNotSupportedBadge />
 
 ### Step 1: Obtain a Voucher
 
@@ -162,4 +162,5 @@ iexec.account.withdraw(RLC_amount);
 <script setup>
 // Assets
 import builderDashboardImage from '@/assets/tooling-&-explorers/builder-dashboard/builder-dashboard.png';
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
 </script>
diff --git a/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3telegram.md b/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3telegram.md
index a22702db..2227bb68 100644
--- a/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3telegram.md
+++ b/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3telegram.md
@@ -17,7 +17,7 @@ send messages, ensuring secure and decentralized email exchanges.
 This guide explains how to pay for Web3Telegram's computing power using
 **vouchers** and **xRLC**, detailing the steps for each method.
 
-## Using Vouchers for Web3Telegram
+## Using Vouchers for Web3Telegram <ChainNotSupportedBadge />
 
 ### Step 1: Obtain a Voucher
 
@@ -175,4 +175,5 @@ iexec.account.withdraw(RLC_amount);
 <script setup>
 // Assets
 import builderDashboardImage from '@/assets/tooling-&-explorers/builder-dashboard/builder-dashboard.png';
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
 </script>
diff --git a/src/references/dataProtector/dataProtectorCore/getResultFromCompletedTask.md b/src/references/dataProtector/dataProtectorCore/getResultFromCompletedTask.md
index 3ee3eacc..6d1d869b 100644
--- a/src/references/dataProtector/dataProtectorCore/getResultFromCompletedTask.md
+++ b/src/references/dataProtector/dataProtectorCore/getResultFromCompletedTask.md
@@ -141,3 +141,4 @@ The actual content of the protected file.
 import RequiredBadge from '@/components/RequiredBadge.vue'
 import OptionalBadge from '@/components/OptionalBadge.vue'
 </script>
+```
diff --git a/src/references/web3mail/methods/sendEmail.md b/src/references/web3mail/methods/sendEmail.md
index fc9d7e0d..cb4e3083 100644
--- a/src/references/web3mail/methods/sendEmail.md
+++ b/src/references/web3mail/methods/sendEmail.md
@@ -112,7 +112,7 @@ const sendEmail = await web3mail.sendEmail({
 });
 ```
 
-### useVoucher <OptionalBadge />
+### useVoucher <ChainNotSupportedBadge /><OptionalBadge />
 
 **Type:** `boolean`  
 **Default:** `false`
@@ -394,4 +394,5 @@ For any other errors, you'll get a `WorkflowError` error in the form of:
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
 import OptionalBadge from '@/components/OptionalBadge.vue'
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
 </script>
diff --git a/src/references/web3telegram/methods/sendTelegram.md b/src/references/web3telegram/methods/sendTelegram.md
index 90a0c6bf..3801dacc 100644
--- a/src/references/web3telegram/methods/sendTelegram.md
+++ b/src/references/web3telegram/methods/sendTelegram.md
@@ -117,7 +117,7 @@ const sendTelegram = await web3telegram.sendTelegram({
 });
 ```
 
-### useVoucher <OptionalBadge />
+### useVoucher <ChainNotSupportedBadge /> <OptionalBadge />
 
 **Type:** `boolean`  
 **Default:** `false`
@@ -294,8 +294,7 @@ This uniquely identifies the telegram task on the iExec side chain. You can view
 the status of the `sendTelegram` method by monitoring the task on the
 [iExec Explorer](https://explorer.iex.ec/bellecour).
 
-```
-
 <script setup>
 import OptionalBadge from '@/components/OptionalBadge.vue'
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
 </script>

From fb5b1c3f8b2578d799cb44f842b0362d73f3ceb9 Mon Sep 17 00:00:00 2001
From: Le-Caignec <robinlecaignec@yahoo.fr>
Date: Thu, 14 Aug 2025 17:34:11 +0200
Subject: [PATCH 09/27] refactor: update ChainNotSupportedBadge styling and
 text

Changed the badge type from warning to tip and updated the text for improved clarity. Adjusted the color scheme to enhance visibility and align with design standards.
---
 src/components/ChainNotSupportedBadge.vue | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/src/components/ChainNotSupportedBadge.vue b/src/components/ChainNotSupportedBadge.vue
index bae437a2..d7f88c0b 100644
--- a/src/components/ChainNotSupportedBadge.vue
+++ b/src/components/ChainNotSupportedBadge.vue
@@ -17,11 +17,11 @@ const shouldShow = computed(() => isArbitrumSelected.value);
 <template>
   <VPBadge
     v-if="shouldShow"
-    type="warning"
-    text="Not Supported for this Chain"
+    type="tip"
+    text="Chain Not Supported"
     style="
-      color: var(--vp-c-orange-1);
-      background-color: hsla(15, 100%, 40%, 8%);
+      color: var(--vp-c-red-1);
+      background-color: hsla(350, 89%, 60%, 8%);
       margin-top: 1px;
       margin-right: 4px;
     "

From 51bb5f661d32db1bb5c2de67cac3e1b7779fd095 Mon Sep 17 00:00:00 2001
From: Le-Caignec <robinlecaignec@yahoo.fr>
Date: Thu, 14 Aug 2025 18:49:20 +0200
Subject: [PATCH 10/27] docs: integrate ChainNotSupportedBadge across data
 protector documentation

Added ChainNotSupportedBadge to various sections of the data protector documentation, including sharing, renting, and subscription methods, to indicate unsupported chains. Removed the obsolete dps-smart-contract documentation and updated the README with a new development workflow section. Enhanced clarity by importing the badge component in relevant script sections.
---
 .vitepress/sidebar.ts                         |   4 -
 README.md                                     |  10 +-
 .../advanced/advanced-configuration.md        |   6 +-
 .../dataProtector/advanced/apps-whitelist.md  |   6 +-
 .../addAppToAddOnlyAppWhitelist.md            |   3 +-
 .../createAddOnlyAppWhitelist.md              |   6 +-
 .../getUserAddOnlyAppWhitelist.md             |   3 +-
 .../advanced/dps-smart-contract.md            | 123 ------------------
 .../dataProtectorCore/processProtectedData.md |   2 +-
 .../dataProtector/dataProtectorSharing.md     |   6 +-
 .../dataProtectorSharing/collection.md        |   6 +-
 .../collection/addToCollection.md             |   3 +-
 .../collection/createCollection.md            |   6 +-
 .../collection/removeCollection.md            |   3 +-
 .../removeProtectedDataFromCollection.md      |   3 +-
 .../consume/consumeProtectedData.md           |  17 +--
 .../read/getCollectionOwners.md               |   3 +-
 .../read/getCollectionSubscriptions.md        |   3 +-
 .../read/getCollectionsByOwner.md             |   3 +-
 .../read/getProtectedDataInCollections.md     |   3 +-
 .../read/getProtectedDataPricingParams.md     |   3 +-
 .../dataProtectorSharing/read/getRentals.md   |   3 +-
 .../dataProtectorSharing/renting.md           |   6 +-
 .../renting/removeProtectedDataFromRenting.md |   3 +-
 .../renting/rentProtectedData.md              |   3 +-
 .../renting/setProtectedDataRentingParams.md  |   6 +-
 .../renting/setProtectedDataToRenting.md      |   3 +-
 .../dataProtectorSharing/selling.md           |   6 +-
 .../selling/buyProtectedData.md               |   3 +-
 .../selling/removeProtectedDataForSale.md     |   3 +-
 .../selling/setProtectedDataForSale.md        |   3 +-
 .../dataProtectorSharing/subscription.md      |   6 +-
 .../removeProtectedDataFromSubscription.md    |   3 +-
 .../setProtectedDataToSubscription.md         |   3 +-
 .../subscription/setSubscriptionParams.md     |   3 +-
 .../subscription/subscribeToCollection.md     |   3 +-
 36 files changed, 105 insertions(+), 174 deletions(-)
 delete mode 100644 src/references/dataProtector/advanced/dps-smart-contract.md

diff --git a/.vitepress/sidebar.ts b/.vitepress/sidebar.ts
index e77aac5f..3cc495dc 100644
--- a/.vitepress/sidebar.ts
+++ b/.vitepress/sidebar.ts
@@ -429,10 +429,6 @@ export function getSidebar() {
                 text: 'Advanced Configuration',
                 link: '/references/dataProtector/advanced/advanced-configuration',
               },
-              {
-                text: 'Sharing smart contract',
-                link: '/references/dataProtector/advanced/dps-smart-contract',
-              },
               {
                 text: 'Apps whitelist',
                 link: '/references/dataProtector/advanced/apps-whitelist',
diff --git a/README.md b/README.md
index d189c831..7dd51cab 100644
--- a/README.md
+++ b/README.md
@@ -168,19 +168,15 @@ for input parameters:
 ## TODO
 
 - Add an audit section for smart contracts
-- Add Arbitrum support
 - On arbitrum hide : DataProtector Sharing ??
 - Adapt hardcoded address to feat with new contracts deployed on arbitrum
 - Add link to the new explorer feature Asset_Types in the guide =>
   `handle-schemas-dataset-types`
 - Add link to remix for deploying whitelist
-- complete `use-iapp` section
-- Maybe split input and output in two diff sub section in build your iapp guide
 - SGX vs TDX need review
 - Explorer l'intégration de codeSpace
-- complete `Protocol`section
-- Add a Development workflow
-- Update context7 when doc will be deployed
+- Add a Development workflow pahe (1 - ProtectData, 2- ...)
+- Update context7 when doc will be deployed (Martin)
 - Check theGraph Images with design Team
 - Update the Dune Dashboard to the final version
 - Add new section in `iexec-explorer.md` file to talk about: available chain on
@@ -189,7 +185,7 @@ for input parameters:
 - Check how to pay guide to update with the launch on Arbitrum (RLC vs xRLC)
 - framework AI supporté TDX vs SGX
 - check glossary
-- migrate github SDK doc here
+- migrate github iexec SDK doc here
 - migrate pay-per-task page into a guide
 - check pages (introduction & getting-started) for use-iapp guide
 - explain TDX vs SGX
diff --git a/src/references/dataProtector/advanced/advanced-configuration.md b/src/references/dataProtector/advanced/advanced-configuration.md
index bbb23d20..d5b427b8 100644
--- a/src/references/dataProtector/advanced/advanced-configuration.md
+++ b/src/references/dataProtector/advanced/advanced-configuration.md
@@ -22,7 +22,7 @@ section.
 import { type DataProtectorConfigOptions } from '@iexec/dataprotector';
 ```
 
-### dataprotectorContractAddress
+### dataprotectorContractAddress <ChainNotSupportedBadge />
 
 `AddressOrENS`
 
@@ -164,3 +164,7 @@ const dataProtector = new IExecDataProtector(web3Provider, {
 discontinuity.
 
 :::
+
+<script setup>
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
+</script>
diff --git a/src/references/dataProtector/advanced/apps-whitelist.md b/src/references/dataProtector/advanced/apps-whitelist.md
index b2a14726..e88ed232 100644
--- a/src/references/dataProtector/advanced/apps-whitelist.md
+++ b/src/references/dataProtector/advanced/apps-whitelist.md
@@ -6,7 +6,7 @@ description:
   Environment (TEE) dApp and whitelist usage for secure data delivery.
 ---
 
-# Apps Whitelist
+# Apps Whitelist <ChainNotSupportedBadge />
 
 In order to consume a protected data, an iExec TEE dApp needs to be provided.
 
@@ -78,3 +78,7 @@ See it in
 
 See it in
 [https://blockscout-bellecour.iex.ec/](https://blockscout-bellecour.iex.ec/address/0x1cb7D4F3FFa203F211e57357D759321C6CE49921)
+
+<script setup>
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
+</script>
diff --git a/src/references/dataProtector/advanced/apps-whitelist/addAppToAddOnlyAppWhitelist.md b/src/references/dataProtector/advanced/apps-whitelist/addAppToAddOnlyAppWhitelist.md
index f6e93993..433288f3 100644
--- a/src/references/dataProtector/advanced/apps-whitelist/addAppToAddOnlyAppWhitelist.md
+++ b/src/references/dataProtector/advanced/apps-whitelist/addAppToAddOnlyAppWhitelist.md
@@ -5,7 +5,7 @@ description:
   data access control.
 ---
 
-# addAppToAddOnlyAppWhitelist
+# addAppToAddOnlyAppWhitelist <ChainNotSupportedBadge />
 
 Method to add an app (iExec TEE dApp) into the `AddOnlyAppWhitelist`.
 
@@ -99,4 +99,5 @@ See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
 </script>
diff --git a/src/references/dataProtector/advanced/apps-whitelist/createAddOnlyAppWhitelist.md b/src/references/dataProtector/advanced/apps-whitelist/createAddOnlyAppWhitelist.md
index 567f287a..935ee810 100644
--- a/src/references/dataProtector/advanced/apps-whitelist/createAddOnlyAppWhitelist.md
+++ b/src/references/dataProtector/advanced/apps-whitelist/createAddOnlyAppWhitelist.md
@@ -5,7 +5,7 @@ description:
   becomes the owner by default, with transferable ownership as an ERC721.
 ---
 
-# createAddOnlyAppWhitelist
+# createAddOnlyAppWhitelist <ChainNotSupportedBadge />
 
 Method to create an `AddOnlyAppWhitelist`. By default, the owner will be the
 caller of the `createAddOnlyAppWhitelist` method, but as the
@@ -31,3 +31,7 @@ const isAddedToAddAppToAddOnlyAppWhitelist =
 ```ts twoslash
 import { type CreateAppWhitelistResponse } from '@iexec/dataprotector';
 ```
+
+<script setup>
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
+</script>
diff --git a/src/references/dataProtector/advanced/apps-whitelist/getUserAddOnlyAppWhitelist.md b/src/references/dataProtector/advanced/apps-whitelist/getUserAddOnlyAppWhitelist.md
index fe34dafb..5d5842b3 100644
--- a/src/references/dataProtector/advanced/apps-whitelist/getUserAddOnlyAppWhitelist.md
+++ b/src/references/dataProtector/advanced/apps-whitelist/getUserAddOnlyAppWhitelist.md
@@ -5,7 +5,7 @@ description:
   app access control management.
 ---
 
-# getUserAddOnlyAppWhitelist
+# getUserAddOnlyAppWhitelist <ChainNotSupportedBadge />
 
 Method to get `AddOnlyAppWhitelist`, you can filter by user ethereum address.
 
@@ -62,4 +62,5 @@ import { type AddOnlyAppWhitelist } from '@iexec/dataprotector';
 
 <script setup>
 import OptionalBadge from '@/components/OptionalBadge.vue'
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
 </script>
diff --git a/src/references/dataProtector/advanced/dps-smart-contract.md b/src/references/dataProtector/advanced/dps-smart-contract.md
deleted file mode 100644
index 08f2e408..00000000
--- a/src/references/dataProtector/advanced/dps-smart-contract.md
+++ /dev/null
@@ -1,123 +0,0 @@
----
-title: DataProtector Sharing Smart Contracts
-description:
-  Learn about the DataProtector Sharing smart contract for managing and sharing
-  protected data via collections, subscriptions, rentals, and sales. Explore the
-  Solidity code and features in iExec's implementation.
----
-
-# DataProtector Sharing Smart Contracts
-
-A specific smart contract has been developed to support all of the "Sharing"
-module features.
-
-It mainly serves as **a storage for collections**, their associated protected
-data, and their owners.
-
-## Code
-
-You can find the Solidity code
-[here](https://github.com/iExecBlockchainComputing/dataprotector-sdk/tree/main/packages/sharing-smart-contract)
-
-## DataProtectorSharing
-
-This is a contract that provides a mechanism for managing and sharing protected
-data through collections, subscriptions, rentals, and sales. This contract
-extends several functionalities from OpenZeppelin libraries and incorporates
-access control, token handling, and order management.
-
-::: tip FUNCTIONS
-
----
-
-#### General
-
-- `consumeProtectedData(protectedData, workerpoolOrder, app)`
-- `getProtectedDataRenter(protectedData, renterAddress)`
-- `getCollectionSubscriber(collectionTokenId, subscriberAddress)`
-- `createCollection(to)`
-- `addProtectedDataToCollection(collectionTokenId, protectedData, appWhitelist)`
-- `removeProtectedDataFromCollection(protectedData)`
-
-#### Subscription
-
-- `subscribeToCollection(collectionTokenId, subscriptionParams)`
-- `setProtectedDataToSubscription(protectedData)`
-- `removeProtectedDataFromSubscription(protectedData)`
-- `setSubscriptionParams(collectionTokenId, subscriptionParams)`
-
-#### Renting
-
-- `rentProtectedData(protectedData, rentingParams)`
-- `setProtectedDataToRenting(protectedData, rentingParams)`
-- `removeProtectedDataFromRenting(protectedData)`
-
-#### Sale
-
-- `buyProtectedData(protectedData, to, price)`
-- `setProtectedDataForSale(protectedData, price)`
-- `removeProtectedDataForSale(protectedData)`
-
-:::
-
-:::tip EVENTS
-
----
-
-#### General
-
-- `OwnershipTransferred(previousOwner, newOwner)`
-- `ProtectedDataTransfer(protectedData, fromCollection, toCollection, appWhitelist)`
-
-#### Subscription
-
-- `NewSubscription(collectionTokenId, subscriber, endDate)`
-- `ProtectedDataAddedForSubscription(collectionTokenId, protectedData)`
-- `ProtectedDataRemovedFromSubscription(collectionTokenId, protectedData)`
-- `NewSubscriptionParams(collectionTokenId, subscriptionParams)`
-
-#### Renting
-
-- `NewRental(collectionTokenId, protectedData, renter, endDate)`
-- `ProtectedDataAddedForRenting(collectionTokenId, protectedData, rentingParams)`
-- `ProtectedDataRemovedFromRenting(collectionTokenId, protectedData)`
-
-#### Sale
-
-- `ProtectedDataSold(collectionTokenId, newOwner, protectedData)`
-- `ProtectedDataAddedForSale(collectionTokenId, protectedData, price)`
-- `ProtectedDataRemovedFromSale(collectionTokenId, protectedData)`
-- `ProtectedDataConsumed(dealid, protectedData, mode)`
-
-:::
-
-:::tip ERRORS
-
----
-
-#### General
-
-- `OnlyPocoCallerAuthorized(account)`
-- `EmptyCallData()`
-
-#### Subscription
-
-- `InvalidSubscriptionParams(collectionTokenId, subscriptionParams)`
-- `OnGoingCollectionSubscriptions(collectionTokenId)`
-- `ProtectedDataAvailableInSubscription(collectionTokenId, protectedData)`
-
-#### Renting
-
-- `ProtectedDataCurrentlyBeingRented(protectedData)`
-- `ProtectedDataNotAvailableForRenting(protectedData)`
-- `DurationInvalid(duration)`
-- `ProtectedDataAvailableForRenting(collectionTokenId, protectedData)`
-
-#### Sale
-
-- `ProtectedDataNotForSale(protectedData)`
-- `InvalidPriceForPurchase(protectedData, price)`
-- `WorkerpoolOrderNotFree(workerpoolOrder)`
-- `NoValidRentalOrSubscription(collectionTokenId, protectedData)`
-
-:::
diff --git a/src/references/dataProtector/dataProtectorCore/processProtectedData.md b/src/references/dataProtector/dataProtectorCore/processProtectedData.md
index 6289ba4d..c27f5e74 100644
--- a/src/references/dataProtector/dataProtectorCore/processProtectedData.md
+++ b/src/references/dataProtector/dataProtectorCore/processProtectedData.md
@@ -160,7 +160,7 @@ sufficient funds for this transfer to proceed.
 
 :::
 
-### voucherOwner <OptionalBadge />
+### voucherOwner <ChainNotSupportedBadge /> <OptionalBadge />
 
 **Type:** `Address`
 
diff --git a/src/references/dataProtector/dataProtectorSharing.md b/src/references/dataProtector/dataProtectorSharing.md
index 086fd6a6..293a92fa 100644
--- a/src/references/dataProtector/dataProtectorSharing.md
+++ b/src/references/dataProtector/dataProtectorSharing.md
@@ -6,7 +6,7 @@ description:
   maintaining control and privacy.
 ---
 
-# DataProtector Sharing
+# DataProtector Sharing <ChainNotSupportedBadge />
 
 The DataProtector Sharing module includes a set of methods for distributing and
 monetizing your protected data. These work seamlessly in your own applications
@@ -63,3 +63,7 @@ additional activity from the data owner. This has several key benefits
   distribution, only the consumer of the data signs their transaction
 - The data owner doesn't manage access, the Data Sharing smart contract
   automatically enforces the distribution and monetization choices
+
+<script setup>
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorSharing/collection.md b/src/references/dataProtector/dataProtectorSharing/collection.md
index 55921734..d875283a 100644
--- a/src/references/dataProtector/dataProtectorSharing/collection.md
+++ b/src/references/dataProtector/dataProtectorSharing/collection.md
@@ -6,7 +6,7 @@ description:
   or selling to control how your data is shared and monetized.
 ---
 
-# Data Sharing - Collection Methods
+# Data Sharing - Collection Methods <ChainNotSupportedBadge />
 
 A collection is a way to group protected data for sharing by the Data Sharing
 module. The Data Sharing smart contract operates on data contained within a
@@ -68,3 +68,7 @@ for any protected data in the collection.
 
 The collection owner may list any of their protected data for sale. This is
 especially useful for dealers of digital assets like NFTs.
+
+<script setup>
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorSharing/collection/addToCollection.md b/src/references/dataProtector/dataProtectorSharing/collection/addToCollection.md
index 72249928..53a593ff 100644
--- a/src/references/dataProtector/dataProtectorSharing/collection/addToCollection.md
+++ b/src/references/dataProtector/dataProtectorSharing/collection/addToCollection.md
@@ -6,7 +6,7 @@ description:
   the specified collection.
 ---
 
-# addToCollection
+# addToCollection <ChainNotSupportedBadge />
 
 Method to transfer one of your protected data to a collection of yours in the
 Data Sharing smart contract.
@@ -168,4 +168,5 @@ See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
 import OptionalBadge from '@/components/OptionalBadge.vue'
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
 </script>
diff --git a/src/references/dataProtector/dataProtectorSharing/collection/createCollection.md b/src/references/dataProtector/dataProtectorSharing/collection/createCollection.md
index 9f48e64e..b880deaf 100644
--- a/src/references/dataProtector/dataProtectorSharing/collection/createCollection.md
+++ b/src/references/dataProtector/dataProtectorSharing/collection/createCollection.md
@@ -6,7 +6,7 @@ description:
   DataProtector Sharing.
 ---
 
-# createCollection
+# createCollection <ChainNotSupportedBadge />
 
 Method to create a new collection in the Data Sharing smart contract.
 
@@ -34,3 +34,7 @@ const createCollectionResult = await dataProtectorSharing.createCollection();
 ```ts twoslash
 import { type CreateCollectionResponse } from '@iexec/dataprotector';
 ```
+
+<script setup>
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorSharing/collection/removeCollection.md b/src/references/dataProtector/dataProtectorSharing/collection/removeCollection.md
index b34454ab..bccc0738 100644
--- a/src/references/dataProtector/dataProtectorSharing/collection/removeCollection.md
+++ b/src/references/dataProtector/dataProtectorSharing/collection/removeCollection.md
@@ -6,7 +6,7 @@ description:
   the collection.
 ---
 
-# removeCollection
+# removeCollection <ChainNotSupportedBadge />
 
 Method to remove one of your collections in the Data Sharing smart contract.
 
@@ -71,4 +71,5 @@ See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
 </script>
diff --git a/src/references/dataProtector/dataProtectorSharing/collection/removeProtectedDataFromCollection.md b/src/references/dataProtector/dataProtectorSharing/collection/removeProtectedDataFromCollection.md
index f6f24e95..087a9a76 100644
--- a/src/references/dataProtector/dataProtectorSharing/collection/removeProtectedDataFromCollection.md
+++ b/src/references/dataProtector/dataProtectorSharing/collection/removeProtectedDataFromCollection.md
@@ -6,7 +6,7 @@ description:
   the owner.
 ---
 
-# removeProtectedDataFromCollection
+# removeProtectedDataFromCollection <ChainNotSupportedBadge />
 
 Method to remove one of your protected data from a collection of yours in the
 Data Sharing smart contract.
@@ -77,4 +77,5 @@ See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
 </script>
diff --git a/src/references/dataProtector/dataProtectorSharing/consume/consumeProtectedData.md b/src/references/dataProtector/dataProtectorSharing/consume/consumeProtectedData.md
index aefeedce..361bdc76 100644
--- a/src/references/dataProtector/dataProtectorSharing/consume/consumeProtectedData.md
+++ b/src/references/dataProtector/dataProtectorSharing/consume/consumeProtectedData.md
@@ -6,13 +6,7 @@ description:
   Service, and securely retrieving encrypted data from IPFS.
 ---
 
-<script setup>
-import { Icon } from '@iconify/vue';
-import RequiredBadge from '@/components/RequiredBadge.vue'
-import OptionalBadge from '@/components/OptionalBadge.vue'
-</script>
-
-# consumeProtectedData
+# consumeProtectedData <ChainNotSupportedBadge />
 
 Method to consume a protected data, ie. visualize it or download it.
 
@@ -83,7 +77,7 @@ const consumeProtectedDataResult =
   });
 ```
 
-### app <RequiredBadge /> {#app-param}
+### app <RequiredBadge />
 
 **Type:** `AddressOrENS`
 
@@ -341,3 +335,10 @@ Identifies the specific task associated with the deal.
 `ArrayBuffer`
 
 The actual content of the protected file.
+
+<script setup>
+import { Icon } from '@iconify/vue';
+import RequiredBadge from '@/components/RequiredBadge.vue'
+import OptionalBadge from '@/components/OptionalBadge.vue'
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorSharing/read/getCollectionOwners.md b/src/references/dataProtector/dataProtectorSharing/read/getCollectionOwners.md
index 9bf0320c..460dd499 100644
--- a/src/references/dataProtector/dataProtectorSharing/read/getCollectionOwners.md
+++ b/src/references/dataProtector/dataProtectorSharing/read/getCollectionOwners.md
@@ -5,7 +5,7 @@ description:
   in descending order.
 ---
 
-# getCollectionOwners
+# getCollectionOwners <ChainNotSupportedBadge />
 
 Method to get all collection owners.
 
@@ -71,4 +71,5 @@ collections.
 
 <script setup>
 import OptionalBadge from '@/components/OptionalBadge.vue'
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
 </script>
diff --git a/src/references/dataProtector/dataProtectorSharing/read/getCollectionSubscriptions.md b/src/references/dataProtector/dataProtectorSharing/read/getCollectionSubscriptions.md
index ce3e0c97..64a724fc 100644
--- a/src/references/dataProtector/dataProtectorSharing/read/getCollectionSubscriptions.md
+++ b/src/references/dataProtector/dataProtectorSharing/read/getCollectionSubscriptions.md
@@ -5,7 +5,7 @@ description:
   detailed information about subscription activity based on collection ID.
 ---
 
-# getCollectionSubscriptions
+# getCollectionSubscriptions <ChainNotSupportedBadge />
 
 Method to get all subscriptions for:
 
@@ -107,4 +107,5 @@ Type ↗️</a>
 
 <script setup>
 import OptionalBadge from '@/components/OptionalBadge.vue'
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
 </script>
diff --git a/src/references/dataProtector/dataProtectorSharing/read/getCollectionsByOwner.md b/src/references/dataProtector/dataProtectorSharing/read/getCollectionsByOwner.md
index e8ae57ca..a3de9d0c 100644
--- a/src/references/dataProtector/dataProtectorSharing/read/getCollectionsByOwner.md
+++ b/src/references/dataProtector/dataProtectorSharing/read/getCollectionsByOwner.md
@@ -5,7 +5,7 @@ description:
   pagination options.
 ---
 
-# getCollectionsByOwner
+# getCollectionsByOwner <ChainNotSupportedBadge />
 
 Method to get all collections for a specific user.
 
@@ -91,4 +91,5 @@ Type ↗️</a>
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
 import OptionalBadge from '@/components/OptionalBadge.vue'
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
 </script>
diff --git a/src/references/dataProtector/dataProtectorSharing/read/getProtectedDataInCollections.md b/src/references/dataProtector/dataProtectorSharing/read/getProtectedDataInCollections.md
index 503afa0d..9df3146d 100644
--- a/src/references/dataProtector/dataProtectorSharing/read/getProtectedDataInCollections.md
+++ b/src/references/dataProtector/dataProtectorSharing/read/getProtectedDataInCollections.md
@@ -6,7 +6,7 @@ description:
   timestamp in descending order.
 ---
 
-# getProtectedDataInCollections
+# getProtectedDataInCollections <ChainNotSupportedBadge />
 
 Method to get protected data that are in collections.
 
@@ -230,4 +230,5 @@ Type ↗️</a>
 
 <script setup>
 import OptionalBadge from '@/components/OptionalBadge.vue'
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
 </script>
diff --git a/src/references/dataProtector/dataProtectorSharing/read/getProtectedDataPricingParams.md b/src/references/dataProtector/dataProtectorSharing/read/getProtectedDataPricingParams.md
index 7cafca5b..068acfd3 100644
--- a/src/references/dataProtector/dataProtectorSharing/read/getProtectedDataPricingParams.md
+++ b/src/references/dataProtector/dataProtectorSharing/read/getProtectedDataPricingParams.md
@@ -6,7 +6,7 @@ description:
   access.
 ---
 
-# getProtectedDataPricingParams
+# getProtectedDataPricingParams <ChainNotSupportedBadge />
 
 Method to get all distribution params for a protected data.
 
@@ -66,4 +66,5 @@ Type ↗️</a>
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
 </script>
diff --git a/src/references/dataProtector/dataProtectorSharing/read/getRentals.md b/src/references/dataProtector/dataProtectorSharing/read/getRentals.md
index 9d4377de..663e81cc 100644
--- a/src/references/dataProtector/dataProtectorSharing/read/getRentals.md
+++ b/src/references/dataProtector/dataProtectorSharing/read/getRentals.md
@@ -5,7 +5,7 @@ description:
   detailed rental information based on the protected data address.
 ---
 
-# getRentals
+# getRentals <ChainNotSupportedBadge />
 
 Method to get all rentals for:
 
@@ -104,4 +104,5 @@ Type ↗️</a>
 
 <script setup>
 import OptionalBadge from '@/components/OptionalBadge.vue'
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
 </script>
diff --git a/src/references/dataProtector/dataProtectorSharing/renting.md b/src/references/dataProtector/dataProtectorSharing/renting.md
index c6597a68..90495442 100644
--- a/src/references/dataProtector/dataProtectorSharing/renting.md
+++ b/src/references/dataProtector/dataProtectorSharing/renting.md
@@ -7,7 +7,7 @@ description:
   terms, even if modified by the owner.
 ---
 
-# Data Sharing - Renting
+# Data Sharing - Renting <ChainNotSupportedBadge />
 
 Rental agreements are one of the options given for distributing a collection
 owner's protected data. A rental agreement has the following attributes:
@@ -40,3 +40,7 @@ The collection owner has a few options once they list protected data for rent:
 Making either of these chances is effective immediately but only for future
 rentals. The Data Sharing smart contract enforces any ongoing rental agreements
 until the terms expire.
+
+<script setup>
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorSharing/renting/removeProtectedDataFromRenting.md b/src/references/dataProtector/dataProtectorSharing/renting/removeProtectedDataFromRenting.md
index 701e756d..a5230b6c 100644
--- a/src/references/dataProtector/dataProtectorSharing/renting/removeProtectedDataFromRenting.md
+++ b/src/references/dataProtector/dataProtectorSharing/renting/removeProtectedDataFromRenting.md
@@ -6,7 +6,7 @@ description:
   honored until their rental period ends.
 ---
 
-# removeProtectedDataFromRenting
+# removeProtectedDataFromRenting <ChainNotSupportedBadge />
 
 Method to remove a protected data from renting.
 
@@ -67,4 +67,5 @@ See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
 </script>
diff --git a/src/references/dataProtector/dataProtectorSharing/renting/rentProtectedData.md b/src/references/dataProtector/dataProtectorSharing/renting/rentProtectedData.md
index 8d023c85..7f8aa774 100644
--- a/src/references/dataProtector/dataProtectorSharing/renting/rentProtectedData.md
+++ b/src/references/dataProtector/dataProtectorSharing/renting/rentProtectedData.md
@@ -7,7 +7,7 @@ description:
   a transaction that would revert.
 ---
 
-# rentProtectedData
+# rentProtectedData <ChainNotSupportedBadge />
 
 Method to rent a protected data.
 
@@ -140,4 +140,5 @@ See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
 </script>
diff --git a/src/references/dataProtector/dataProtectorSharing/renting/setProtectedDataRentingParams.md b/src/references/dataProtector/dataProtectorSharing/renting/setProtectedDataRentingParams.md
index 52cffaad..bf0ff910 100644
--- a/src/references/dataProtector/dataProtectorSharing/renting/setProtectedDataRentingParams.md
+++ b/src/references/dataProtector/dataProtectorSharing/renting/setProtectedDataRentingParams.md
@@ -6,7 +6,7 @@ description:
   isn't listed for rent yet, it will be set for renting with the provided terms.
 ---
 
-# setProtectedDataRentingParams
+# setProtectedDataRentingParams <ChainNotSupportedBadge />
 
 Method to update a protected data renting params.
 
@@ -115,3 +115,7 @@ import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
 See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+
+<script setup>
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorSharing/renting/setProtectedDataToRenting.md b/src/references/dataProtector/dataProtectorSharing/renting/setProtectedDataToRenting.md
index 2f50f299..03049683 100644
--- a/src/references/dataProtector/dataProtectorSharing/renting/setProtectedDataToRenting.md
+++ b/src/references/dataProtector/dataProtectorSharing/renting/setProtectedDataToRenting.md
@@ -6,7 +6,7 @@ description:
   data is already listed for rent, it updates the terms accordingly.
 ---
 
-# setProtectedDataToRenting
+# setProtectedDataToRenting <ChainNotSupportedBadge />
 
 Method to allow a protected data to be rented.
 
@@ -119,4 +119,5 @@ See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
 </script>
diff --git a/src/references/dataProtector/dataProtectorSharing/selling.md b/src/references/dataProtector/dataProtectorSharing/selling.md
index 63f377ec..b9f4c257 100644
--- a/src/references/dataProtector/dataProtectorSharing/selling.md
+++ b/src/references/dataProtector/dataProtectorSharing/selling.md
@@ -5,7 +5,7 @@ description:
   through blockchain transactions, and manage data listing operations.
 ---
 
-# Data Sharing - Selling
+# Data Sharing - Selling <ChainNotSupportedBadge />
 
 The owner of protected data may list the data for sale. Upon completion of a
 sale, ownership of the protected data transfers to the buyer. This is a
@@ -13,3 +13,7 @@ permanent operation enforced by the blockchain and executed by the Data Sharing
 smart contract. The data owner may de-list the protected data at any point until
 a sale is completed. The new owner of the protected data has full rights to
 distribute the protected data through any channels they desire.
+
+<script setup>
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorSharing/selling/buyProtectedData.md b/src/references/dataProtector/dataProtectorSharing/selling/buyProtectedData.md
index c50c5435..b00fcdd9 100644
--- a/src/references/dataProtector/dataProtectorSharing/selling/buyProtectedData.md
+++ b/src/references/dataProtector/dataProtectorSharing/selling/buyProtectedData.md
@@ -6,7 +6,7 @@ description:
   the data as desired.
 ---
 
-# buyProtectedData
+# buyProtectedData <ChainNotSupportedBadge />
 
 Method to buy a protected data that is for sale.
 
@@ -166,4 +166,5 @@ See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
 import OptionalBadge from '@/components/OptionalBadge.vue'
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
 </script>
diff --git a/src/references/dataProtector/dataProtectorSharing/selling/removeProtectedDataForSale.md b/src/references/dataProtector/dataProtectorSharing/selling/removeProtectedDataForSale.md
index 568a45bd..41d1bf46 100644
--- a/src/references/dataProtector/dataProtectorSharing/selling/removeProtectedDataForSale.md
+++ b/src/references/dataProtector/dataProtectorSharing/selling/removeProtectedDataForSale.md
@@ -5,7 +5,7 @@ description:
   purchase transactions.
 ---
 
-# removeProtectedDataForSale
+# removeProtectedDataForSale <ChainNotSupportedBadge />
 
 Method to remove a protected data for sale.
 
@@ -63,4 +63,5 @@ See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
 </script>
diff --git a/src/references/dataProtector/dataProtectorSharing/selling/setProtectedDataForSale.md b/src/references/dataProtector/dataProtectorSharing/selling/setProtectedDataForSale.md
index 76d7cdde..d6cd8236 100644
--- a/src/references/dataProtector/dataProtectorSharing/selling/setProtectedDataForSale.md
+++ b/src/references/dataProtector/dataProtectorSharing/selling/setProtectedDataForSale.md
@@ -6,7 +6,7 @@ description:
   their own pricing or retain the data for personal use."
 ---
 
-# setProtectedDataForSale
+# setProtectedDataForSale <ChainNotSupportedBadge />
 
 Method to set a protected data for sale.
 
@@ -90,4 +90,5 @@ See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
 </script>
diff --git a/src/references/dataProtector/dataProtectorSharing/subscription.md b/src/references/dataProtector/dataProtectorSharing/subscription.md
index 206420ff..f2f2d913 100644
--- a/src/references/dataProtector/dataProtectorSharing/subscription.md
+++ b/src/references/dataProtector/dataProtectorSharing/subscription.md
@@ -6,7 +6,7 @@ description:
   modifying terms and protecting subscribers' access.
 ---
 
-# Data Sharing - Subscription
+# Data Sharing - Subscription <ChainNotSupportedBadge />
 
 Subscription agreements are one of the options for distributing a collection
 owner's protected data. Similar to the rental distribution terms, a subscription
@@ -58,3 +58,7 @@ The collection owner has a few options to manage their subscription bundles:
 Making any of these changes is effective immediately. For any existing
 subscribers, updates to the subscription terms take effect upon renewal of the
 subscription.
+
+<script setup>
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorSharing/subscription/removeProtectedDataFromSubscription.md b/src/references/dataProtector/dataProtectorSharing/subscription/removeProtectedDataFromSubscription.md
index 035f5f64..92105e53 100644
--- a/src/references/dataProtector/dataProtectorSharing/subscription/removeProtectedDataFromSubscription.md
+++ b/src/references/dataProtector/dataProtectorSharing/subscription/removeProtectedDataFromSubscription.md
@@ -5,7 +5,7 @@ description:
   data to current and future subscribers, removing it from subscription access.
 ---
 
-# removeProtectedDataFromSubscription
+# removeProtectedDataFromSubscription <ChainNotSupportedBadge />
 
 Method to remove a protected data from your subscription.
 
@@ -78,4 +78,5 @@ See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
 </script>
diff --git a/src/references/dataProtector/dataProtectorSharing/subscription/setProtectedDataToSubscription.md b/src/references/dataProtector/dataProtectorSharing/subscription/setProtectedDataToSubscription.md
index 2576461a..c4d905fe 100644
--- a/src/references/dataProtector/dataProtectorSharing/subscription/setProtectedDataToSubscription.md
+++ b/src/references/dataProtector/dataProtectorSharing/subscription/setProtectedDataToSubscription.md
@@ -6,7 +6,7 @@ description:
   access your data easily.
 ---
 
-# setProtectedDataToSubscription
+# setProtectedDataToSubscription <ChainNotSupportedBadge />
 
 Method to set a protected data as part of your subscription.
 
@@ -67,4 +67,5 @@ See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
 </script>
diff --git a/src/references/dataProtector/dataProtectorSharing/subscription/setSubscriptionParams.md b/src/references/dataProtector/dataProtectorSharing/subscription/setSubscriptionParams.md
index a414c15f..549e06ab 100644
--- a/src/references/dataProtector/dataProtectorSharing/subscription/setSubscriptionParams.md
+++ b/src/references/dataProtector/dataProtectorSharing/subscription/setSubscriptionParams.md
@@ -6,7 +6,7 @@ description:
   using the Data Sharing smart contract.
 ---
 
-# setSubscriptionParams
+# setSubscriptionParams <ChainNotSupportedBadge />
 
 Method to set subscription parameters for a given collection of yours.
 
@@ -115,4 +115,5 @@ See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
 </script>
diff --git a/src/references/dataProtector/dataProtectorSharing/subscription/subscribeToCollection.md b/src/references/dataProtector/dataProtectorSharing/subscription/subscribeToCollection.md
index 624bf2a5..78734975 100644
--- a/src/references/dataProtector/dataProtectorSharing/subscription/subscribeToCollection.md
+++ b/src/references/dataProtector/dataProtectorSharing/subscription/subscribeToCollection.md
@@ -6,7 +6,7 @@ description:
   no automatic renewal, using the Data Sharing smart contract.
 ---
 
-# subscribeToCollection
+# subscribeToCollection <ChainNotSupportedBadge />
 
 Method to subscribe to a collection.
 
@@ -136,4 +136,5 @@ See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
 </script>

From 648f750b5b15857ca17ef014f3eb7ebbb8629c05 Mon Sep 17 00:00:00 2001
From: Le-Caignec <robinlecaignec@yahoo.fr>
Date: Sun, 17 Aug 2025 15:43:45 +0200
Subject: [PATCH 11/27] feat: add TokenSymbol component and update
 documentation references

---
 src/components/TokenSymbol.vue                | 25 ++++++++++
 src/get-started/overview/what-is-iexec.md     |  8 +++-
 .../protocol/worker/manage-access.md          |  6 ++-
 .../protocol/worker/quick-start.md            | 12 +++--
 src/guides/build-iapp/manage-access.md        | 12 +++--
 src/guides/manage-data/manage-access.md       |  3 +-
 src/guides/use-iapp/getting-started.md        |  1 -
 src/guides/use-iapp/how-to-pay-executions.md  |  5 +-
 .../how-to-pay/how-to-pay-for-web3mail.md     | 44 +++++++----------
 .../how-to-pay/how-to-pay-for-web3telegram.md | 47 +++++++------------
 src/guides/use-iapp/introduction.md           |  8 +++-
 .../dataProtectorCore/grantAccess.md          |  3 +-
 .../dataProtectorCore/processProtectedData.md |  3 +-
 src/references/dataProtector/types.md         |  6 ++-
 src/references/web3mail/methods/sendEmail.md  |  5 +-
 .../web3telegram/methods/sendTelegram.md      |  5 +-
 16 files changed, 111 insertions(+), 82 deletions(-)
 create mode 100644 src/components/TokenSymbol.vue

diff --git a/src/components/TokenSymbol.vue b/src/components/TokenSymbol.vue
new file mode 100644
index 00000000..b5f54f06
--- /dev/null
+++ b/src/components/TokenSymbol.vue
@@ -0,0 +1,25 @@
+<template>
+  <span class="font-semibold text-inherit">{{ tokenSymbol }}</span>
+</template>
+
+<script setup lang="ts">
+import { computed } from 'vue';
+import useUserStore from '@/stores/useUser.store';
+
+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';
+});
+</script>
diff --git a/src/get-started/overview/what-is-iexec.md b/src/get-started/overview/what-is-iexec.md
index 11f43eb5..7649f867 100644
--- a/src/get-started/overview/what-is-iexec.md
+++ b/src/get-started/overview/what-is-iexec.md
@@ -38,14 +38,14 @@ providing a decentralized infrastructure that combines:
 3. **⚙️ Worker Network**
    - Distributed computing providers
    - Execute iApps securely
-   - Earn RLC tokens for contributions
+   - Earn <TokenSymbol /> tokens for contributions
 
 ## 🚀 **Key Features**
 
 - **TEE (Trusted Execution Environment)** support
 - **Zero-knowledge computation**
 - **Decentralized marketplace** for computing resources
-- **RLC token** for payments and governance
+- **<TokenSymbol /> token** for payments and governance
 - **Cross-chain compatibility**
 
 ## 🔗 **Get Started**
@@ -55,3 +55,7 @@ Ready to explore iExec? Check out:
 - [What is Protected Data?](/get-started/overview/what-is-protected-data)
 - [What is an iApp?](/get-started/overview/what-is-iapp)
 - [Hello World Tutorial](/get-started/helloWorld)
+
+<script setup>
+import TokenSymbol from '@/components/TokenSymbol.vue'
+</script>
diff --git a/src/get-started/protocol/worker/manage-access.md b/src/get-started/protocol/worker/manage-access.md
index b3631024..66b5756c 100644
--- a/src/get-started/protocol/worker/manage-access.md
+++ b/src/get-started/protocol/worker/manage-access.md
@@ -44,7 +44,7 @@ your workerpool:
 | key                 | description                                                                          |
 | ------------------- | ------------------------------------------------------------------------------------ |
 | `workerpool`        | workerpool address                                                                   |
-| `workerpoolprice`   | price to charge the requester for each execution of the app (in nRLC)                |
+| `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            |
@@ -106,3 +106,7 @@ cancel command.
 ```bash
 iexec order cancel --workerpool <orderHash>
 ```
+
+<script setup>
+import TokenSymbol from '@/components/TokenSymbol.vue'
+</script>
diff --git a/src/get-started/protocol/worker/quick-start.md b/src/get-started/protocol/worker/quick-start.md
index 47f10e4e..b6f96c93 100644
--- a/src/get-started/protocol/worker/quick-start.md
+++ b/src/get-started/protocol/worker/quick-start.md
@@ -14,11 +14,11 @@ 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 RLC 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 RLC. Some RLC must be deposited to your iExec
+- 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.
 
@@ -33,14 +33,18 @@ configuration documentation of the
 For security reason, it is **highly recommended** to launch your worker in a
 virtual machine.
 
-After having loaded some RLC and deposited them to your iExec account, you can
+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 RLCs.
+be able to compute some tasks coming from the iExec network to earn some <TokenSymbol />s.
 
 ## Wallet restriction
 
 An exclusive wallet must be associated to your worker. You need N wallets if you
 want N workers.
+
+<script setup>
+import TokenSymbol from '@/components/TokenSymbol.vue'
+</script>
diff --git a/src/guides/build-iapp/manage-access.md b/src/guides/build-iapp/manage-access.md
index fad6bb19..a325c2a5 100644
--- a/src/guides/build-iapp/manage-access.md
+++ b/src/guides/build-iapp/manage-access.md
@@ -40,7 +40,7 @@ Here's the simplified process:
 2. **You sign the order** with your wallet
 3. **You publish the order** on the iExec marketplace
 4. **Users can discover** and execute your iApp according to your conditions
-5. **You automatically receive** payment in RLC for each execution
+5. **You automatically receive** payment in <TokenSymbol /> for each execution
 
 ```
 Deployed iApp + Signed App Order = Application accessible on iExec
@@ -231,12 +231,12 @@ Here's the detailed description of each parameter:
 **Common values:**
 
 - `"0"` - Free
-- `"1000000000"` - 1 RLC per execution
-- `"500000000"` - 0.5 RLC per execution
+- `"1000000000"` - 1 <TokenSymbol /> per execution
+- `"500000000"` - 0.5 <TokenSymbol /> per execution
 
 ::: tip
 
-1 RLC = 1,000,000,000 nRLC (10^9)
+1 <TokenSymbol /> = 1,000,000,000 nano <TokenSymbol /> (10^9)
 
 :::
 
@@ -301,3 +301,7 @@ Next steps:
   Complete CLI reference
 - **[Official Orders Documentation](https://protocol.docs.iex.ec/for-developers/advanced/manage-your-apporders)** -
   Protocol-level order management
+
+<script setup>
+import TokenSymbol from '@/components/TokenSymbol.vue'
+</script>
diff --git a/src/guides/manage-data/manage-access.md b/src/guides/manage-data/manage-access.md
index d0d0deb1..13863327 100644
--- a/src/guides/manage-data/manage-access.md
+++ b/src/guides/manage-data/manage-access.md
@@ -190,7 +190,7 @@ yourself!
 Set to `0` for free access, or specify a price to monetize your data
 automatically.
 
-**Example**: `pricePerAccess: 1_000_000_000` = 1 RLC per access
+**Example**: `pricePerAccess: 1_000_000_000` = 1 <TokenSymbol /> per access
 
 → **Want to learn more monetization capabilities?** See our detailed
 [Monetize Protected Data guide](/guides/manage-data/monetize-protected-data)
@@ -232,4 +232,5 @@ steps:
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
 import OptionalBadge from '@/components/OptionalBadge.vue'
+import TokenSymbol from '@/components/TokenSymbol.vue'
 </script>
diff --git a/src/guides/use-iapp/getting-started.md b/src/guides/use-iapp/getting-started.md
index cbd9667e..8a00cf16 100644
--- a/src/guides/use-iapp/getting-started.md
+++ b/src/guides/use-iapp/getting-started.md
@@ -17,7 +17,6 @@ Before you begin, make sure you have:
 - Some RLC tokens for paying computation fees (or access to free vouchers
   through learning programs) - [Learn about RLC tokens](/get-started/rlc) and
   [how to bridge them](/get-started/tooling-and-explorers/bridge)
-  - **Note**: On Arbitrum, you'll need AETH (Arbitrum ETH) instead of RLC
 - Basic understanding of blockchain transactions
 - iExec SDK installed
 
diff --git a/src/guides/use-iapp/how-to-pay-executions.md b/src/guides/use-iapp/how-to-pay-executions.md
index 86f7a76b..e49dbdd6 100644
--- a/src/guides/use-iapp/how-to-pay-executions.md
+++ b/src/guides/use-iapp/how-to-pay-executions.md
@@ -14,7 +14,7 @@ and cost management strategies.
 
 iExec supports multiple payment methods for executing iApps:
 
-1. **RLC Tokens**: Direct payment using RLC (Request Compute Language) tokens
+1. **RLC Tokens**: Direct payment using <TokenSymbol /> tokens
 2. **Vouchers**: Pre-funded vouchers for simplified payment
 3. **Mixed Payment**: Combination of RLC and vouchers
 
@@ -120,7 +120,7 @@ const result = await dataProtectorCore.processProtectedData({
 
 ::: tip
 
-If your voucher doesn't have enough xRLC to cover the deal, the SDK will
+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.
@@ -496,4 +496,5 @@ Now that you understand payment methods:
 
 <script setup>
 import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
+import TokenSymbol from '@/components/TokenSymbol.vue'
 </script>
diff --git a/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3mail.md b/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3mail.md
index dea0db5f..3d8f72aa 100644
--- a/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3mail.md
+++ b/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3mail.md
@@ -2,7 +2,7 @@
 title: How to Pay for Web3Mail
 description:
   Learn how to pay for Web3Mail's confidential computing power using vouchers
-  and xLC for secure, blockchain-based email communication.
+  and RLC for secure, blockchain-based email communication.
 ---
 
 # How to Pay for Web3Mail
@@ -14,7 +14,7 @@ The `sendEmail` function uses confidential computing power to encrypt and send
 messages, ensuring secure and decentralized email exchanges.
 
 This guide explains how to pay for Web3Mail's computing power using **vouchers**
-and **xRLC**, detailing the steps for each method.
+and **<TokenSymbol />**, detailing the steps for each method.
 
 ## Using Vouchers for Web3Mail <ChainNotSupportedBadge />
 
@@ -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 xRLC for fallback payment in Web3Mail, refer
-to the **Using xRLC 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
 
@@ -73,9 +73,9 @@ const sendEmail = await web3mail.sendEmail({
 });
 ```
 
-## Using xRLC for Web3Mail
+## Using <TokenSymbol /> for Web3Mail
 
-If you choose to use xRLC to cover the computational cost of Web3Mail (or if you
+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:
 
@@ -83,7 +83,7 @@ address), follow these steps:
 
 To manage RLC tokens, developers must use the iExec SDK, which offers all the
 necessary tools for interacting with the iExec platform. This includes
-depositing, withdrawing, and checking balances of RLC and xRLC
+depositing, withdrawing, and checking balances of RLC and <TokenSymbol />
 
 - In your JS/TS project npm install iexec
 - Instantiate the iExec SDK (see the
@@ -97,32 +97,19 @@ const iexec = new IExec({ ethProvider: window.ethereum });
 
 ### Purchase RLC
 
-Obtain RLC tokens from a supported cryptocurrency exchange.
+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.
 
-### Convert to xRLC
+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.
 
-Use the iExec Bridge to convert your RLC into xRLC for use on iExec's sidechain.
-The bridging operation follows the lock & mint / burn & unlock principle. When
-sending tokens from Mainnet to Bellecour, the bridge locks the initial amount on
-the source chain and mints the equivalent on the destination chain. When going
-in the other direction, it burns tokens on the Sidechain and unlocks the same
-amount on Mainnet. The bridged asset is called xRLC on Bellecour.
+### Deposit <TokenSymbol />
 
-Users can send tokens from the Ethereum Mainnet to the iExec Sidechain or
-vice-versa using the Account Manager
-([iExec Explorer](https://explorer.iex.ec/bellecour) or
-[POA Bridge UI](https://bridge-bellecour.iex.ec/)) available across all iExec
-products.
-
-### Deposit xRLC
-
-Deposit the xRLC into your iExec account using the command:
+Deposit the <TokenSymbol /> into your iExec account using the command:
 
 ```javascript
-iexec.account.deposit(xRLC_amount);
+iexec.account.deposit(RLC_amount);
 ```
 
-This converts xRLC 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
 
@@ -135,7 +122,7 @@ iexec.account.show();
 ### Execute sendEmail
 
 Set the `useVoucher` parameter to `false` when using Web3Mail's sendEmail
-function to pay with xRLC:
+function to pay with <TokenSymbol />:
 
 ```ts twoslash
 import { IExecWeb3mail, getWeb3Provider } from '@iexec/web3mail';
@@ -153,7 +140,7 @@ const sendEmail = await web3mail.sendEmail({
 
 ### Withdraw sRLC (If Desired)
 
-Convert sRLC back to xRLC and withdraw to your wallet using:
+Convert sRLC back to <TokenSymbol /> and withdraw to your wallet using:
 
 ```javascript
 iexec.account.withdraw(RLC_amount);
@@ -163,4 +150,5 @@ iexec.account.withdraw(RLC_amount);
 // Assets
 import builderDashboardImage from '@/assets/tooling-&-explorers/builder-dashboard/builder-dashboard.png';
 import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
+import TokenSymbol from '@/components/TokenSymbol.vue'
 </script>
diff --git a/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3telegram.md b/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3telegram.md
index 2227bb68..518638bc 100644
--- a/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3telegram.md
+++ b/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3telegram.md
@@ -1,9 +1,8 @@
 ---
 title: How to Pay for Web3Telegram
 description:
-  Learn how to pay for Web3Telegram using vouchers or xRLC. This guide walks you
-  through obtaining vouchers, managing RLC to xRLC conversion, and using both
-  methods for secure Telegram 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
@@ -15,7 +14,7 @@ The `sendTelegram` function uses confidential computing power to encrypt and
 send messages, ensuring secure and decentralized email exchanges.
 
 This guide explains how to pay for Web3Telegram's computing power using
-**vouchers** and **xRLC**, detailing the steps for each method.
+**vouchers** and **<TokenSymbol />**, detailing the steps for each method.
 
 ## Using Vouchers for Web3Telegram <ChainNotSupportedBadge />
 
@@ -53,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 xRLC for fallback payment in Web3Telegram,
-refer to the **Using xRLC 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
 
@@ -80,9 +79,9 @@ const sendTelegram = await web3telegram.sendTelegram({
 });
 ```
 
-## Using xRLC for Web3Telegram
+## Using <TokenSymbol /> for Web3Telegram
 
-If you choose to use xRLC to cover the computational cost of Web3Telegram (or if
+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:
 
@@ -90,7 +89,7 @@ follow these steps:
 
 To manage RLC tokens, developers must use the iExec SDK, which offers all the
 necessary tools for interacting with the iExec platform. This includes
-depositing, withdrawing, and checking balances of RLC and xRLC
+depositing, withdrawing, and checking balances of RLC and <TokenSymbol />
 
 - In your JS/TS project npm install iexec
 - Instantiate the iExec SDK (see the
@@ -104,32 +103,19 @@ const iexec = new IExec({ ethProvider: window.ethereum });
 
 ### Purchase RLC
 
-Obtain RLC tokens from a supported cryptocurrency exchange.
+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.
 
-### Convert to xRLC
+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.
 
-Use the iExec Bridge to convert your RLC into xRLC for use on iExec's sidechain.
-The bridging operation follows the lock & mint / burn & unlock principle. When
-sending tokens from Mainnet to Bellecour, the bridge locks the initial amount on
-the source chain and mints the equivalent on the destination chain. When going
-in the other direction, it burns tokens on the Sidechain and unlocks the same
-amount on Mainnet. The bridged asset is called xRLC on Bellecour.
+### Deposit <TokenSymbol />
 
-Users can send tokens from the Ethereum Mainnet to the iExec Sidechain or
-vice-versa using the Account Manager
-([iExec Explorer](https://explorer.iex.ec/bellecour) or
-[POA Bridge UI](https://bridge-bellecour.iex.ec/)) available across all iExec
-products.
-
-### Deposit xRLC
-
-Deposit the xRLC into your iExec account using the command:
+Deposit the <TokenSymbol /> into your iExec account using the command:
 
 ```javascript
-iexec.account.deposit(xRLC_amount);
+iexec.account.deposit(RLC_amount);
 ```
 
-This converts xRLC 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
 
@@ -142,7 +128,7 @@ iexec.account.show();
 ### Execute `sendTelegram`
 
 Set the `useVoucher` parameter to `false` when using Web3Telegram's sendTelegram
-function to pay with xRLC:
+function to pay with <TokenSymbol />:
 
 ```ts twoslash
 import { IExecWeb3telegram, getWeb3Provider } from '@iexec/web3telegram';
@@ -166,7 +152,7 @@ const sendTelegram = await web3telegram.sendTelegram({
 
 ### Withdraw sRLC (If Desired)
 
-Convert sRLC back to xRLC and withdraw to your wallet using:
+Convert sRLC back to <TokenSymbol /> and withdraw to your wallet using:
 
 ```javascript
 iexec.account.withdraw(RLC_amount);
@@ -176,4 +162,5 @@ iexec.account.withdraw(RLC_amount);
 // Assets
 import builderDashboardImage from '@/assets/tooling-&-explorers/builder-dashboard/builder-dashboard.png';
 import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
+import TokenSymbol from '@/components/TokenSymbol.vue'
 </script>
diff --git a/src/guides/use-iapp/introduction.md b/src/guides/use-iapp/introduction.md
index 223cf203..0874e948 100644
--- a/src/guides/use-iapp/introduction.md
+++ b/src/guides/use-iapp/introduction.md
@@ -53,7 +53,7 @@ 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**: RLC tokens are distributed to all participants
+9. **Payment Settlement**: <TokenSymbol /> tokens are distributed to all participants
 
 ### Network Architecture Diagram
 
@@ -70,7 +70,7 @@ 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**: RLC tokens are distributed to all participants
+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
@@ -82,3 +82,7 @@ protected throughout the computation.
 Ready to start using iApps? Check out our
 [Getting Started Guide](./getting-started.md) to learn how to find, execute, and
 interact with iApps on the iExec network.
+
+<script setup>
+import TokenSymbol from '@/components/TokenSymbol.vue'
+</script>
diff --git a/src/references/dataProtector/dataProtectorCore/grantAccess.md b/src/references/dataProtector/dataProtectorCore/grantAccess.md
index effb7a4f..fc8d2fd1 100644
--- a/src/references/dataProtector/dataProtectorCore/grantAccess.md
+++ b/src/references/dataProtector/dataProtectorCore/grantAccess.md
@@ -165,7 +165,7 @@ const grantedAccess = await dataProtectorCore.grantAccess({
 ::: tip
 
 `pricePerAccess` is expressed in nano RLC (nRLC). nRLC is the smallest
-subdivision of the RLC token, 1 RLC equals to 10^9 nRLC.
+subdivision of the <TokenSymbol /> token, 1 <TokenSymbol /> equals to 10^9 nRLC.
 
 When provided, `pricePerAccess` must be a non-negative integer value.
 
@@ -254,4 +254,5 @@ The result of this method confirms the new access grant. It consists of a JSON
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
 import OptionalBadge from '@/components/OptionalBadge.vue'
+import TokenSymbol from '@/components/TokenSymbol.vue'
 </script>
diff --git a/src/references/dataProtector/dataProtectorCore/processProtectedData.md b/src/references/dataProtector/dataProtectorCore/processProtectedData.md
index c27f5e74..b52da37c 100644
--- a/src/references/dataProtector/dataProtectorCore/processProtectedData.md
+++ b/src/references/dataProtector/dataProtectorCore/processProtectedData.md
@@ -153,7 +153,7 @@ const processProtectedDataResponse =
 
 ::: tip
 
-If your voucher doesn't have enough xRLC to cover the deal, the SDK will
+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.
@@ -500,4 +500,5 @@ processed during the task.
 import RequiredBadge from '@/components/RequiredBadge.vue'
 import OptionalBadge from '@/components/OptionalBadge.vue'
 import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
+import TokenSymbol from '@/components/TokenSymbol.vue'
 </script>
diff --git a/src/references/dataProtector/types.md b/src/references/dataProtector/types.md
index db89799b..96a22f72 100644
--- a/src/references/dataProtector/types.md
+++ b/src/references/dataProtector/types.md
@@ -17,7 +17,7 @@ Types in DataProtector.
 
 ### datasetprice: <span class="text-yellow">`string`</span>
 
-- Price (iun nRLC) to charge the user specified in `requesterrestrict` for each
+- Price (in n<TokenSymbol />) to charge the user specified in `requesterrestrict` for each
   use of this `protectedData`
 
 ### volume: <span class="text-yellow">`string`</span>
@@ -122,3 +122,7 @@ _Hash example:_ `0xc9c2d58fc01fe54149b7daf49a0026d4ab1fdd3d10fb7c76350790fff03fe
 
 You can read more about he iExec Explorer
 [here](https://protocol.docs.iex.ec/for-developers/toolbox/iexec-explorer).
+
+<script setup>
+import TokenSymbol from '@/components/TokenSymbol.vue'
+</script>
diff --git a/src/references/web3mail/methods/sendEmail.md b/src/references/web3mail/methods/sendEmail.md
index cb4e3083..66e8528e 100644
--- a/src/references/web3mail/methods/sendEmail.md
+++ b/src/references/web3mail/methods/sendEmail.md
@@ -21,7 +21,7 @@ documentation for more details.
 
 ::: tip
 
-For executing the `sendEmail` method with a voucher or xRLC, refer to the
+For executing the `sendEmail` method with a voucher or <TokenSymbol />, refer to the
 dedicated section in the documentation under
 "[How to Pay for web3mail](/guides/use-iapp/how-to-pay/how-to-pay-for-web3mail)".
 
@@ -136,7 +136,7 @@ const sendEmail = await web3mail.sendEmail({
 
 ::: tip
 
-If your voucher doesn't have enough xRLC to cover the deal, the SDK will
+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.
@@ -395,4 +395,5 @@ For any other errors, you'll get a `WorkflowError` error in the form of:
 import RequiredBadge from '@/components/RequiredBadge.vue'
 import OptionalBadge from '@/components/OptionalBadge.vue'
 import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
+import TokenSymbol from '@/components/TokenSymbol.vue'
 </script>
diff --git a/src/references/web3telegram/methods/sendTelegram.md b/src/references/web3telegram/methods/sendTelegram.md
index 3801dacc..8a6157fa 100644
--- a/src/references/web3telegram/methods/sendTelegram.md
+++ b/src/references/web3telegram/methods/sendTelegram.md
@@ -21,7 +21,7 @@ documentation for more details.
 
 ::: tip
 
-For executing the `sendTelegram` method with a voucher or xRLC, refer to the
+For executing the `sendTelegram` method with a voucher or <TokenSymbol />, refer to the
 dedicated section in the documentation under
 "[How to Pay for web3telegram](/guides/use-iapp/how-to-pay/how-to-pay-for-web3telegram)".
 
@@ -147,7 +147,7 @@ const sendTelegram = await web3telegram.sendTelegram({
 
 ::: tip
 
-If your voucher doesn't have enough xRLC to cover the deal, the SDK will
+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.
@@ -297,4 +297,5 @@ the status of the `sendTelegram` method by monitoring the task on the
 <script setup>
 import OptionalBadge from '@/components/OptionalBadge.vue'
 import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
+import TokenSymbol from '@/components/TokenSymbol.vue'
 </script>

From f07498f73a967872e1b911c6f107dc30cc74b041 Mon Sep 17 00:00:00 2001
From: Le-Caignec <robinlecaignec@yahoo.fr>
Date: Sun, 17 Aug 2025 16:02:15 +0200
Subject: [PATCH 12/27] refactor: clean up whitespace and improve documentation
 clarity

---
 src/components/TokenSymbol.vue                |  4 +--
 .../protocol/worker/manage-access.md          | 22 ++++++++--------
 .../protocol/worker/quick-start.md            | 14 +++++-----
 src/guides/use-iapp/getting-started.md        |  2 +-
 src/guides/use-iapp/how-to-pay-executions.md  |  8 +++---
 .../how-to-pay/how-to-pay-for-web3mail.md     | 22 ++++++++++------
 .../how-to-pay/how-to-pay-for-web3telegram.md | 26 ++++++++++++-------
 src/guides/use-iapp/introduction.md           |  7 ++---
 .../dataProtectorCore/processProtectedData.md |  8 +++---
 src/references/dataProtector/types.md         |  4 +--
 src/references/iapp-generator.md              |  7 ++---
 src/references/web3mail/methods/sendEmail.md  | 12 ++++-----
 .../web3telegram/methods/sendTelegram.md      | 12 ++++-----
 src/utils/bellecourChainConfig.ts             | 22 ----------------
 src/utils/chain.utils.ts                      | 13 +++++++---
 15 files changed, 92 insertions(+), 91 deletions(-)
 delete mode 100644 src/utils/bellecourChainConfig.ts

diff --git a/src/components/TokenSymbol.vue b/src/components/TokenSymbol.vue
index b5f54f06..5778577a 100644
--- a/src/components/TokenSymbol.vue
+++ b/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';
 });
diff --git a/src/get-started/protocol/worker/manage-access.md b/src/get-started/protocol/worker/manage-access.md
index 66b5756c..bba873b3 100644
--- a/src/get-started/protocol/worker/manage-access.md
+++ b/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.
diff --git a/src/get-started/protocol/worker/quick-start.md b/src/get-started/protocol/worker/quick-start.md
index b6f96c93..371f58f1 100644
--- a/src/get-started/protocol/worker/quick-start.md
+++ b/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
 
diff --git a/src/guides/use-iapp/getting-started.md b/src/guides/use-iapp/getting-started.md
index 8a00cf16..e70c10c4 100644
--- a/src/guides/use-iapp/getting-started.md
+++ b/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
diff --git a/src/guides/use-iapp/how-to-pay-executions.md b/src/guides/use-iapp/how-to-pay-executions.md
index e49dbdd6..cce12e86 100644
--- a/src/guides/use-iapp/how-to-pay-executions.md
+++ b/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.
 
 :::
 
diff --git a/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3mail.md b/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3mail.md
index 3d8f72aa..4a96ddca 100644
--- a/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3mail.md
+++ b/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
 
diff --git a/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3telegram.md b/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3telegram.md
index 518638bc..6dab94f6 100644
--- a/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3telegram.md
+++ b/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
 
diff --git a/src/guides/use-iapp/introduction.md b/src/guides/use-iapp/introduction.md
index 0874e948..88a296b1 100644
--- a/src/guides/use-iapp/introduction.md
+++ b/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
diff --git a/src/references/dataProtector/dataProtectorCore/processProtectedData.md b/src/references/dataProtector/dataProtectorCore/processProtectedData.md
index b52da37c..c0f0f132 100644
--- a/src/references/dataProtector/dataProtectorCore/processProtectedData.md
+++ b/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.
 
 :::
 
diff --git a/src/references/dataProtector/types.md b/src/references/dataProtector/types.md
index 96a22f72..3bc83212 100644
--- a/src/references/dataProtector/types.md
+++ b/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>
 
diff --git a/src/references/iapp-generator.md b/src/references/iapp-generator.md
index 25990a96..c2ac47a6 100644
--- a/src/references/iapp-generator.md
+++ b/src/references/iapp-generator.md
@@ -67,8 +67,8 @@ Ready for production? Dive into specialized topics:
 
 - **[Using TDX (Experimental)](/guides/build-iapp/using-tdx)** - Next-gen TEE
   technology
-- **[Complete Guides Overview](/guides/build-iapp/)** - All development guides
-  in one place
+- **[Complete Guides Overview](/guides/build-iapp/build-&-deploy)** - All
+  development guides in one place
 
 ## Why Choose iApp Generator?
 
@@ -109,7 +109,8 @@ applications:
 
 ### Need Help?
 
-- **[Complete Guides](/guides/build-iapp/)** - All development guides
+- **[Complete Guides](/guides/build-iapp/build-&-deploy)** - All development
+  guides
 - **[iExec Discord](https://discord.com/invite/pbt9m98wnU)** - Community support
 - **[Protocol Documentation](https://protocol.docs.iex.ec)** - Technical deep
   dive
diff --git a/src/references/web3mail/methods/sendEmail.md b/src/references/web3mail/methods/sendEmail.md
index 66e8528e..7bd39ea0 100644
--- a/src/references/web3mail/methods/sendEmail.md
+++ b/src/references/web3mail/methods/sendEmail.md
@@ -21,8 +21,8 @@ documentation for more details.
 
 ::: tip
 
-For executing the `sendEmail` method with a voucher or <TokenSymbol />, refer to the
-dedicated section in the documentation under
+For executing the `sendEmail` method with a voucher or <TokenSymbol />, refer to
+the dedicated section in the documentation under
 "[How to Pay for web3mail](/guides/use-iapp/how-to-pay/how-to-pay-for-web3mail)".
 
 :::
@@ -136,10 +136,10 @@ const sendEmail = await web3mail.sendEmail({
 
 ::: 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.
 
 :::
 
diff --git a/src/references/web3telegram/methods/sendTelegram.md b/src/references/web3telegram/methods/sendTelegram.md
index 8a6157fa..3c37d60e 100644
--- a/src/references/web3telegram/methods/sendTelegram.md
+++ b/src/references/web3telegram/methods/sendTelegram.md
@@ -21,8 +21,8 @@ documentation for more details.
 
 ::: tip
 
-For executing the `sendTelegram` method with a voucher or <TokenSymbol />, refer to the
-dedicated section in the documentation under
+For executing the `sendTelegram` method with a voucher or <TokenSymbol />, refer
+to the dedicated section in the documentation under
 "[How to Pay for web3telegram](/guides/use-iapp/how-to-pay/how-to-pay-for-web3telegram)".
 
 :::
@@ -147,10 +147,10 @@ const sendTelegram = await web3telegram.sendTelegram({
 
 ::: 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.
 
 :::
 
diff --git a/src/utils/bellecourChainConfig.ts b/src/utils/bellecourChainConfig.ts
deleted file mode 100644
index 156eb43f..00000000
--- a/src/utils/bellecourChainConfig.ts
+++ /dev/null
@@ -1,22 +0,0 @@
-import { type Chain } from 'viem';
-
-export const bellecour = {
-  id: 0x86,
-  name: 'iExec Sidechain',
-  nativeCurrency: {
-    decimals: 18,
-    name: 'xRLC',
-    symbol: 'xRLC',
-  },
-  rpcUrls: {
-    public: { http: ['https://bellecour.iex.ec'] },
-    default: { http: ['https://bellecour.iex.ec'] },
-  },
-  blockExplorers: {
-    etherscan: {
-      name: 'Blockscout',
-      url: 'https://blockscout-bellecour.iex.ec',
-    },
-    default: { name: 'Blockscout', url: 'https://blockscout-bellecour.iex.ec' },
-  },
-} as const satisfies Chain;
diff --git a/src/utils/chain.utils.ts b/src/utils/chain.utils.ts
index eed3f0ad..491c4230 100644
--- a/src/utils/chain.utils.ts
+++ b/src/utils/chain.utils.ts
@@ -1,5 +1,5 @@
 import { arbitrum } from 'viem/chains';
-import { bellecour } from './bellecourChainConfig';
+import { bellecour } from './wagmiNetworks';
 import arbitrumLogo from '@/assets/icons/arbitrum.svg';
 import iexecLogo from '@/assets/icons/iexec-logo.png';
 
@@ -36,12 +36,19 @@ export function getSupportedChains(): Chain[] {
       blockExplorers: arbitrum.blockExplorers,
     },
     {
-      id: bellecour.id,
+      id: Number(bellecour.id),
       name: bellecour.name,
       icon: iexecLogo,
       nativeCurrency: bellecour.nativeCurrency,
       rpcUrls: bellecour.rpcUrls,
-      blockExplorers: bellecour.blockExplorers,
+      blockExplorers: {
+        default: {
+          name: bellecour.blockExplorers?.default?.name || 'Blockscout',
+          url:
+            bellecour.blockExplorers?.default?.url ||
+            'https://blockscout-bellecour.iex.ec',
+        },
+      },
     },
   ];
 }

From d54e9002686dbe50056aee2e271b6332758bc027 Mon Sep 17 00:00:00 2001
From: Le-Caignec <robinlecaignec@yahoo.fr>
Date: Sun, 17 Aug 2025 16:19:41 +0200
Subject: [PATCH 13/27] docs: update documentation links and import paths for
 consistency

---
 README.md                                          |  2 +-
 src/components/AddressChip.vue                     |  4 ++--
 src/get-started/helloWorld/2-protectData.md        |  2 +-
 src/get-started/helloWorld/4-manageDataAccess.md   |  4 ++--
 src/get-started/helloWorld/5-bonusChapter.md       |  2 +-
 src/get-started/rlc.md                             |  8 ++++----
 src/guides/use-iapp/add-inputs-to-execution.md     |  8 +++++---
 src/guides/use-iapp/different-ways-to-execute.md   |  7 ++++---
 src/guides/use-iapp/getting-started.md             | 14 +++++++-------
 src/guides/use-iapp/how-to-pay-executions.md       |  6 ++++--
 src/guides/use-iapp/introduction.md                |  4 ++--
 .../use-iapp/use-iapp-with-protected-data.md       |  8 +++++---
 src/modules/helloWorld/CouponCode.vue              |  2 +-
 src/modules/helloWorld/GrantAccess.vue             |  2 +-
 src/modules/helloWorld/ProtectData.vue             |  2 +-
 .../advanced/advanced-configuration.md             |  3 ++-
 .../dataProtector/advanced/apps-whitelist.md       |  4 ++--
 .../apps-whitelist/addAppToAddOnlyAppWhitelist.md  |  3 ++-
 .../dataProtectorCore/getGrantedAccess.md          | 14 +++++++-------
 .../dataProtectorCore/getProtectedData.md          |  5 +++--
 .../dataProtector/dataProtectorCore/grantAccess.md |  2 +-
 .../dataProtectorCore/processProtectedData.md      |  5 +++--
 .../dataProtectorCore/revokeAllAccess.md           |  2 +-
 .../dataProtectorCore/revokeOneAccess.md           |  5 +++--
 .../dataProtector/dataProtectorSharing.md          |  2 +-
 .../collection/addToCollection.md                  |  5 +++--
 .../collection/removeCollection.md                 |  5 +++--
 .../removeProtectedDataFromCollection.md           |  3 ++-
 .../consume/consumeProtectedData.md                |  6 ++++--
 .../renting/removeProtectedDataFromRenting.md      |  3 ++-
 .../renting/rentProtectedData.md                   |  7 ++++---
 .../renting/setProtectedDataRentingParams.md       |  3 ++-
 .../renting/setProtectedDataToRenting.md           |  3 ++-
 .../selling/buyProtectedData.md                    |  5 +++--
 .../selling/removeProtectedDataForSale.md          |  3 ++-
 .../selling/setProtectedDataForSale.md             |  3 ++-
 .../removeProtectedDataFromSubscription.md         |  3 ++-
 .../subscription/setProtectedDataToSubscription.md |  3 ++-
 .../subscription/setSubscriptionParams.md          |  3 ++-
 .../subscription/subscribeToCollection.md          |  3 ++-
 src/references/dataProtector/getting-started.md    |  8 ++++----
 src/references/dataProtector/types.md              |  5 +++--
 src/references/web3telegram.md                     |  2 +-
 .../injected-wallet-provider.ts                    |  2 +-
 src/utils/wagmiConfig.ts                           |  6 +++---
 45 files changed, 115 insertions(+), 86 deletions(-)

diff --git a/README.md b/README.md
index 7dd51cab..6b071c8c 100644
--- a/README.md
+++ b/README.md
@@ -79,7 +79,7 @@ steps to contribute:
 
 Fork this repository and ensure you're working on the `main` branch:
 
-[![fork-button](./src/public/fork-button.png)](https://github.com/iExecBlockchainComputing/documentation/fork)
+[![fork-button](/src/public/fork-button.png)](https://github.com/iExecBlockchainComputing/documentation/fork)
 
 ### 2. Set Up Your Development Environment
 
diff --git a/src/components/AddressChip.vue b/src/components/AddressChip.vue
index 568c6117..90598dac 100644
--- a/src/components/AddressChip.vue
+++ b/src/components/AddressChip.vue
@@ -15,8 +15,8 @@
 <script setup>
 import { ref, computed } from 'vue';
 import avatarStyles from './profile.module.css';
-import { getAvatarVisualNumber } from '../utils/getAvatarVisualNumber';
-import { truncateAddress } from '../utils/truncateAddress';
+import { getAvatarVisualNumber } from '@/utils/getAvatarVisualNumber';
+import { truncateAddress } from '@/utils/truncateAddress';
 
 const props = defineProps({
   address: {
diff --git a/src/get-started/helloWorld/2-protectData.md b/src/get-started/helloWorld/2-protectData.md
index b7e7903d..06d841f7 100644
--- a/src/get-started/helloWorld/2-protectData.md
+++ b/src/get-started/helloWorld/2-protectData.md
@@ -6,7 +6,7 @@ description:
 ---
 
 <script setup>
-import ProtectData from '../../modules/helloWorld/ProtectData.vue';
+import ProtectData from '@/modules/helloWorld/ProtectData.vue';
 </script>
 
 # 🛡️ Let's Protect Data
diff --git a/src/get-started/helloWorld/4-manageDataAccess.md b/src/get-started/helloWorld/4-manageDataAccess.md
index 7addca54..e937396d 100644
--- a/src/get-started/helloWorld/4-manageDataAccess.md
+++ b/src/get-started/helloWorld/4-manageDataAccess.md
@@ -6,8 +6,8 @@ description:
 ---
 
 <script setup>
-import GrantAccess from '../../modules/helloWorld/GrantAccess.vue';
-import { useWalletConnection } from '../../hooks/useWalletConnection.vue';
+import GrantAccess from '@/modules/helloWorld/GrantAccess.vue';
+import { useWalletConnection } from '@/hooks/useWalletConnection.vue';
 
 const { protectedDataAddress } = useWalletConnection();
 </script>
diff --git a/src/get-started/helloWorld/5-bonusChapter.md b/src/get-started/helloWorld/5-bonusChapter.md
index 1c04bd22..0897a677 100644
--- a/src/get-started/helloWorld/5-bonusChapter.md
+++ b/src/get-started/helloWorld/5-bonusChapter.md
@@ -58,7 +58,7 @@ description:
 </template>
 
 <script setup>
-import CouponCode from '../../modules/helloWorld/CouponCode.vue';
+import CouponCode from '@/modules/helloWorld/CouponCode.vue';
 import Button from '@/components/ui/Button.vue';
 import useUserStore from '@/stores/useUser.store';
 import { computed } from 'vue';
diff --git a/src/get-started/rlc.md b/src/get-started/rlc.md
index 166063ec..fd2a03ce 100644
--- a/src/get-started/rlc.md
+++ b/src/get-started/rlc.md
@@ -117,10 +117,10 @@ You can acquire RLC tokens through several methods:
 
 Ready to dive into the iExec ecosystem? Here are the next steps:
 
-- **[Bridge RLC](./tooling-and-explorers/bridge.md)** - Transfer RLC between
-  networks
-- **[Start Using iExec](./quick-start.md)** - Begin your confidential computing
-  journey
+- **[Bridge RLC](/get-started/tooling-and-explorers/bridge)** - Transfer RLC
+  between networks
+- **[Start Using iExec](/get-started/quick-start)** - Begin your confidential
+  computing journey
 - **[Earn RLC](/guides/manage-data/manage-access)** - Become a provider and
   monetize your resources
 
diff --git a/src/guides/use-iapp/add-inputs-to-execution.md b/src/guides/use-iapp/add-inputs-to-execution.md
index 79469175..c9c6d3ba 100644
--- a/src/guides/use-iapp/add-inputs-to-execution.md
+++ b/src/guides/use-iapp/add-inputs-to-execution.md
@@ -333,6 +333,8 @@ const dbPassword = process.env.IEXEC_SECRET_2; // 'database-password'
 Now that you understand how to add inputs to iApp executions:
 
 - Learn about
-  [Using iApps with Protected Data](./use-iapp-with-protected-data.md)
-- Explore [Different Ways to Execute](./different-ways-to-execute.md) iApps
-- Check out our [How to Pay for Executions](./how-to-pay-executions.md) guide
+  [Using iApps with Protected Data](/guides/use-iapp/use-iapp-with-protected-data)
+- Explore
+  [Different Ways to Execute](/guides/use-iapp/different-ways-to-execute) iApps
+- Check out our
+  [How to Pay for Executions](/guides/use-iapp/how-to-pay-executions) guide
diff --git a/src/guides/use-iapp/different-ways-to-execute.md b/src/guides/use-iapp/different-ways-to-execute.md
index c9fbd30c..2cd2afd3 100644
--- a/src/guides/use-iapp/different-ways-to-execute.md
+++ b/src/guides/use-iapp/different-ways-to-execute.md
@@ -109,6 +109,7 @@ iapp test
 ## Next Steps
 
 - Learn how to
-  [use iApps with protected data](./use-iapp-with-protected-data.md)
-- Discover how to [add inputs to execution](./add-inputs-to-execution.md)
-- Understand [how to pay for executions](./how-to-pay-executions.md)
+  [use iApps with protected data](/guides/use-iapp/use-iapp-with-protected-data)
+- Discover how to
+  [add inputs to execution](/guides/use-iapp/add-inputs-to-execution)
+- Understand [how to pay for executions](/guides/use-iapp/how-to-pay-executions)
diff --git a/src/guides/use-iapp/getting-started.md b/src/guides/use-iapp/getting-started.md
index e70c10c4..2d9c22ed 100644
--- a/src/guides/use-iapp/getting-started.md
+++ b/src/guides/use-iapp/getting-started.md
@@ -73,14 +73,14 @@ section.
 
 For step-by-step instructions, check out these guides:
 
-- **[Different Ways to Execute](./different-ways-to-execute.md)** - iExec cli,
-  lib, and other execution methods
-- **[Use iApps with Protected Data](./use-iapp-with-protected-data.md)** -
+- **[Different Ways to Execute](/guides/use-iapp/different-ways-to-execute)** -
+  iExec cli, lib, and other execution methods
+- **[Use iApps with Protected Data](/guides/use-iapp/use-iapp-with-protected-data)** -
   Working with sensitive data securely
-- **[Add Inputs to Execution](./add-inputs-to-execution.md)** - How to provide
-  data and parameters to iApps
-- **[How to Pay for Executions](./how-to-pay-executions.md)** - Understanding
-  costs and payment options
+- **[Add Inputs to Execution](/guides/use-iapp/add-inputs-to-execution)** - How
+  to provide data and parameters to iApps
+- **[How to Pay for Executions](/guides/use-iapp/how-to-pay-executions)** -
+  Understanding costs and payment options
 
 ## Quick Start
 
diff --git a/src/guides/use-iapp/how-to-pay-executions.md b/src/guides/use-iapp/how-to-pay-executions.md
index cce12e86..08eb9754 100644
--- a/src/guides/use-iapp/how-to-pay-executions.md
+++ b/src/guides/use-iapp/how-to-pay-executions.md
@@ -490,8 +490,10 @@ const executeWithPaymentRetry = async (params: any, maxRetries = 3) => {
 
 Now that you understand payment methods:
 
-- Learn about [Adding Inputs to Execution](./add-inputs-to-execution.md)
-- Explore [Using iApps with Protected Data](./use-iapp-with-protected-data.md)
+- Learn about
+  [Adding Inputs to Execution](/guides/use-iapp/add-inputs-to-execution)
+- Explore
+  [Using iApps with Protected Data](/guides/use-iapp/use-iapp-with-protected-data)
 - Review the pricing information above for detailed cost analysis
 
 <script setup>
diff --git a/src/guides/use-iapp/introduction.md b/src/guides/use-iapp/introduction.md
index 88a296b1..5aef1167 100644
--- a/src/guides/use-iapp/introduction.md
+++ b/src/guides/use-iapp/introduction.md
@@ -81,8 +81,8 @@ protected throughout the computation.
 ## Getting Started
 
 Ready to start using iApps? Check out our
-[Getting Started Guide](./getting-started.md) to learn how to find, execute, and
-interact with iApps on the iExec network.
+[Getting Started Guide](/guides/use-iapp/getting-started) to learn how to find,
+execute, and interact with iApps on the iExec network.
 
 <script setup>
 import TokenSymbol from '@/components/TokenSymbol.vue'
diff --git a/src/guides/use-iapp/use-iapp-with-protected-data.md b/src/guides/use-iapp/use-iapp-with-protected-data.md
index 1b7ea5d9..3a501a1b 100644
--- a/src/guides/use-iapp/use-iapp-with-protected-data.md
+++ b/src/guides/use-iapp/use-iapp-with-protected-data.md
@@ -455,6 +455,8 @@ const taskResult = await dataProtectorCore.getResultFromCompletedTask({
 
 Now that you understand how to use iApps with protected data:
 
-- Learn about [Different Ways to Execute](./different-ways-to-execute.md) iApps
-- Explore [How to Pay for Executions](./how-to-pay-executions.md)
-- Check out our [Add Inputs to Execution](./add-inputs-to-execution.md) guide
+- Learn about
+  [Different Ways to Execute](/guides/use-iapp/different-ways-to-execute) iApps
+- Explore [How to Pay for Executions](/guides/use-iapp/how-to-pay-executions)
+- Check out our
+  [Add Inputs to Execution](/guides/use-iapp/add-inputs-to-execution) guide
diff --git a/src/modules/helloWorld/CouponCode.vue b/src/modules/helloWorld/CouponCode.vue
index db55dc4d..20e2549a 100644
--- a/src/modules/helloWorld/CouponCode.vue
+++ b/src/modules/helloWorld/CouponCode.vue
@@ -60,7 +60,7 @@
 <script setup>
 import { ref, computed } from 'vue';
 import ReownButton from './ReownButton.vue';
-import { useWalletConnection } from '../../hooks/useWalletConnection.vue';
+import { useWalletConnection } from '@/hooks/useWalletConnection.vue';
 
 const { userAddress } = useWalletConnection();
 
diff --git a/src/modules/helloWorld/GrantAccess.vue b/src/modules/helloWorld/GrantAccess.vue
index 5b7fae16..807294a0 100644
--- a/src/modules/helloWorld/GrantAccess.vue
+++ b/src/modules/helloWorld/GrantAccess.vue
@@ -110,7 +110,7 @@ import { IExecDataProtectorCore } from '@iexec/dataprotector';
 import Button from '@/components/ui/Button.vue';
 import ReownButton from './ReownButton.vue';
 import { useAccount } from '@wagmi/vue';
-import { useWalletConnection } from '../../hooks/useWalletConnection.vue';
+import { useWalletConnection } from '@/hooks/useWalletConnection.vue';
 import useUserStore from '@/stores/useUser.store';
 
 const { connector } = useAccount();
diff --git a/src/modules/helloWorld/ProtectData.vue b/src/modules/helloWorld/ProtectData.vue
index d57bcc63..d442bb1d 100644
--- a/src/modules/helloWorld/ProtectData.vue
+++ b/src/modules/helloWorld/ProtectData.vue
@@ -115,7 +115,7 @@ import { IExecDataProtectorCore } from '@iexec/dataprotector';
 import Button from '@/components/ui/Button.vue';
 import ReownButton from './ReownButton.vue';
 import { useAccount } from '@wagmi/vue';
-import { useWalletConnection } from '../../hooks/useWalletConnection.vue';
+import { useWalletConnection } from '@/hooks/useWalletConnection.vue';
 import useUserStore from '@/stores/useUser.store';
 
 const { connector } = useAccount();
diff --git a/src/references/dataProtector/advanced/advanced-configuration.md b/src/references/dataProtector/advanced/advanced-configuration.md
index d5b427b8..b6cbcde9 100644
--- a/src/references/dataProtector/advanced/advanced-configuration.md
+++ b/src/references/dataProtector/advanced/advanced-configuration.md
@@ -13,7 +13,8 @@ parameters. As these parameters are very specific, they are not needed for a
 standard usage of `@iexec/dataprotector`.
 
 Similarly, not all functionalities need to be instantiated at once in the SDK,
-as described in the [getting started](../getting-started.md#instantiate-sdk)
+as described in the
+[getting started](/references/dataProtector/getting-started#instantiate-sdk)
 section.
 
 ## Parameters
diff --git a/src/references/dataProtector/advanced/apps-whitelist.md b/src/references/dataProtector/advanced/apps-whitelist.md
index e88ed232..2f22aab4 100644
--- a/src/references/dataProtector/advanced/apps-whitelist.md
+++ b/src/references/dataProtector/advanced/apps-whitelist.md
@@ -21,13 +21,13 @@ The story goes as follow:
 
 1. The collection owner adds a protected data to a collection. When doing so,
    they need to set an `addOnlyAppWhitelist` parameter (see
-   [here](../dataProtectorSharing/collection/addToCollection.md#addonlyappwhitelist)).
+   [here](/references/dataProtector/dataProtectorSharing/collection/addToCollection#addonlyappwhitelist)).
    This parameter is the address of a whitelist smart contract that contains
    applications allowed to consume the protected data.
 
 2. When a user wants to consume the protected data, they need to provide the
    address of the application they want to use to consume the data (See
-   [consumeProtectedData](../dataProtectorSharing/consume/consumeProtectedData.md#app-param)
+   [consumeProtectedData](/references/dataProtector/dataProtectorSharing/consume/consumeProtectedData#app-param)
    &nbsp;`app` parameter). This chosen application must be in the whitelist
    defined by the collection owner.
 
diff --git a/src/references/dataProtector/advanced/apps-whitelist/addAppToAddOnlyAppWhitelist.md b/src/references/dataProtector/advanced/apps-whitelist/addAppToAddOnlyAppWhitelist.md
index 433288f3..db370135 100644
--- a/src/references/dataProtector/advanced/apps-whitelist/addAppToAddOnlyAppWhitelist.md
+++ b/src/references/dataProtector/advanced/apps-whitelist/addAppToAddOnlyAppWhitelist.md
@@ -95,7 +95,8 @@ const isAddedToAddAppToAddOnlyAppWhitelist =
 import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
-See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+See
+[`SuccessWithTransactionHash`](/references/dataProtector/types#successwithtransactionhash)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
diff --git a/src/references/dataProtector/dataProtectorCore/getGrantedAccess.md b/src/references/dataProtector/dataProtectorCore/getGrantedAccess.md
index a2755b91..08679c58 100644
--- a/src/references/dataProtector/dataProtectorCore/getGrantedAccess.md
+++ b/src/references/dataProtector/dataProtectorCore/getGrantedAccess.md
@@ -86,12 +86,12 @@ const listGrantedAccess = await dataProtectorCore.getGrantedAccess({
 ::: tip
 
 If you specified an application whitelist when using
-[`grantAccess`](./grantAccess.md), you must specify that same whitelist address
-when using this filtering option. The `getGrantedAccess` method does not check
-against whitelist smart contracts when aggregating results. If you granted
-authorization to a whitelist but specify an application address for the
-`authorizedApp` parameter, you will not receive any results unless you _also_
-explicitly granted access to that application address.
+[`grantAccess`](/references/dataProtector/dataProtectorCore/grantAccess), you
+must specify that same whitelist address when using this filtering option. The
+`getGrantedAccess` method does not check against whitelist smart contracts when
+aggregating results. If you granted authorization to a whitelist but specify an
+application address for the `authorizedApp` parameter, you will not receive any
+results unless you _also_ explicitly granted access to that application address.
 
 :::
 
@@ -216,7 +216,7 @@ smaller than the page size.
 
 **Type:** GrantedAccess
 
-See [`GrantedAccess`](../types.md#grantedaccess)
+See [`GrantedAccess`](/references/dataProtector/types#grantedaccess)
 
 <script setup>
 import OptionalBadge from '@/components/OptionalBadge.vue'
diff --git a/src/references/dataProtector/dataProtectorCore/getProtectedData.md b/src/references/dataProtector/dataProtectorCore/getProtectedData.md
index b8578125..ae9106d0 100644
--- a/src/references/dataProtector/dataProtectorCore/getProtectedData.md
+++ b/src/references/dataProtector/dataProtectorCore/getProtectedData.md
@@ -99,7 +99,8 @@ const listProtectedData = await dataProtectorCore.getProtectedData({
 ```
 <!-- prettier-ignore-end -->
 
-Available types are listed [here](./protectData#schema).
+Available types are listed
+[here](/references/dataProtector/dataProtectorCore/protectData#schema).
 
 ### owner <OptionalBadge />
 
@@ -190,7 +191,7 @@ const listProtectedData = await dataProtectorCore.getProtectedData({
 import { type ProtectedData } from '@iexec/dataprotector';
 ```
 
-See [`ProtectedData`](../types.md#protecteddata)
+See [`ProtectedData`](/references/dataProtector/types#protecteddata)
 
 <script setup>
 import OptionalBadge from '@/components/OptionalBadge.vue'
diff --git a/src/references/dataProtector/dataProtectorCore/grantAccess.md b/src/references/dataProtector/dataProtectorCore/grantAccess.md
index fc8d2fd1..e83d8eb4 100644
--- a/src/references/dataProtector/dataProtectorCore/grantAccess.md
+++ b/src/references/dataProtector/dataProtectorCore/grantAccess.md
@@ -249,7 +249,7 @@ import { type GrantedAccess } from '@iexec/dataprotector';
 The result of this method confirms the new access grant. It consists of a JSON
 `grantedAccess` object.
 
-[`GrantedAccess`](../types.md#grantedaccess)
+[`GrantedAccess`](/references/dataProtector/types#grantedaccess)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
diff --git a/src/references/dataProtector/dataProtectorCore/processProtectedData.md b/src/references/dataProtector/dataProtectorCore/processProtectedData.md
index c0f0f132..a6c7316d 100644
--- a/src/references/dataProtector/dataProtectorCore/processProtectedData.md
+++ b/src/references/dataProtector/dataProtectorCore/processProtectedData.md
@@ -14,7 +14,8 @@ application.
 > [!IMPORTANT]
 >
 > You must ensure this application has authorization to use the `protectedData`.
-> You may grant this permission using the [`grantAccess`](./grantAccess.md)
+> You may grant this permission using the
+> [`grantAccess`](/references/dataProtector/dataProtectorCore/grantAccess)
 > method.
 
 ## Usage
@@ -469,7 +470,7 @@ Bellecour side chain. You can monitor task execution using the
 ::: tip
 
 The
-[getResultFromCompletedTask()](../dataProtectorCore/getResultFromCompletedTask.md)
+[getResultFromCompletedTask()](/references/dataProtector/dataProtectorCore/getResultFromCompletedTask)
 function allows you to retrieve the result of a completed task using its
 `taskId`.
 
diff --git a/src/references/dataProtector/dataProtectorCore/revokeAllAccess.md b/src/references/dataProtector/dataProtectorCore/revokeAllAccess.md
index 3275ea34..55e4977d 100644
--- a/src/references/dataProtector/dataProtectorCore/revokeAllAccess.md
+++ b/src/references/dataProtector/dataProtectorCore/revokeAllAccess.md
@@ -140,7 +140,7 @@ Once with `isDone: false`, and then with `isDone: true`
 import { type RevokedAccess } from '@iexec/dataprotector';
 ```
 
-[`RevokedAccess[]`](../types.md#revokedaccess)
+[`RevokedAccess[]`](/references/dataProtector/types#revokedaccess)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
diff --git a/src/references/dataProtector/dataProtectorCore/revokeOneAccess.md b/src/references/dataProtector/dataProtectorCore/revokeOneAccess.md
index 5ff6909a..c460c2ce 100644
--- a/src/references/dataProtector/dataProtectorCore/revokeOneAccess.md
+++ b/src/references/dataProtector/dataProtectorCore/revokeOneAccess.md
@@ -20,7 +20,8 @@ As this will generate a blockchain transaction, expect it to take a least 5sec
 
 The `revokeOneAccess` method requires a `grantedAccess` object as an input
 parameter. This object is retrieved from the
-[`getGrantedAccess`](./getGrantedAccess.md) method.
+[`getGrantedAccess`](/references/dataProtector/dataProtectorCore/getGrantedAccess)
+method.
 
 ```ts twoslash
 import { IExecDataProtectorCore, getWeb3Provider } from '@iexec/dataprotector';
@@ -88,7 +89,7 @@ data).
 import { type RevokedAccess } from '@iexec/dataprotector';
 ```
 
-[`RevokedAccess`](../types.md#revokedaccess)
+[`RevokedAccess`](/references/dataProtector/types#revokedaccess)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
diff --git a/src/references/dataProtector/dataProtectorSharing.md b/src/references/dataProtector/dataProtectorSharing.md
index 293a92fa..25992d4a 100644
--- a/src/references/dataProtector/dataProtectorSharing.md
+++ b/src/references/dataProtector/dataProtectorSharing.md
@@ -31,7 +31,7 @@ is bundled by the user into one or more collections. Within the collection, the
 user may specify different sharing options for different pieces of data. This
 illustration shows the hierarchy of a Data Sharing smart contract:
 
-![Data Sharing smart contract](./dataProtectorSharing/data-sharing-sc.png)
+![Data Sharing smart contract](/references/dataProtector/dataProtectorSharing/data-sharing-sc.png)
 
 The Data Sharing smart contract enforces governance over the user's protected
 data based on their desired distribution choices. The user has complete control
diff --git a/src/references/dataProtector/dataProtectorSharing/collection/addToCollection.md b/src/references/dataProtector/dataProtectorSharing/collection/addToCollection.md
index 53a593ff..d590d522 100644
--- a/src/references/dataProtector/dataProtectorSharing/collection/addToCollection.md
+++ b/src/references/dataProtector/dataProtectorSharing/collection/addToCollection.md
@@ -117,7 +117,7 @@ For this `addOnlyAppWhitelist`, you are free to use
 `0x256bcd881c33bdf9df952f2a0148f27d439f2e64`.
 
 For more details on how to create and manage appsWhitelist, see
-[Apps whitelist](../../advanced/apps-whitelist).
+[Apps whitelist](/references/dataProtector/advanced/apps-whitelist).
 
 :::
 
@@ -163,7 +163,8 @@ Once with `isDone: false`, and then with `isDone: true`
 import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
-See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+See
+[`SuccessWithTransactionHash`](/references/dataProtector/types#successwithtransactionhash)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
diff --git a/src/references/dataProtector/dataProtectorSharing/collection/removeCollection.md b/src/references/dataProtector/dataProtectorSharing/collection/removeCollection.md
index bccc0738..b84d719f 100644
--- a/src/references/dataProtector/dataProtectorSharing/collection/removeCollection.md
+++ b/src/references/dataProtector/dataProtectorSharing/collection/removeCollection.md
@@ -33,7 +33,7 @@ const { txHash } = await dataProtectorSharing.removeCollection({
 
 - You must be the owner of the collection.
 - There should be no protected data in the collection. See
-  [`removeProtectedDataFromCollection`](./removeProtectedDataFromCollection.md).
+  [`removeProtectedDataFromCollection`](/references/dataProtector/dataProtectorSharing/collection/removeProtectedDataFromCollection).
 
 ## Parameters
 
@@ -67,7 +67,8 @@ const { txHash } = await dataProtectorSharing.removeCollection({
 import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
-See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+See
+[`SuccessWithTransactionHash`](/references/dataProtector/types#successwithtransactionhash)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
diff --git a/src/references/dataProtector/dataProtectorSharing/collection/removeProtectedDataFromCollection.md b/src/references/dataProtector/dataProtectorSharing/collection/removeProtectedDataFromCollection.md
index 087a9a76..f33e24f6 100644
--- a/src/references/dataProtector/dataProtectorSharing/collection/removeProtectedDataFromCollection.md
+++ b/src/references/dataProtector/dataProtectorSharing/collection/removeProtectedDataFromCollection.md
@@ -73,7 +73,8 @@ const { txHash } = await dataProtectorSharing.removeProtectedDataFromCollection(
 import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
-See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+See
+[`SuccessWithTransactionHash`](/references/dataProtector/types#successwithtransactionhash)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
diff --git a/src/references/dataProtector/dataProtectorSharing/consume/consumeProtectedData.md b/src/references/dataProtector/dataProtectorSharing/consume/consumeProtectedData.md
index 361bdc76..7467cbce 100644
--- a/src/references/dataProtector/dataProtectorSharing/consume/consumeProtectedData.md
+++ b/src/references/dataProtector/dataProtectorSharing/consume/consumeProtectedData.md
@@ -113,7 +113,8 @@ For this `app` parameter you can use the "Protected data delivery TEE dApp":
 </div>Please note: This application can only be used <strong>within the
 dataProtectorSharing module</strong>, as it is owned by the DataProtector Sharing smart contract.
 
-For more details, see [Apps whitelist](../../advanced/apps-whitelist).
+For more details, see
+[Apps whitelist](/references/dataProtector/advanced/apps-whitelist).
 
 :::
 
@@ -122,7 +123,8 @@ For more details, see [Apps whitelist](../../advanced/apps-whitelist).
 If you want to provide **your own TEE dApp**, you will need to create a
 whitelist that contains your app.
 
-For more details, see [Apps whitelist](../../advanced/apps-whitelist).
+For more details, see
+[Apps whitelist](/references/dataProtector/advanced/apps-whitelist).
 
 :::
 
diff --git a/src/references/dataProtector/dataProtectorSharing/renting/removeProtectedDataFromRenting.md b/src/references/dataProtector/dataProtectorSharing/renting/removeProtectedDataFromRenting.md
index a5230b6c..92e8e7c1 100644
--- a/src/references/dataProtector/dataProtectorSharing/renting/removeProtectedDataFromRenting.md
+++ b/src/references/dataProtector/dataProtectorSharing/renting/removeProtectedDataFromRenting.md
@@ -63,7 +63,8 @@ const notForRentingAnymoreResult =
 import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
-See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+See
+[`SuccessWithTransactionHash`](/references/dataProtector/types#successwithtransactionhash)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
diff --git a/src/references/dataProtector/dataProtectorSharing/renting/rentProtectedData.md b/src/references/dataProtector/dataProtectorSharing/renting/rentProtectedData.md
index 7f8aa774..a599853b 100644
--- a/src/references/dataProtector/dataProtectorSharing/renting/rentProtectedData.md
+++ b/src/references/dataProtector/dataProtectorSharing/renting/rentProtectedData.md
@@ -95,7 +95,7 @@ const rentResult = await dataProtectorSharing.rentProtectedData({
 ::: tip
 
 To get the renting price of the given protected data, you can use
-[getProtectedDataPricingParams](../read/getProtectedDataPricingParams.md).
+[getProtectedDataPricingParams](/references/dataProtector/dataProtectorSharing/read/getProtectedDataPricingParams).
 
 :::
 
@@ -126,7 +126,7 @@ const rentResult = await dataProtectorSharing.rentProtectedData({
 ::: tip
 
 To get the renting duration of the given protected data, you can use
-[getProtectedDataPricingParams](../read/getProtectedDataPricingParams.md).
+[getProtectedDataPricingParams](/references/dataProtector/dataProtectorSharing/read/getProtectedDataPricingParams).
 
 :::
 
@@ -136,7 +136,8 @@ To get the renting duration of the given protected data, you can use
 import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
-See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+See
+[`SuccessWithTransactionHash`](/references/dataProtector/types#successwithtransactionhash)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
diff --git a/src/references/dataProtector/dataProtectorSharing/renting/setProtectedDataRentingParams.md b/src/references/dataProtector/dataProtectorSharing/renting/setProtectedDataRentingParams.md
index bf0ff910..d66a297c 100644
--- a/src/references/dataProtector/dataProtectorSharing/renting/setProtectedDataRentingParams.md
+++ b/src/references/dataProtector/dataProtectorSharing/renting/setProtectedDataRentingParams.md
@@ -114,7 +114,8 @@ const setForRentingResult =
 import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
-See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+See
+[`SuccessWithTransactionHash`](/references/dataProtector/types#successwithtransactionhash)
 
 <script setup>
 import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
diff --git a/src/references/dataProtector/dataProtectorSharing/renting/setProtectedDataToRenting.md b/src/references/dataProtector/dataProtectorSharing/renting/setProtectedDataToRenting.md
index 03049683..c9033977 100644
--- a/src/references/dataProtector/dataProtectorSharing/renting/setProtectedDataToRenting.md
+++ b/src/references/dataProtector/dataProtectorSharing/renting/setProtectedDataToRenting.md
@@ -115,7 +115,8 @@ const setForRentingResult =
 import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
-See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+See
+[`SuccessWithTransactionHash`](/references/dataProtector/types#successwithtransactionhash)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
diff --git a/src/references/dataProtector/dataProtectorSharing/selling/buyProtectedData.md b/src/references/dataProtector/dataProtectorSharing/selling/buyProtectedData.md
index b00fcdd9..9969ce89 100644
--- a/src/references/dataProtector/dataProtectorSharing/selling/buyProtectedData.md
+++ b/src/references/dataProtector/dataProtectorSharing/selling/buyProtectedData.md
@@ -151,7 +151,7 @@ purpose of Content Creator usecase-demo. This `addOnlyAppWhitelist` is managed
 by iExec.
 
 For more details on how to create and manage appsWhitelist, see
-[Apps whitelist](../../advanced/apps-whitelist).
+[Apps whitelist](/references/dataProtector/advanced/apps-whitelist).
 
 :::
 
@@ -161,7 +161,8 @@ For more details on how to create and manage appsWhitelist, see
 import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
-See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+See
+[`SuccessWithTransactionHash`](/references/dataProtector/types#successwithtransactionhash)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
diff --git a/src/references/dataProtector/dataProtectorSharing/selling/removeProtectedDataForSale.md b/src/references/dataProtector/dataProtectorSharing/selling/removeProtectedDataForSale.md
index 41d1bf46..6044f308 100644
--- a/src/references/dataProtector/dataProtectorSharing/selling/removeProtectedDataForSale.md
+++ b/src/references/dataProtector/dataProtectorSharing/selling/removeProtectedDataForSale.md
@@ -59,7 +59,8 @@ const notForSaleAnymoreResult =
 import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
-See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+See
+[`SuccessWithTransactionHash`](/references/dataProtector/types#successwithtransactionhash)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
diff --git a/src/references/dataProtector/dataProtectorSharing/selling/setProtectedDataForSale.md b/src/references/dataProtector/dataProtectorSharing/selling/setProtectedDataForSale.md
index d6cd8236..2d642382 100644
--- a/src/references/dataProtector/dataProtectorSharing/selling/setProtectedDataForSale.md
+++ b/src/references/dataProtector/dataProtectorSharing/selling/setProtectedDataForSale.md
@@ -86,7 +86,8 @@ const setForSaleResult = await dataProtectorSharing.setProtectedDataForSale({
 import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
-See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+See
+[`SuccessWithTransactionHash`](/references/dataProtector/types#successwithtransactionhash)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
diff --git a/src/references/dataProtector/dataProtectorSharing/subscription/removeProtectedDataFromSubscription.md b/src/references/dataProtector/dataProtectorSharing/subscription/removeProtectedDataFromSubscription.md
index 92105e53..fa54fcc2 100644
--- a/src/references/dataProtector/dataProtectorSharing/subscription/removeProtectedDataFromSubscription.md
+++ b/src/references/dataProtector/dataProtectorSharing/subscription/removeProtectedDataFromSubscription.md
@@ -74,7 +74,8 @@ const { txHash } =
 import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
-See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+See
+[`SuccessWithTransactionHash`](/references/dataProtector/types#successwithtransactionhash)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
diff --git a/src/references/dataProtector/dataProtectorSharing/subscription/setProtectedDataToSubscription.md b/src/references/dataProtector/dataProtectorSharing/subscription/setProtectedDataToSubscription.md
index c4d905fe..f35b16a6 100644
--- a/src/references/dataProtector/dataProtectorSharing/subscription/setProtectedDataToSubscription.md
+++ b/src/references/dataProtector/dataProtectorSharing/subscription/setProtectedDataToSubscription.md
@@ -63,7 +63,8 @@ const setToSubscriptionResult =
 import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
-See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+See
+[`SuccessWithTransactionHash`](/references/dataProtector/types#successwithtransactionhash)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
diff --git a/src/references/dataProtector/dataProtectorSharing/subscription/setSubscriptionParams.md b/src/references/dataProtector/dataProtectorSharing/subscription/setSubscriptionParams.md
index 549e06ab..d31e44a2 100644
--- a/src/references/dataProtector/dataProtectorSharing/subscription/setSubscriptionParams.md
+++ b/src/references/dataProtector/dataProtectorSharing/subscription/setSubscriptionParams.md
@@ -111,7 +111,8 @@ const setSubscriptionParamsResult =
 import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
-See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+See
+[`SuccessWithTransactionHash`](/references/dataProtector/types#successwithtransactionhash)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
diff --git a/src/references/dataProtector/dataProtectorSharing/subscription/subscribeToCollection.md b/src/references/dataProtector/dataProtectorSharing/subscription/subscribeToCollection.md
index 78734975..5d51a636 100644
--- a/src/references/dataProtector/dataProtectorSharing/subscription/subscribeToCollection.md
+++ b/src/references/dataProtector/dataProtectorSharing/subscription/subscribeToCollection.md
@@ -132,7 +132,8 @@ const { txHash } = await dataProtectorSharing.subscribeToCollection({
 import { type SuccessWithTransactionHash } from '@iexec/dataprotector';
 ```
 
-See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
+See
+[`SuccessWithTransactionHash`](/references/dataProtector/types#successwithtransactionhash)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
diff --git a/src/references/dataProtector/getting-started.md b/src/references/dataProtector/getting-started.md
index 68e07cb2..13ff000d 100644
--- a/src/references/dataProtector/getting-started.md
+++ b/src/references/dataProtector/getting-started.md
@@ -195,7 +195,7 @@ const dataProtectorSharing = dataProtector.sharing;
 #### Advanced Configuration
 
 To add optional parameters, see
-[advanced configuration](./advanced/advanced-configuration.md).
+[advanced configuration](/references/dataProtector/advanced/advanced-configuration).
 
 ::: info
 
@@ -205,9 +205,9 @@ protected data in the experimental **intel TDX** environment.
 
 For more details see:
 
-- [configure DataProtector TDX](./advanced/advanced-configuration.md#iexecoptions)
-- [create TDX protected data](./dataProtectorCore/protectData.md#usage)
-- [process TDX protected data](./dataProtectorCore/processProtectedData.md#workerpool)
+- [configure DataProtector TDX](/references/dataProtector/advanced/advanced-configuration#iexecoptions)
+- [create TDX protected data](/references/dataProtector/dataProtectorCore/protectData#usage)
+- [process TDX protected data](/references/dataProtector/dataProtectorCore/processProtectedData#workerpool)
 
 ⚠️ Keep in mind: TDX mode is experimental and can be subject to instabilities or
 discontinuity.
diff --git a/src/references/dataProtector/types.md b/src/references/dataProtector/types.md
index 3bc83212..e586d99a 100644
--- a/src/references/dataProtector/types.md
+++ b/src/references/dataProtector/types.md
@@ -73,8 +73,9 @@ Types in DataProtector.
 ### schema: <span class="text-yellow">`DataSchema`</span>
 
 - Data schema for the protected data as defined when the protected data was
-  created (see [protectedData](./dataProtectorCore/protectData.md)). `schema`
-  provides a structured representation of the protected data format and
+  created (see
+  [protectedData](/references/dataProtector/dataProtectorCore/protectData)).
+  `schema` provides a structured representation of the protected data format and
   attributes. This field plays a crucial role in understanding and interpreting
   the underlying structure of the sensitive information.
 
diff --git a/src/references/web3telegram.md b/src/references/web3telegram.md
index 10094200..06ea8929 100644
--- a/src/references/web3telegram.md
+++ b/src/references/web3telegram.md
@@ -19,7 +19,7 @@ telegram chat ID recipients through use of Ethereum addresses.
 The telegram chat ID address is stored as a `protectedData` entity using
 [iExec Data Protector](/references/dataProtector). Through this mechanism, users
 have complete control over which applications may use their
-[chat ID](./web3telegram/integration-guide.md#_1-get-your-users-to-retrieve-their-chat-id)
+[chat ID](/references/web3telegram/integration-guide#_1-get-your-users-to-retrieve-their-chat-id)
 for sending communications.
 
 Sending a user a message, therefore, requires knowledge of the Ethereum address
diff --git a/src/utils/injected-wallet-provider/injected-wallet-provider.ts b/src/utils/injected-wallet-provider/injected-wallet-provider.ts
index 0a657294..f6b6c637 100644
--- a/src/utils/injected-wallet-provider/injected-wallet-provider.ts
+++ b/src/utils/injected-wallet-provider/injected-wallet-provider.ts
@@ -3,7 +3,7 @@ import {
   EIP6963AnnounceProviderEvent,
   EIP6963ProviderDetail,
   EIP6963RequestProviderEvent,
-} from './types';
+} from '@/utils/injected-wallet-provider/types';
 
 // This class extends EventEmitter to be able to emit events and give our DApp an interface to subscribe to
 export class InjectedWalletProvider extends EventEmitter {
diff --git a/src/utils/wagmiConfig.ts b/src/utils/wagmiConfig.ts
index c4fd8918..c78f72a4 100644
--- a/src/utils/wagmiConfig.ts
+++ b/src/utils/wagmiConfig.ts
@@ -2,9 +2,9 @@ import { createAppKit } from '@reown/appkit/vue';
 import { WagmiAdapter } from '@reown/appkit-adapter-wagmi';
 import { http, CreateConnectorFn } from '@wagmi/vue';
 import { injected } from '@wagmi/vue/connectors';
-import wagmiNetworks from './wagmiNetworks.ts';
-import { InjectedWalletProvider } from './injected-wallet-provider/injected-wallet-provider.ts';
-import { EIP6963ProviderDetail } from './injected-wallet-provider/types.ts';
+import wagmiNetworks from '@/utils/wagmiNetworks';
+import { InjectedWalletProvider } from '@/utils/injected-wallet-provider/injected-wallet-provider';
+import { EIP6963ProviderDetail } from '@/utils/injected-wallet-provider/types';
 import { AppKitNetwork } from '@reown/appkit/networks';
 
 export const projectId = import.meta.env.VITE_REOWN_PROJECT_ID as string;

From d79d99971999869aec47e81a63c2b2b700ece783 Mon Sep 17 00:00:00 2001
From: Le-Caignec <robinlecaignec@yahoo.fr>
Date: Sun, 17 Aug 2025 16:56:15 +0200
Subject: [PATCH 14/27] fix: update default chain in ChainSelector to Arbitrum
 and improve documentation layout in helloWorld

---
 src/components/ChainSelector.vue |  4 ++--
 src/get-started/helloWorld.md    | 18 +++++++-----------
 2 files changed, 9 insertions(+), 13 deletions(-)

diff --git a/src/components/ChainSelector.vue b/src/components/ChainSelector.vue
index 1a903718..6be13e7c 100644
--- a/src/components/ChainSelector.vue
+++ b/src/components/ChainSelector.vue
@@ -77,8 +77,8 @@ if (!userStore.chainId) {
       userStore.setSelectedChain(walletChain);
     }
   } else {
-    // Otherwise, use Bellecour as default
-    const defaultChain = getChainById(0x86); // Bellecour
+    // Otherwise, use Arbitrum as default
+    const defaultChain = getChainById(42161); // Arbitrum
     if (defaultChain) {
       userStore.setSelectedChain(defaultChain);
     }
diff --git a/src/get-started/helloWorld.md b/src/get-started/helloWorld.md
index 4b06eb3b..3b2fc8f4 100644
--- a/src/get-started/helloWorld.md
+++ b/src/get-started/helloWorld.md
@@ -14,13 +14,9 @@ import ChainSelector from '@/components/ChainSelector.vue'
 
 > Reading time 🕒 2 mins
 
-<div class="mb-6 p-4 bg-[var(--vp-c-bg-soft)] rounded-lg border border-[var(--vp-c-divider)]">
-  <div class="flex items-center gap-3 mb-3">
-    <span class="text-lg">🌐</span>
-    <h3 class="m-0 text-lg font-medium">Select Your Network</h3>
-  </div>
-  <div class="flex items-center gap-3">
-    <span class="text-sm font-medium">Network:</span>
+<div class="mb-0 p-6 bg-[var(--vp-c-bg-soft)] rounded-lg border border-[var(--vp-c-divider)]">
+  <div class="flex">
+    <h3 class="m-0! py-2 text-lg font-medium">🌐 Select Your Network :</h3>
     <ChainSelector />
   </div>
 </div>
@@ -100,21 +96,21 @@ Before you begin, make sure you have:
 <div class="flex flex-col gap-2 my-4 pl-0">
   <div class="flex items-center gap-4 text-left">
     <div class="flex items-center gap-1 flex-1 text-sm font-medium">
-      🦊 Ethereum Wallet 
+      🦊 Ethereum Wallet
       <InfoIcon tooltip="Required to interact with iExec sidechain Bellecour features, manage your data access permissions, and handle transactions on the iExec platform" />
     </div>
     <a target="_blank" href="https://chromewebstore.google.com/detail/metamask/nkbihfbeogaeaoehlefnkodbefgpgknn" class="no-underline! text-sm ml-auto hover:underline!">Metamask Download →</a>
   </div>
   <div class="flex items-center gap-4 text-left">
     <div class="flex items-center gap-1 flex-1 text-sm font-medium">
-      📦 Node.js v20+ 
+      📦 Node.js v20+
       <InfoIcon tooltip="Required runtime environment for running JavaScript code and managing project dependencies" />
     </div>
     <a target="_blank" href="https://nodejs.org/en/" class="no-underline! text-sm ml-auto hover:underline!">Download →</a>
   </div>
    <div class="flex items-center gap-4 text-left">
     <div class="flex items-center gap-1 flex-1 text-sm font-medium">
-      🐳 Docker installed 
+      🐳 Docker installed
       <InfoIcon tooltip="Docker is essential for creating isolated containers that package your iExec applications with all dependencies. This ensures consistent and secure execution across different environments, especially in TEEs (Trusted Execution Environments)" />
     </div>
     <a target="_blank" href="https://docker.com/" class="no-underline! text-sm ml-auto hover:underline!">Download →</a>
@@ -122,7 +118,7 @@ Before you begin, make sure you have:
   
   <div class="flex items-center gap-4 text-left">
     <div class="flex items-center gap-1 flex-1 text-sm font-medium">
-      🐳 DockerHub Account 
+      🐳 DockerHub Account
       <InfoIcon tooltip="Needed to publish and manage your iExec applications in containers for secure deployment" />
     </div>
     <a target="_blank" href="https://hub.docker.com/" class="no-underline! text-sm ml-auto hover:underline!">Sign Up →</a>

From cbec0c3d93db1012b26d0b06cbfb353ff57fb5d6 Mon Sep 17 00:00:00 2001
From: Le-Caignec <robinlecaignec@yahoo.fr>
Date: Sun, 17 Aug 2025 20:37:12 +0200
Subject: [PATCH 15/27] fix: tw feedbacks

---
 .vitepress/sidebar.ts                         |  2 +-
 src/get-started/develop-with-ai.md            | 12 ++---
 src/get-started/helloWorld.md                 |  2 +-
 src/get-started/helloWorld/1-overview.md      |  8 +--
 src/get-started/helloWorld/2-protectData.md   |  2 +-
 src/get-started/{ => overview}/rlc.md         | 43 +++++++++++----
 src/get-started/overview/what-is-iapp.md      | 38 +++++++------
 .../overview/what-is-protected-data.md        | 13 +++--
 src/get-started/quick-start.md                |  2 +-
 src/get-started/welcome.md                    | 33 ++++++++----
 src/guides/build-iapp/build-&-deploy.md       |  4 +-
 src/guides/build-iapp/debugging.md            |  2 +-
 .../manage-data/monetize-protected-data.md    |  7 ++-
 src/guides/use-iapp/getting-started.md        |  3 +-
 .../how-to-pay/how-to-pay-for-web3mail.md     |  4 +-
 .../how-to-pay/how-to-pay-for-web3telegram.md |  4 +-
 src/index.md                                  | 16 +++---
 .../dataProtector/getting-started.md          |  5 +-
 src/references/iapp-generator.md              | 54 +++++++++----------
 .../iapp-generator/building-your-iexec-app.md |  2 +-
 src/references/iapp-generator/deserializer.md |  4 +-
 21 files changed, 153 insertions(+), 107 deletions(-)
 rename src/get-started/{ => overview}/rlc.md (75%)

diff --git a/.vitepress/sidebar.ts b/.vitepress/sidebar.ts
index 3cc495dc..44c230ce 100644
--- a/.vitepress/sidebar.ts
+++ b/.vitepress/sidebar.ts
@@ -73,7 +73,7 @@ export function getSidebar() {
           },
           {
             text: '🪙 RLC Token',
-            link: '/get-started/rlc',
+            link: '/get-started/overview/rlc',
           },
         ],
       },
diff --git a/src/get-started/develop-with-ai.md b/src/get-started/develop-with-ai.md
index faecb310..210a7f59 100644
--- a/src/get-started/develop-with-ai.md
+++ b/src/get-started/develop-with-ai.md
@@ -7,7 +7,7 @@ description:
 
 # 🤖 Develop with AI
 
-Building privacy-first applications with iExec can be accelerated using
+AI tools accelerate building privacy-first applications with iExec using
 AI-powered development tools. This guide covers how to effectively use AI
 assistants while maintaining security best practices.
 
@@ -23,12 +23,12 @@ provide:
 
 ## 🎨 Vibe Coding Integration
 
-Vibe coding is a modern way to build applications by describing what you want in
-plain language. An AI assistant (like Cursor or ChatGPT) then generates code
-based on your description.
+Vibe coding lets you build applications by describing what you want in plain
+language. An AI assistant (like Cursor or ChatGPT) then generates code based on
+your description.
 
-It's fast, creative, and helps you prototype ideas quickly. Even if you're not a
-technical expert you can:
+It's fast, creative, and helps you prototype ideas quickly. Even non-technical
+users can:
 
 - Write a prompt like: "I want to create a form able to protect my data with
   DataProtector"
diff --git a/src/get-started/helloWorld.md b/src/get-started/helloWorld.md
index 3b2fc8f4..a4c61083 100644
--- a/src/get-started/helloWorld.md
+++ b/src/get-started/helloWorld.md
@@ -97,7 +97,7 @@ Before you begin, make sure you have:
   <div class="flex items-center gap-4 text-left">
     <div class="flex items-center gap-1 flex-1 text-sm font-medium">
       🦊 Ethereum Wallet
-      <InfoIcon tooltip="Required to interact with iExec sidechain Bellecour features, manage your data access permissions, and handle transactions on the iExec platform" />
+      <InfoIcon tooltip="Required to interact with iExec protocol, manage your data access permissions, and handle transactions on the iExec platform" />
     </div>
     <a target="_blank" href="https://chromewebstore.google.com/detail/metamask/nkbihfbeogaeaoehlefnkodbefgpgknn" class="no-underline! text-sm ml-auto hover:underline!">Metamask Download →</a>
   </div>
diff --git a/src/get-started/helloWorld/1-overview.md b/src/get-started/helloWorld/1-overview.md
index d416ccc7..8f1fb28c 100644
--- a/src/get-started/helloWorld/1-overview.md
+++ b/src/get-started/helloWorld/1-overview.md
@@ -66,8 +66,8 @@ description:
 
 ## 👷 How do we Solve it?
 
-Unlike traditional security solutions, iExec protects your data throughout its
-entire lifecycle, during storage, transfer, and even while **being processed by
+Unlike traditional tools, iExec protects your data throughout its entire
+lifecycle, during storage, transfer, and even while **being processed by
 applications.**
 
 This is made possible thanks to
@@ -128,8 +128,8 @@ applications:
 
 ### 1. Meet Bob: the dApp Developer 👨‍💻
 
-Bob is building a decentralized application that leverages iExec's technology.
-His platform consists of:
+Bob is building a decentralized application that uses iExec's technology. His
+platform consists of:
 
 - A user-friendly interface for users.
 - A DataProtector SDK that's easy to integrate into any application.
diff --git a/src/get-started/helloWorld/2-protectData.md b/src/get-started/helloWorld/2-protectData.md
index 06d841f7..088c6c17 100644
--- a/src/get-started/helloWorld/2-protectData.md
+++ b/src/get-started/helloWorld/2-protectData.md
@@ -30,7 +30,7 @@ their dApps with these key features:
 
 - 🔐 **Data Privacy and Security**
 
-  Utilizes end-to-end encryption and decentralized storage
+  Uses end-to-end encryption and decentralized storage
   (<a href="https://ipfs.tech/" target="_blank">IPFS</a> or
   <a href="https://ar.io/" target="_blank">AR.io</a>) to ensure protection and
   confidentiality, leveraging advanced confidential computing technology.
diff --git a/src/get-started/rlc.md b/src/get-started/overview/rlc.md
similarity index 75%
rename from src/get-started/rlc.md
rename to src/get-started/overview/rlc.md
index fd2a03ce..998aefb6 100644
--- a/src/get-started/rlc.md
+++ b/src/get-started/overview/rlc.md
@@ -1,8 +1,9 @@
 ---
 title: RLC Token
 description:
-  The RLC token is the cryptocurrency that powers the iExec decentralized
-  computing ecosystem
+  RLC (Run on Lots of Computers) is the cryptocurrency powering iExec's
+  confidential computing ecosystem. Learn about RLC tokenomics, utility, and how
+  it drives privacy-first Web3 applications.
 ---
 
 <div class="flex flex-col items-center mb-8">
@@ -11,15 +12,31 @@ description:
   <p class="text-lg text-center text-gray-600 max-w-2xl">The native cryptocurrency that powers the entire iExec decentralized confidential computing ecosystem</p>
 </div>
 
-**RLC** (**R**un on **L**ots of **C**omputers) serves as the primary medium of
-exchange for all interactions within the protocol, enabling users to access
-confidential computing services, and rewarding providers for their
+RLC (Run on Lots of Computers) powers all privacy apps on iExec. Every
+confidential computation requires RLC. Every piece of protected data consumed
+requires RLC. Every app execution requires RLC. The more builders use our tools,
+the more utility RLC gains in real applications.
+
+## 🎯 Why RLC Matters
+
+**Stack adoption = token usage.** Developers build with iExec tools. RLC gets
+used. More privacy apps deployed = more RLC demand.
+
+### For Users
+
+Every confidential computation you run uses RLC. That's how we keep your data
+private while making it usable.
+
+### For Providers
+
+Build apps, provide data, or run workers. All earn RLC when people use your
 contributions.
 
-## 🎯 What RLC Enables
+### For Holders
 
-RLC is essential for interacting with the iExec protocol and accessing its
-decentralized confidential computing services.
+**Clear positioning:** More developers using iExec's privacy tools = more RLC
+utility in real applications. We're building activable privacy, not just
+protocols.
 
 ## 💰 Transparent Payment Flow
 
@@ -46,7 +63,7 @@ protocol during the task period. In exchange, you receive **sRLC (staked RLC)**.
 Once the task is completed, you can recover the RLC that wasn't consumed for the
 task payment.
 
-## 💰 Tokenomics & Ecosystem Metrics
+### 📊 Ecosystem Growth Metrics
 
 RLC operates on a utility-driven economic model where demand for confidential
 computing services drives token value:
@@ -57,6 +74,14 @@ scarcity and value preservation.
 **Network Effects**: As more users and providers join the iExec ecosystem, the
 demand for RLC increases, driving token value through network effects.
 
+**Utility-Driven Growth**: Every interaction in the **Turnkey Privacy**
+ecosystem requires RLC:
+
+- iApp executions consume RLC for computation
+- Protected Data access requires RLC
+- Confidential computations need RLC for execution
+- Staking mechanisms lock RLC, reducing circulating supply
+
 <ImageViewer
     :image-url-dark="duneDashboard"
     image-alt="RLC Token Economics Dashboard"
diff --git a/src/get-started/overview/what-is-iapp.md b/src/get-started/overview/what-is-iapp.md
index 06f051fe..3870c5ac 100644
--- a/src/get-started/overview/what-is-iapp.md
+++ b/src/get-started/overview/what-is-iapp.md
@@ -1,18 +1,21 @@
 ---
 title: What is an iApp?
-description: Privacy-first applications that run on decentralized infrastructure
+description:
+  Learn about iExec Applications (iApps) - confidential computing apps that
+  process sensitive data in secure TEE environments. Build privacy-preserving
+  AI, data analysis, and Web3 apps.
 ---
 
 # 🚀 What is an iApp?
 
-An iExec Application (iApp) is your regular application code (Python script, AI
-model, data processor, ...) that can securely process protected data (created by
-[DataProtector](/references/dataProtector)) inside a confidential computing
-environment called TEE (a Trusted Execution Environment).
+An iExec Application (iApp) brings Turnkey Privacy to your regular application
+code. Your Python scripts, AI models, or data processors can securely process
+protected data inside a TEE (Trusted Execution Environment).
 
 ## Why iApps Matter ?
 
-iApps let you process sensitive data while keeping it private and secure.
+iApps provide Turnkey Privacy capabilities. Process sensitive data while keeping
+it private and secure.
 
 Imagine you want to build:
 
@@ -37,8 +40,10 @@ Imagine you want to build:
   </div>
 </div>
 
-Users have this data, but they won't give it to your regular app. **With iApps,
-they will.**
+Users have this data, but they won't trust your regular app with it. **With
+Turnkey Privacy iApps, they will.**
+
+**You gain their trust. They gain their privacy. Everyone wins.**
 
 ## Key Concepts
 
@@ -63,13 +68,12 @@ they will.**
 
 ## How it Works
 
-Your code runs in a Trusted Execution Environment (TEE), a secure area inside
-specific processors (Intel SGX/TDX chipset). Everything that happens there stays
-private and protected, even from the operating system.
+Your code runs in a Trusted Execution Environment (TEE). This secure area exists
+inside specific processors (Intel SGX/TDX chipset). Everything stays private and
+protected there, even from the operating system.
 
-An authorized user can trigger an iApp that processes someone's protected data
-inside this private environment. The data is used, but never exposed, not even
-to the person running the app.
+Authorized users trigger iApps that process protected data inside this private
+environment. Your iApp uses the data but never exposes it, not even to you.
 
 <div class="bg-[var(--vp-c-bg-soft)] rounded-[6px] p-6 mb-6">
   <div class="flex flex-col gap-3">
@@ -93,9 +97,9 @@ to the person running the app.
 </div>
 
 Your iApp can send emails, update contracts, make transactions, trigger
-notifications - anything your code needs to do with the protected data. This
-isn't about trust - it's about **cryptographic and hardware-enforced
-guarantees** that privacy is preserved within the TEE execution environment.
+notifications - anything your code needs. This isn't about trust. We provide
+**cryptographic and hardware-enforced guarantees** that preserve privacy within
+the TEE execution environment.
 
 ## Use Cases
 
diff --git a/src/get-started/overview/what-is-protected-data.md b/src/get-started/overview/what-is-protected-data.md
index b77571da..969692b2 100644
--- a/src/get-started/overview/what-is-protected-data.md
+++ b/src/get-started/overview/what-is-protected-data.md
@@ -1,16 +1,19 @@
 ---
 title: What is Protected Data?
-description: Understanding iExec's data protection mechanisms
+description:
+  Learn about iExec's Protected Data - encrypted datasets that enable
+  privacy-preserving computation. Understand DataProtector encryption, access
+  controls, and secure data monetization.
 ---
 
 # ❓ What is Protected Data?
 
 Protected Data refers to any data encrypted using the **iExec Data Protector
-tool**. This end-to-end encryption solution enables users to protect, manage and
-monetize their data within the Web3 ecosystem.
+tool**. This Turnkey Privacy encryption solution enables users to protect,
+manage and monetize their data within the Web3 ecosystem effortlessly.
 
 <div class="bg-gradient-to-r from-purple-400/10 to-purple-400/5 rounded-[6px] p-6 border-l-4 border-fuchsia-700 mb-6">
-  <p class="m-0!">Unlike standard datasets, Protected Data exposes its <span class="text-fuchsia-700 font-semibold">data types on-chain</span> (for example, indicating that it contains an email address or a photo). This allows anyone to <span class="text-fuchsia-700 font-semibold">identify entries with the corresponding types</span>.</p>
+  <p class="m-0!">Unlike standard datasets, Protected Data exposes its <span class="text-fuchsia-700 font-semibold">data types on-chain</span> (indicating types like email addresses or photos). This lets anyone <span class="text-fuchsia-700 font-semibold">identify entries with matching types</span>.</p>
 </div>
 
 ## Key Concepts
@@ -186,7 +189,7 @@ monetize their data within the Web3 ecosystem.
 </div>
 
 <div class="bg-gradient-to-r from-green-400/10 to-green-400/5 rounded-[6px] p-6 border-l-4 border-green-600 mb-6">
-  <p class="m-0!">Ready to protect your data? Start with our <span class="text-green-700 font-semibold">DataProtector guides</span> and learn how to secure your sensitive information while unlocking its value.</p>
+  <p class="m-0!">Ready to protect your data? Start with our <span class="text-green-700 font-semibold">DataProtector guides</span>. Learn how to secure sensitive information while unlocking its value.</p>
 </div>
 
 ## Next Steps
diff --git a/src/get-started/quick-start.md b/src/get-started/quick-start.md
index afad97a4..9e3c2d32 100644
--- a/src/get-started/quick-start.md
+++ b/src/get-started/quick-start.md
@@ -102,7 +102,7 @@ learning and prototyping.
 
 </CardGrid>
 
-## Next StepsAfter Exploring our Starters and Sandboxes
+## Next Steps After Exploring our Starters and Sandboxes
 
 1. **Choose Your Framework**: Start with our Next.js template or wait for
    React/Vue options
diff --git a/src/get-started/welcome.md b/src/get-started/welcome.md
index 3011f4cc..7e10224a 100644
--- a/src/get-started/welcome.md
+++ b/src/get-started/welcome.md
@@ -1,10 +1,12 @@
 ---
 title: About iExec
 description:
-  Discover how iExec empowers developers to build privacy-first applications
+  Build privacy-first Web3 applications with iExec's turnkey privacy toolkit.
+  Confidential computing, TEE technology, and blockchain data protection made
+  simple for developers.
 ---
 
-# 💡 Privacy Made Easy
+# 💡 Turnkey Privacy Toolkit
 
 <div class="bg-gradient-to-r from-[#fcd15a] to-[#ffad4d] rounded-[6px] px-8 pb-4 text-gray-800 max-w-3xl mx-auto mb-6">
   <h2 class="text-2xl font-bold mt-0 !border-none">Welcome to iExec</h2>
@@ -13,17 +15,19 @@ description:
 
 ## 🤔 Why iExec?
 
-In a world where data privacy is more critical than ever, developers face a
-tough challenge: how to build innovative applications without compromising
-sensitive user data.
+You shouldn't have to choose between innovation and privacy. **Every developer
+deserves the power** to build groundbreaking applications while **keeping user
+data completely secure**. Your users deserve **absolute confidence** that their
+privacy is protected.
 
 <div class="bg-gradient-to-r from-purple-400/10 to-purple-400/5 rounded-[6px] p-6 border-l-4 border-fuchsia-700 mb-6">
-  <p class="!m-0">iExec solves this by providing a <span class="text-fuchsia-700 font-semibold">privacy-first toolkit</span> that makes it simple to protect, manage, and compute data securely, even in untrusted environments. We believe privacy should be a <span class="text-fuchsia-700 font-semibold">built-in feature</span>, not an afterthought.</p>
+  <p class="!m-0">iExec solves this with <span class="text-fuchsia-700 font-semibold">Turnkey Privacy</span> - a toolkit that simplifies data protection, management, and secure computation, even in untrusted environments. We believe privacy should be <span class="text-fuchsia-700 font-semibold">plug-and-play simple</span>, not an afterthought.</p>
 </div>
 
 ## 🛠️ How we Make it Happen
 
-iExec provides a complete toolkit that makes privacy simple and actionable:
+iExec provides Turnkey Privacy tools that make confidential computing simple and
+actionable:
 
 <div class="bg-[var(--vp-c-bg-soft)] rounded-[6px] p-6 mb-6">
   <div class="flex flex-col gap-3">
@@ -48,7 +52,7 @@ iExec provides a complete toolkit that makes privacy simple and actionable:
     <div class="flex items-center gap-3">
       <span class="text-xl">🔧</span>
       <div>
-        <strong>Plug & Play tools:</strong> Fluide experience with comprehensive toolkit, SDKs, and ready-to-use components for seamless development
+        <strong>Activable Tools:</strong> Composable toolkit, SDKs, and ready-to-use components for straightforward development
       </div>
     </div>
   </div>
@@ -152,7 +156,7 @@ Confidential Computing made easy
 </div>
 
 <div class="bg-gradient-to-r from-green-400/10 to-green-400/5 rounded-[6px] p-6 border-l-4 border-green-600 mb-6">
-  <p class="m-0!">In the next chapters, we'll guide you through our <span class="text-green-700 font-semibold">Hello World journey</span>, a 30 minutes start that will teach you everything about iExec, from <span class="text-green-700 font-semibold">protecting sensitive data</span> to <span class="text-green-700 font-semibold">building and deploying confidential apps</span>.</p>
+<p class="m-0!">The next chapters guide you through our <span class="text-green-700 font-semibold">Hello World journey</span>. This 30-minute start teaches you everything about iExec. You'll learn <span class="text-green-700 font-semibold">protecting sensitive data</span> and <span class="text-green-700 font-semibold">building and deploying confidential apps</span>.</p>
 </div>
 
 ## 🚀 Start Building
@@ -184,5 +188,12 @@ Ready to build privacy-first applications? Choose your path:
 
 ---
 
-_Ready to transform how you handle sensitive data? Let's build something amazing
-together._
+_**Join thousands of developers** who are already transforming the future of
+privacy. **You have the power** to build the next generation of trust-first
+applications. Let's build something amazing together._ 🚀
+
+<div class="bg-gradient-to-r from-amber-400/10 to-amber-400/5 rounded-[6px] p-6 border-l-4 border-amber-600 mt-6">
+  <h4 class="!mt-0 !mb-2">🏆 Join the iExec Community</h4>
+  <p class="!mb-2">Be part of a growing movement of developers, data owners, and privacy advocates who are <strong>reshaping how the world handles sensitive data</strong>.</p>
+  <p class="!mb-0">When you build with iExec, you're not just solving a technical challenge—<strong>you're championing user rights and digital sovereignty</strong>. Every application you create makes the web more private, more secure, and more trustworthy for everyone.</p>
+</div>
diff --git a/src/guides/build-iapp/build-&-deploy.md b/src/guides/build-iapp/build-&-deploy.md
index c037f4b1..06f99b98 100644
--- a/src/guides/build-iapp/build-&-deploy.md
+++ b/src/guides/build-iapp/build-&-deploy.md
@@ -7,8 +7,8 @@ description:
 # Create and Deploy an iApp
 
 iApps (iExec Applications) are decentralized applications that run on the iExec
-network. They leverage confidential computing to ensure data privacy and
-security while providing scalable off-chain computation.
+network. They use confidential computing to ensure data privacy and security
+while providing scalable off-chain computation.
 
 ## About iApp Generator
 
diff --git a/src/guides/build-iapp/debugging.md b/src/guides/build-iapp/debugging.md
index 80172c4a..6101f034 100644
--- a/src/guides/build-iapp/debugging.md
+++ b/src/guides/build-iapp/debugging.md
@@ -28,7 +28,7 @@ Understanding how your task progresses through the iExec network:
 
 ### iExec Explorer
 
-Track your tasks at [explorer.iex.ec](https://explorer.iex.ec):
+Track your tasks at [iExec Explorer](https://explorer.iex.ec):
 
 - Search by `taskId` or deal ID
 - Check status: `PENDING` → `ACTIVE` → `COMPLETED/FAILED`
diff --git a/src/guides/manage-data/monetize-protected-data.md b/src/guides/manage-data/monetize-protected-data.md
index a544fb0e..3674b327 100644
--- a/src/guides/manage-data/monetize-protected-data.md
+++ b/src/guides/manage-data/monetize-protected-data.md
@@ -1,5 +1,8 @@
 ---
-title: Monetize Protected Data
+title:
+  Monetize your encrypted data with iExec's DataProtector. Learn usage-based
+  payments with signed orders and time-based access subscriptions. Turn your
+  data into revenue streams securely.
 description:
   Explore different ways to monetize your protected data with signed orders
   (usage-based) and time-based access (time-period payments)
@@ -9,7 +12,7 @@ description:
 
 **Your protected data can generate revenue automatically.**
 
-iExec offers two fundamental approaches for monetizing your data:
+iExec provides two fundamental approaches for monetizing your data:
 
 - **DataProtector Core**: **Signed orders** with pay-per-use counting - specify
   exact conditions, users pay for each individual data processing
diff --git a/src/guides/use-iapp/getting-started.md b/src/guides/use-iapp/getting-started.md
index 2d9c22ed..c88164af 100644
--- a/src/guides/use-iapp/getting-started.md
+++ b/src/guides/use-iapp/getting-started.md
@@ -15,7 +15,8 @@ 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](/get-started/rlc) and
+  through learning programs) -
+  [Learn about RLC tokens](/get-started/overview/rlc) and
   [how to bridge them](/get-started/tooling-and-explorers/bridge)
 - Basic understanding of blockchain transactions
 - iExec SDK installed
diff --git a/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3mail.md b/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3mail.md
index 4a96ddca..873f12af 100644
--- a/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3mail.md
+++ b/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3mail.md
@@ -99,8 +99,8 @@ const iexec = new IExec({ ethProvider: window.ethereum });
 
 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.
+[RLC Token guide](/get-started/overview/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
diff --git a/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3telegram.md b/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3telegram.md
index 6dab94f6..3677d60d 100644
--- a/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3telegram.md
+++ b/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3telegram.md
@@ -105,8 +105,8 @@ const iexec = new IExec({ ethProvider: window.ethereum });
 
 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.
+[RLC Token guide](/get-started/overview/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
diff --git a/src/index.md b/src/index.md
index b894152e..71ae80b7 100644
--- a/src/index.md
+++ b/src/index.md
@@ -23,20 +23,20 @@ features:
   - icon: 🔐
     title: Protect & Manage Data
     details:
-      Secure your data with advanced encryption and control access while
-      maintaining privacy using DataProtector
+      DataProtector encrypts and allows you to control access to your sensitive
+      data. Ready-to-use privacy toolkit for developers.
     link: /guides/manage-data/manage-access
   - icon: 🤖
     title: Build iApps
     details:
-      Create decentralized applications that run on confidential computing
-      infrastructure with our iApp Generator
+      iApp Generator builds confidential applications that run in secure TEEs.
+      Custom confidentiality integration without managing infrastructure.
     link: /guides/build-iapp/build-&-deploy
   - icon: ⚡
     title: Use iApps
     details:
-      Execute existing iApps including Web3Mail, Web3Telegram for your
-      applications
+      Execute privacy-preserving apps like Web3Mail and Web3Telegram. Use what
+      others built, extend what you need.
     link: /guides/use-iapp/introduction
   - icon: 💰
     title: Monetize Data
@@ -47,7 +47,7 @@ features:
   - icon: 🧠
     title: Protocols
     details:
-      Deep dive into the core concepts of the protocol and understand how iExec
-      enables privacy, governance, and monetization
+      Deep dive into core protocol concepts. Understand how iExec enables
+      privacy, governance, and monetization.
     link: /get-started/protocol/proof-of-contribution
 ---
diff --git a/src/references/dataProtector/getting-started.md b/src/references/dataProtector/getting-started.md
index 13ff000d..4872e5f8 100644
--- a/src/references/dataProtector/getting-started.md
+++ b/src/references/dataProtector/getting-started.md
@@ -1,6 +1,9 @@
 ---
 title: Getting Started
-description: DataProtector getting started
+description:
+  Get started with DataProtector - iExec's turnkey privacy toolkit for
+  encrypting, controlling, and monetizing sensitive data. Learn SDK setup, data
+  protection, and access controls in minutes.
 ---
 
 # Getting Started
diff --git a/src/references/iapp-generator.md b/src/references/iapp-generator.md
index c2ac47a6..fc5dc478 100644
--- a/src/references/iapp-generator.md
+++ b/src/references/iapp-generator.md
@@ -1,32 +1,28 @@
 ---
 title: iApp Generator
 description:
-  Build privacy-first applications that run in secure TEE environments. Your
-  complete toolkit for creating, testing, and deploying confidential iApps on
-  the iExec network.
+  iApp Generator CLI toolkit for building confidential computing applications.
+  Create privacy-preserving AI, data analysis, and Web3 apps that run in secure
+  TEE environments. Deploy in minutes
 ---
 
 # 🤖 iApp Generator
 
-**Build privacy-first applications that run in secure TEE environments.** iApp
-Generator is your complete toolkit for creating, testing, and deploying
-confidential iApps on the iExec network.
-
-Transform your ideas into production-ready privacy-preserving applications in
-minutes, not months.
+**Here's the tool, what it does, and how to use it.** iApp Generator is a CLI
+that builds applications running inside TEEs. You write code, we handle the
+confidential computing setup.
 
 ## What is iApp Generator?
 
-**iApp Generator** is a CLI tool that simplifies building **iExec Applications
-(iApps)** - applications that run inside **Trusted Execution Environments
-(TEE)** for maximum privacy and security.
+**iApp Generator** builds confidential applications. Your code runs in Intel
+SGX/TDX secure enclaves where data stays private during processing.
 
-### What you Can Build
+### What you get
 
-- **AI models** that process sensitive data privately
-- **Data analysis** tools that protect user information
-- **Custom algorithms** with confidential inputs and outputs
-- **Privacy-preserving services** for Web3 applications
+- **Project scaffolding** - Complete setup, ready to deploy
+- **Local testing** - Debug in simulation mode before going live
+- **Simple deployment** - One command deploys to TEE workers
+- **Data integration** - Works with encrypted datasets out of the box
 
 ### What iApp Generator Provides
 
@@ -72,25 +68,25 @@ Ready for production? Dive into specialized topics:
 
 ## Why Choose iApp Generator?
 
-### 🔒 **Privacy by Design**
+### Privacy without infrastructure overhead
 
-Your applications run in hardware-secured enclaves where even the infrastructure
-provider can't access your data or code.
+Your code runs in Intel SGX/TDX enclaves. Even the worker running your app can't
+see what's happening inside.
 
-### ⚡ **Developer-Friendly**
+### You build, we handle the TEE complexity
 
-Focus on your application logic while iApp Generator handles the complex TEE
-setup, deployment, and execution infrastructure.
+Write normal application code. iApp Generator handles secure deployment, worker
+coordination, and result encryption.
 
-### 🌍 **Decentralized Infrastructure**
+### Runs everywhere TEEs exist
 
-Deploy on a global network of TEE-enabled workers without managing servers or
-cloud infrastructure.
+Deploy across Intel-enabled workers globally. No server management, no cloud
+provider lock-in.
 
-### 🔧 **Complete Toolkit**
+### Complete toolkit
 
-From local development to production deployment, everything you need is included
-in one CLI tool.
+Development, testing, deployment, and execution - everything included in one
+CLI.
 
 ## Ready to Build?
 
diff --git a/src/references/iapp-generator/building-your-iexec-app.md b/src/references/iapp-generator/building-your-iexec-app.md
index 41994eb6..b3491741 100644
--- a/src/references/iapp-generator/building-your-iexec-app.md
+++ b/src/references/iapp-generator/building-your-iexec-app.md
@@ -167,7 +167,7 @@ securely within a **Trusted Execution Environment (TEE)**.
 
 ::: info
 
-🧪 While **TEE** iApp are base on **intel SGX** technology by default, iApp has
+🧪 While **TEE** iApp are based on **intel SGX** technology by default, iApp has
 an experimental support for **intel TDX** applications.
 
 TDX mode is enabled by setting the environment variable
diff --git a/src/references/iapp-generator/deserializer.md b/src/references/iapp-generator/deserializer.md
index 11c61f32..8c41e487 100644
--- a/src/references/iapp-generator/deserializer.md
+++ b/src/references/iapp-generator/deserializer.md
@@ -15,8 +15,8 @@ schema.
 
 To simplify this process, you can use our lightweight utility package,
 `@iexec/dataprotector-deserializer`, in your iApp. This package streamlines the
-deserialization of protected data, making it easy for you to access and utilize
-the information securely.
+deserialization of protected data, making it easy for you to access and use the
+information securely.
 
 ## Overview
 

From 3975cae3f5daf2ed5b3cddfbdc8029024d2dd732 Mon Sep 17 00:00:00 2001
From: Le-Caignec <robinlecaignec@yahoo.fr>
Date: Sun, 17 Aug 2025 20:50:08 +0200
Subject: [PATCH 16/27] fix: correct typos and fix english

---
 src/get-started/develop-with-ai.md                     |  2 +-
 src/get-started/overview/rlc.md                        |  8 ++++----
 .../use-iapp/how-to-pay/how-to-pay-for-web3mail.md     |  6 +++---
 .../use-iapp/how-to-pay/how-to-pay-for-web3telegram.md | 10 +++++-----
 src/references/web3mail/methods/sendEmail.md           |  2 +-
 src/references/web3telegram/methods/sendTelegram.md    |  6 +++---
 6 files changed, 17 insertions(+), 17 deletions(-)

diff --git a/src/get-started/develop-with-ai.md b/src/get-started/develop-with-ai.md
index 210a7f59..fe222cbe 100644
--- a/src/get-started/develop-with-ai.md
+++ b/src/get-started/develop-with-ai.md
@@ -13,7 +13,7 @@ assistants while maintaining security best practices.
 
 ## 📚 Documentation for LLMs and AI Code Editors
 
-You can use some MCP (Model Control Protocol) servers like
+You can use MCP (Model Control Protocol) servers like
 [Context7](https://context7.com/iexecblockchaincomputing/documentation-tools) to
 provide:
 
diff --git a/src/get-started/overview/rlc.md b/src/get-started/overview/rlc.md
index 998aefb6..0b6177b1 100644
--- a/src/get-started/overview/rlc.md
+++ b/src/get-started/overview/rlc.md
@@ -19,8 +19,8 @@ the more utility RLC gains in real applications.
 
 ## 🎯 Why RLC Matters
 
-**Stack adoption = token usage.** Developers build with iExec tools. RLC gets
-used. More privacy apps deployed = more RLC demand.
+**Stack adoption = token usage.** When developers build with iExec tools, RLC
+gets used. More privacy apps deployed means more RLC demand.
 
 ### For Users
 
@@ -34,8 +34,8 @@ contributions.
 
 ### For Holders
 
-**Clear positioning:** More developers using iExec's privacy tools = more RLC
-utility in real applications. We're building activable privacy, not just
+**Clear positioning:** More developers using iExec's privacy tools means more
+RLC utility in real applications. We're building actionable privacy, not just
 protocols.
 
 ## 💰 Transparent Payment Flow
diff --git a/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3mail.md b/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3mail.md
index 873f12af..ce496cd0 100644
--- a/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3mail.md
+++ b/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3mail.md
@@ -85,13 +85,13 @@ To manage RLC tokens, developers must use the iExec SDK, which offers all the
 necessary tools for interacting with the iExec platform. This includes
 depositing, withdrawing, and checking balances of RLC and <TokenSymbol />
 
-- In your JS/TS project npm install iexec
+- In your JS/TS project, run `npm install iexec`
 - Instantiate the iExec SDK (see the
   [doc](https://github.com/iExecBlockchainComputing/iexec-sdk/blob/master/docs/README.md#quick-start))
 
 ```javascript
 import { IExec } from 'iexec';
-// connect injected provider
+// Connect to injected provider
 const iexec = new IExec({ ethProvider: window.ethereum });
 ```
 
@@ -100,7 +100,7 @@ const iexec = new IExec({ ethProvider: window.ethereum });
 Obtain RLC tokens from a supported cryptocurrency exchange. For detailed
 information on how to buy RLC tokens, see our
 [RLC Token guide](/get-started/overview/rlc) which covers all available DEX and
-CEX supported.
+CEX options.
 
 For detailed instructions on how to bridge RLC tokens between networks, see our
 [Bridge guide](/get-started/tooling-and-explorers/bridge) which covers all
diff --git a/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3telegram.md b/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3telegram.md
index 3677d60d..e2e0c1cf 100644
--- a/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3telegram.md
+++ b/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3telegram.md
@@ -70,7 +70,7 @@ const sendTelegram = await web3telegram.sendTelegram({
   protectedData: '0x123abc...',
   telegramContent: 'My telegram message content',
   senderName: 'Awesome project team',
-  label: 'some-cutom-id',
+  label: 'some-custom-id',
   workerpoolAddressOrEns: 'prod-v8-bellecour.main.pools.iexec.eth',
   dataMaxPrice: 42,
   appMaxPrice: 42,
@@ -91,13 +91,13 @@ To manage RLC tokens, developers must use the iExec SDK, which offers all the
 necessary tools for interacting with the iExec platform. This includes
 depositing, withdrawing, and checking balances of RLC and <TokenSymbol />
 
-- In your JS/TS project npm install iexec
+- In your JS/TS project, run `npm install iexec`
 - Instantiate the iExec SDK (see the
   [doc](https://github.com/iExecBlockchainComputing/iexec-sdk/blob/master/docs/README.md#quick-start))
 
 ```javascript
 import { IExec } from 'iexec';
-// connect injected provider
+// Connect to injected provider
 const iexec = new IExec({ ethProvider: window.ethereum });
 ```
 
@@ -106,7 +106,7 @@ const iexec = new IExec({ ethProvider: window.ethereum });
 Obtain RLC tokens from a supported cryptocurrency exchange. For detailed
 information on how to buy RLC tokens, see our
 [RLC Token guide](/get-started/overview/rlc) which covers all available DEX and
-CEX supported.
+CEX options.
 
 For detailed instructions on how to bridge RLC tokens between networks, see our
 [Bridge guide](/get-started/tooling-and-explorers/bridge) which covers all
@@ -147,7 +147,7 @@ const sendTelegram = await web3telegram.sendTelegram({
   protectedData: '0x123abc...',
   telegramContent: 'My telegram message content',
   senderName: 'Awesome project team',
-  label: 'some-cutom-id',
+  label: 'some-custom-id',
   workerpoolAddressOrEns: 'prod-v8-bellecour.main.pools.iexec.eth',
   dataMaxPrice: 42,
   appMaxPrice: 42,
diff --git a/src/references/web3mail/methods/sendEmail.md b/src/references/web3mail/methods/sendEmail.md
index 7bd39ea0..fc5c00fb 100644
--- a/src/references/web3mail/methods/sendEmail.md
+++ b/src/references/web3mail/methods/sendEmail.md
@@ -209,7 +209,7 @@ const sendEmail = await web3mail.sendEmail({
   protectedData: '0x123abc...',
   emailSubject: 'My email subject',
   emailContent: 'My email content',
-  label: 'some-cutom-id', // [!code focus]
+  label: 'some-custom-id', // [!code focus]
 });
 ```
 
diff --git a/src/references/web3telegram/methods/sendTelegram.md b/src/references/web3telegram/methods/sendTelegram.md
index 3c37d60e..c14135ac 100644
--- a/src/references/web3telegram/methods/sendTelegram.md
+++ b/src/references/web3telegram/methods/sendTelegram.md
@@ -40,7 +40,7 @@ const sendTelegram = await web3telegram.sendTelegram({
   protectedData: '0x123abc...',
   telegramContent: 'My telegram message content',
   senderName: 'Awesome project team',
-  label: 'some-cutom-id',
+  label: 'some-custom-id',
   workerpoolAddressOrEns: 'prod-v8-bellecour.main.pools.iexec.eth',
   dataMaxPrice: 42,
   appMaxPrice: 42,
@@ -136,7 +136,7 @@ const sendTelegram = await web3telegram.sendTelegram({
   protectedData: '0x123abc...',
   telegramContent: 'My telegram message content',
   senderName: 'Awesome project team',
-  label: 'some-cutom-id',
+  label: 'some-custom-id',
   workerpoolAddressOrEns: 'prod-v8-bellecour.main.pools.iexec.eth',
   dataMaxPrice: 42,
   appMaxPrice: 42,
@@ -172,7 +172,7 @@ const sendTelegram = await web3telegram.sendTelegram({
   protectedData: '0x123abc...',
   senderName: 'Arthur',
   telegramContent: 'My telegram message content',
-  label: 'some-cutom-id', // [!code focus]
+  label: 'some-custom-id', // [!code focus]
 });
 ```
 

From bedd5913260f156e9c0402999b369214309d98d8 Mon Sep 17 00:00:00 2001
From: Le-Caignec <robinlecaignec@yahoo.fr>
Date: Sun, 17 Aug 2025 23:14:04 +0200
Subject: [PATCH 17/27] fix: lisibility & ton

---
 src/get-started/helloWorld.md                    |  2 +-
 src/get-started/helloWorld/1-overview.md         | 11 +++++------
 src/get-started/helloWorld/2-protectData.md      |  7 ++++---
 src/get-started/overview/what-is-iapp.md         |  4 ++--
 src/get-started/overview/what-is-iexec.md        |  9 ++++-----
 .../overview/what-is-protected-data.md           |  4 ++--
 .../protocol/proof-of-contribution.md            |  9 +++------
 src/get-started/protocol/worker/quick-start.md   | 11 +++++------
 src/get-started/tooling-and-explorers/bridge.md  |  9 ++++-----
 src/get-started/use-cases.md                     |  6 +++---
 .../build-iapp/how-to-get-and-decrypt-results.md |  2 +-
 src/guides/use-iapp/getting-started.md           |  4 ++--
 .../how-to-pay/how-to-pay-for-web3mail.md        | 16 ++++++++--------
 .../how-to-pay/how-to-pay-for-web3telegram.md    | 16 ++++++++--------
 src/references/dataProtector.md                  |  2 +-
 .../dataProtectorCore/protectData.md             |  6 +++---
 src/references/dataProtector/migrate-from-v1.md  |  4 ++--
 src/references/glossary.md                       |  2 +-
 src/references/iapp-generator/deserializer.md    |  6 +++---
 src/references/web3mail.md                       |  2 +-
 src/references/web3mail/methods/sendEmail.md     | 10 +++++-----
 src/references/web3telegram.md                   |  2 +-
 src/references/web3telegram/getting-started.md   |  4 ++--
 23 files changed, 71 insertions(+), 77 deletions(-)

diff --git a/src/get-started/helloWorld.md b/src/get-started/helloWorld.md
index a4c61083..fa23f2e5 100644
--- a/src/get-started/helloWorld.md
+++ b/src/get-started/helloWorld.md
@@ -37,7 +37,7 @@ import ChainSelector from '@/components/ChainSelector.vue'
     <div class="text-3xl">📚</div>
     <div class="flex flex-col h-full min-h-[120px]">
       <h3 class="m-0! text-lg leading-tight text-[var(--vp-c-text-1)]">1 - iExec Overview</h3>
-      <p class="my-4 text-sm text-[var(--vp-c-text-2)]">Discover how iExec technologies work and the problem they solves</p>
+      <p class="my-4 text-sm text-[var(--vp-c-text-2)]">Discover how iExec technologies work and the problems they solve</p>
       <div class="mt-auto pt-3">
         <span class="inline-block text-sm bg-[var(--vp-c-bg-soft)] rounded text-[var(--vp-c-text-4)]">8 min read</span>
       </div>
diff --git a/src/get-started/helloWorld/1-overview.md b/src/get-started/helloWorld/1-overview.md
index 8f1fb28c..ff5d3ee7 100644
--- a/src/get-started/helloWorld/1-overview.md
+++ b/src/get-started/helloWorld/1-overview.md
@@ -1,10 +1,9 @@
 ---
 title: iExec Overview
 description:
-  Explore how iExec enables developers to build privacy-preserving dApps using
-  confidential computing, blockchain, and secure data management. Learn how
-  tools like DataProtector and iApps empower users to control, protect, and
-  monetize sensitive data across Web3 applications.
+  Explore how iExec's confidential computing toolkit helps developers build
+  privacy-preserving dApps. Learn how DataProtector and iApps let users control,
+  protect, and monetize sensitive data.
 ---
 
 # 🧐 iExec Overview
@@ -67,7 +66,7 @@ description:
 ## 👷 How do we Solve it?
 
 Unlike traditional tools, iExec protects your data throughout its entire
-lifecycle, during storage, transfer, and even while **being processed by
+lifecycle - during storage, transfer, and even while **being processed by
 applications.**
 
 This is made possible thanks to
@@ -159,7 +158,7 @@ And many other use cases...
 <p>In this chapter, we covered the core concepts of iExec:</p>
   <div class="flex items-center gap-3">
     <span class="text-xl">🔒</span>
-    <p class="m-0"><strong>Privacy-preserving Solution:</strong> iExec provides tools to protect sensitive data throughout its entire lifecycle - storage, transfer, and processing</p>
+    <p class="m-0"><strong>Privacy-preserving Toolkit:</strong> iExec provides tools to protect sensitive data throughout its entire lifecycle - storage, transfer, and processing</p>
   </div>
    <div class="flex items-center gap-3">
     <span class="text-xl">💡</span>
diff --git a/src/get-started/helloWorld/2-protectData.md b/src/get-started/helloWorld/2-protectData.md
index 088c6c17..0f6f743a 100644
--- a/src/get-started/helloWorld/2-protectData.md
+++ b/src/get-started/helloWorld/2-protectData.md
@@ -95,11 +95,11 @@ button:
   </div>
   <div class="flex items-center gap-3">
     <span class="bg-gray-950 text-sm text-white w-6 h-6 rounded-full flex items-center justify-center font-medium">3</span>
-    <span>The encrypted data is stored on IPFS</span>
+    <span>iExec's protocol stores the encrypted data on IPFS</span>
   </div>
   <div class="flex items-center gap-3">
     <span class="bg-gray-950 text-sm text-white w-6 h-6 rounded-full flex items-center justify-center font-medium">4</span>
-    <span>The symmetric key is stored in a secure enclave (TEE) in the Secret Management Service</span>
+    <span>iExec's protocol stores the symmetric key in a secure enclave (TEE) in the Secret Management Service</span>
   </div>
   <div class="flex items-center gap-3">
     <span class="bg-gray-950 text-sm text-white w-6 h-6 rounded-full flex items-center justify-center font-medium">5</span>
@@ -179,7 +179,8 @@ const { address: protectedDataAddress } = await dataProtectorCore.protectData({
 
 - 📦 **Protected Data** is encrypted and stored on decentralized storage
 
-- ⛓️ **Ownership** is stored on the blockchain and linked to your wallet
+- ⛓️ **Ownership** iExec's protocol writes ownership on the blockchain and links
+  it to your wallet
 
 - 🔌 **Integration** is simple with our developer tools
 
diff --git a/src/get-started/overview/what-is-iapp.md b/src/get-started/overview/what-is-iapp.md
index 3870c5ac..29ca35c9 100644
--- a/src/get-started/overview/what-is-iapp.md
+++ b/src/get-started/overview/what-is-iapp.md
@@ -54,7 +54,7 @@ Turnkey Privacy iApps, they will.**
   </div>
   <div class="bg-[var(--vp-c-bg-soft)] rounded-[6px] p-4 flex items-center gap-3">
     <span class="text-green-500 text-xl">✅</span>
-    <p class="m-0"><strong>Trusted Execution:</strong> iExec ensures that your code runs inside a Trusted Execution Environment (TEE), which guarantees that only the specified Docker image is executed in a secure and isolated environment.</p>
+    <p class="m-0"><strong>Trusted Execution:</strong> iExec ensures your code runs inside a Trusted Execution Environment (TEE), guaranteeing only the specified Docker image executes in a secure, isolated environment.</p>
   </div>
   <div class="bg-[var(--vp-c-bg-soft)] rounded-[6px] p-4 flex items-center gap-3">
     <span class="text-green-500 text-xl">✅</span>
@@ -62,7 +62,7 @@ Turnkey Privacy iApps, they will.**
   </div>
   <div class="bg-[var(--vp-c-bg-soft)] rounded-[6px] p-4 flex items-center gap-3">
     <span class="text-green-500 text-xl">✅</span>
-    <p class="m-0"><strong>Zero Trust Architecture:</strong> User data is protected by hardware-based TEEs, which keep data confidential and inaccessible to the host, cloud provider, or operating system during execution.</p>
+    <p class="m-0"><strong>Zero Trust Architecture:</strong> User data is protected by hardware-based TEEs, keeping data confidential and inaccessible to the host, cloud provider, or operating system during execution.</p>
   </div>
 </div>
 
diff --git a/src/get-started/overview/what-is-iexec.md b/src/get-started/overview/what-is-iexec.md
index 7649f867..e093910e 100644
--- a/src/get-started/overview/what-is-iexec.md
+++ b/src/get-started/overview/what-is-iexec.md
@@ -7,14 +7,13 @@ description:
 
 # What is iExec?
 
-iExec is a **decentralized computing platform** that enables developers to build
-and deploy privacy-preserving applications using confidential computing
-technology.
+iExec is a **decentralized confidential computing toolkit** that helps
+developers build privacy-preserving applications.
 
 ## 🎯 **Mission**
 
-iExec's mission is to democratize access to **confidential computing** by
-providing a decentralized infrastructure that combines:
+iExec democratizes **confidential computing** by providing a toolkit that
+combines:
 
 - **🔐 Privacy Protection** - Data remains encrypted during computation
 - **⚡ Scalable Computing** - Access to distributed computing resources
diff --git a/src/get-started/overview/what-is-protected-data.md b/src/get-started/overview/what-is-protected-data.md
index 969692b2..29846cb8 100644
--- a/src/get-started/overview/what-is-protected-data.md
+++ b/src/get-started/overview/what-is-protected-data.md
@@ -66,7 +66,7 @@ manage and monetize their data within the Web3 ecosystem effortlessly.
     <div class="flex items-center gap-3">
       <span>•</span>
       <div>
-        <strong>Secret storage:</strong> Secrets stored in a TEE database.
+        <strong>Secret storage:</strong> iExec's protocol secrets in a TEE database.
       </div>
     </div>
   </div>
@@ -130,7 +130,7 @@ manage and monetize their data within the Web3 ecosystem effortlessly.
     <div class="flex items-center gap-3">
       <span class="text-xl font-bold text-fuchsia-700">5.</span>
       <div>
-        <strong>Compute:</strong> Authorized users can compute on your data with the authorized iApps
+        <strong>Compute:</strong> Authorized users can compute on your data with authorized iApps
       </div>
     </div>
   </div>
diff --git a/src/get-started/protocol/proof-of-contribution.md b/src/get-started/protocol/proof-of-contribution.md
index f8a9ca83..b3d592e5 100644
--- a/src/get-started/protocol/proof-of-contribution.md
+++ b/src/get-started/protocol/proof-of-contribution.md
@@ -50,11 +50,11 @@ take the form of data, applications or computing power.
 Workers must achieve consensus on the execution result to get the requester’s
 funds. If consensus is not achieved, the requester is reimbursed.
 
-Worker and scheduler must stake RLC to participate as a computing providers. Bad
+Worker and scheduler must stake RLC to participate as computing providers. Bad
 behaviour from an actor results in a loss of stake.
 
 This is essential on the public blockchain, but all values can be set to 0 for
-private blockchain solutions.
+private blockchain networks.
 
 ### Permissioning
 
@@ -766,9 +766,6 @@ An application can only perform result encryption inside an enclave. No
 encryption key will be provided by the SMS to an application that doesn't run
 outside an enclave.
 
-(TODO: potential issue, key leaking to malicious application with the requester
-attacking a beneficiary)
-
 **[Dataset owner] How do I limit the usage of my dataset to a specific
 application?**
 
@@ -820,7 +817,7 @@ A scheduler could therefore emit two kinds of workerpoolorder:
 
 ### Callback
 
-Some requester might want an onchain callback with the result of the execution.
+Some requesters might want an onchain callback with the result of the execution.
 The callback mechanism is based on
 [[EIP-1154]](proof-of-contribution.md#references-1). The result is a `bytes`
 value that is set during the `finalize`. The `IexecProxy` implements both side
diff --git a/src/get-started/protocol/worker/quick-start.md b/src/get-started/protocol/worker/quick-start.md
index 371f58f1..340bde8e 100644
--- a/src/get-started/protocol/worker/quick-start.md
+++ b/src/get-started/protocol/worker/quick-start.md
@@ -34,13 +34,12 @@ 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 loading some <TokenSymbol /> and depositing 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.
+When the worker initialization process is complete, the worker will start and
+you will get: **Your worker is all set**. Your worker will now be able to
+compute tasks from the iExec network to earn <TokenSymbol />.
 
 ## Wallet restriction
 
diff --git a/src/get-started/tooling-and-explorers/bridge.md b/src/get-started/tooling-and-explorers/bridge.md
index f79c07d8..a37627ff 100644
--- a/src/get-started/tooling-and-explorers/bridge.md
+++ b/src/get-started/tooling-and-explorers/bridge.md
@@ -7,13 +7,12 @@ description:
 
 # RLC Bridge
 
-**RLC** (RLC Token) is the essential cryptocurrency for interacting with the
-iExec protocol. Whether you are executing tasks, accessing protected data, or
-participating in the iExec decentralized confidential computing network, you
-will need RLC tokens on the appropriate network.
+**RLC** (RLC Token) powers all iExec protocol interactions. You need RLC tokens
+whether you're executing tasks, accessing protected data, or participating in
+the iExec confidential computing network.
 
 This guide helps you bridge RLC tokens to **Bellecour** (becoming xRLC) and
-**Arbitrum** networks using dedicated bridge solutions.
+**Arbitrum** networks using the Bellecour Bridge and Stargate Bridge.
 
 ## 🗂️ Available Bridges
 
diff --git a/src/get-started/use-cases.md b/src/get-started/use-cases.md
index b370ac5f..68ddeea2 100644
--- a/src/get-started/use-cases.md
+++ b/src/get-started/use-cases.md
@@ -7,9 +7,9 @@ description:
 
 # Use Cases Showcase
 
-Explore our demo applications showcasing iExec's privacy-preserving technologies
-in action. Each use case demonstrates real-world applications of confidential
-computing and decentralized data protection.
+Explore our demo applications showcasing iExec's confidential computing toolkit
+in action. Each use case shows real-world applications of privacy-preserving
+technologies.
 
 <div class="grid grid-cols-1 gap-8 my-8">
   <UseCaseCard
diff --git a/src/guides/build-iapp/how-to-get-and-decrypt-results.md b/src/guides/build-iapp/how-to-get-and-decrypt-results.md
index cca00b1e..f56bef05 100644
--- a/src/guides/build-iapp/how-to-get-and-decrypt-results.md
+++ b/src/guides/build-iapp/how-to-get-and-decrypt-results.md
@@ -258,7 +258,7 @@ Error: Failed to decrypt result
 
 **Solutions**:
 
-- Ensure you're using the correct wallet (beneficiary)
+- Use the correct wallet (beneficiary)
 - Check if result was actually encrypted
 - Verify task completed successfully
 
diff --git a/src/guides/use-iapp/getting-started.md b/src/guides/use-iapp/getting-started.md
index c88164af..12aa52eb 100644
--- a/src/guides/use-iapp/getting-started.md
+++ b/src/guides/use-iapp/getting-started.md
@@ -6,8 +6,8 @@ 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 secure, privacy-preserving computation! This guide shows you how to
+use iApps on the iExec confidential computing network.
 
 ## Prerequisites
 
diff --git a/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3mail.md b/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3mail.md
index ce496cd0..599832b1 100644
--- a/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3mail.md
+++ b/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3mail.md
@@ -7,14 +7,14 @@ description:
 
 # How to Pay for Web3Mail
 
-[Web3Mail](/references/web3mail) dev tool offers secure, blockchain-based
-communication by encrypting emails and protecting user privacy.
+[Web3Mail](/references/web3mail) offers secure, blockchain-based communication
+by encrypting emails and protecting user privacy.
 
-The `sendEmail` function uses confidential computing power to encrypt and send
-messages, ensuring secure and decentralized email exchanges.
+The `sendEmail` function uses iExec's protocol to encrypt and send messages,
+ensuring secure and decentralized email exchanges.
 
-This guide explains how to pay for Web3Mail's computing power using **vouchers**
-and **<TokenSymbol />**, detailing the steps for each method.
+This guide shows how to pay for Web3Mail using **vouchers** and
+**<TokenSymbol />**.
 
 ## Using Vouchers for Web3Mail <ChainNotSupportedBadge />
 
@@ -34,8 +34,8 @@ and **<TokenSymbol />**, detailing the steps for each method.
   <img :src="builderDashboardImage" alt="Builder dashboard screenshot">
 </a>
 
-The iExec Builder Dashboard is a comprehensive tool for managing vouchers and
-resources, providing an intuitive interface for:
+The iExec Builder Dashboard manages vouchers and resources with an intuitive
+interface for:
 
 - **Claiming Vouchers**: Builders can claim vouchers during the BUILD and EARN
   stages.
diff --git a/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3telegram.md b/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3telegram.md
index e2e0c1cf..e9a9d098 100644
--- a/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3telegram.md
+++ b/src/guides/use-iapp/how-to-pay/how-to-pay-for-web3telegram.md
@@ -7,14 +7,14 @@ description:
 
 # How to Pay for Web3Telegram
 
-[Web3Telegram](/references/web3telegram) dev tool offers secure,
-blockchain-based communication by encrypting emails and protecting user privacy.
+[Web3Telegram](/references/web3telegram) offers secure, blockchain-based
+communication by encrypting messages and protecting user privacy.
 
-The `sendTelegram` function uses confidential computing power to encrypt and
-send messages, ensuring secure and decentralized email exchanges.
+The `sendTelegram` function uses iExec's protocol to encrypt and send messages,
+ensuring secure and decentralized email exchanges.
 
-This guide explains how to pay for Web3Telegram's computing power using
-**vouchers** and **<TokenSymbol />**, detailing the steps for each method.
+This guide shows how to pay for Web3Telegram using **vouchers** and
+**<TokenSymbol />**.
 
 ## Using Vouchers for Web3Telegram <ChainNotSupportedBadge />
 
@@ -34,8 +34,8 @@ This guide explains how to pay for Web3Telegram's computing power using
   <img :src="builderDashboardImage" alt="Builder dashboard screenshot">
 </a>
 
-The iExec Builder Dashboard is a comprehensive tool for managing vouchers and
-resources, providing an intuitive interface for:
+The iExec Builder Dashboard manages vouchers and resources with an intuitive
+interface for:
 
 - **Claiming Vouchers**: Builders can claim vouchers during the BUILD and EARN
   stages.
diff --git a/src/references/dataProtector.md b/src/references/dataProtector.md
index d8af04f3..ef3eab0e 100644
--- a/src/references/dataProtector.md
+++ b/src/references/dataProtector.md
@@ -1,7 +1,7 @@
 ---
 title: DataProtector
 description:
-  Discover DataProtector, iExec's secure data management solution. Encrypt,
+  Discover DataProtector, iExec's secure data management toolkit. Encrypt,
   share, and monetize your data with DataProtector Core and Sharing modules, all
   powered by blockchain technology.
 ---
diff --git a/src/references/dataProtector/dataProtectorCore/protectData.md b/src/references/dataProtector/dataProtectorCore/protectData.md
index 1f047598..f3355d9a 100644
--- a/src/references/dataProtector/dataProtectorCore/protectData.md
+++ b/src/references/dataProtector/dataProtectorCore/protectData.md
@@ -128,8 +128,8 @@ const protectedData = await dataProtectorCore.protectData({
 
 ::: tip
 
-If you'd like to **protect a file**, you first need to convert it to some kind
-of buffer. To do so, you can use `createArrayBufferFromFile`.
+If you'd like to **protect a file**, you first need to convert it to a buffer.
+You can use `createArrayBufferFromFile` to do this.
 
 ```ts twoslash
 const file: File = new File([], 'emptyFile.txt');
@@ -218,7 +218,7 @@ The name is public and not encrypted.
 **Type:** `"ipfs" | "arweave"`  
 **Default:** `"ipfs"`
 
-Specify the storage solution to use for the protected data encrypted payload
+Specify the storage platform to use for the protected data encrypted payload
 hosting.
 
 ```ts twoslash
diff --git a/src/references/dataProtector/migrate-from-v1.md b/src/references/dataProtector/migrate-from-v1.md
index a202d3f1..3ecf36cf 100644
--- a/src/references/dataProtector/migrate-from-v1.md
+++ b/src/references/dataProtector/migrate-from-v1.md
@@ -42,8 +42,8 @@ const dataProtector = new IExecDataProtectorCore(web3Provider); // [!code ++]
 
 ## Methods
 
-Some methods were renamed in order to standardize the SDK, they still provide
-the same functionalities as before.
+Some methods were renamed to standardize the SDK, but they still provide the
+same functionalities as before.
 
 ### Rename `fetchProtectedData` & Add New Filtering Param
 
diff --git a/src/references/glossary.md b/src/references/glossary.md
index 55f92760..00f8945f 100644
--- a/src/references/glossary.md
+++ b/src/references/glossary.md
@@ -38,7 +38,7 @@ Ensures computation confidentiality through mechanisms of memory encryption at
 the hardware level (in a Trusted Execution Environment or TEE). It can be used
 so that only authorized code can run inside a protected area and manipulate its
 data. In some cases, ensuring that code runs correctly without any third party
-altering the execution, is even more important than hiding the computation's
+altering the execution is even more important than hiding the computation's
 data.
 
 This concept is called Trusted Computing. These guarantees are critical for a
diff --git a/src/references/iapp-generator/deserializer.md b/src/references/iapp-generator/deserializer.md
index 8c41e487..2bb5d4e6 100644
--- a/src/references/iapp-generator/deserializer.md
+++ b/src/references/iapp-generator/deserializer.md
@@ -30,9 +30,9 @@ If you want to build your iApp in another language, you need to know how to
 deserialize a protected data.
 
 Under the hood, protected data are **zip files** replicating the tree structure
-of the original data object. Each value is stored in a dedicated file, binary
-values are stored as is while boolean, numbers, and strings are serialized with
-borsh.
+of the original data object. iExec's protocol stores each value in a dedicated
+file, binary values are stored as is while boolean, numbers, and strings are
+serialized with borsh.
 
 To access a value from a protected data, your app will need to unzip the iExec
 dataset file at `$IEXEC_IN/$IEXEC_DATASET_FILENAME`. Then for `'bool'`, `'f64'`,
diff --git a/src/references/web3mail.md b/src/references/web3mail.md
index cfff7c07..5dbd2bef 100644
--- a/src/references/web3mail.md
+++ b/src/references/web3mail.md
@@ -16,7 +16,7 @@ The Web3Mail tool offers a secure method to manage email-based communications
 via the blockchain. This mechanism helps protect the personal information of the
 email recipients through use of Ethereum addresses.
 
-The email address is stored as a `protectedData` entity using the
+iExec's protocol stores the email address as a `protectedData` entity using the
 [iExec Data Protector tool](/references/dataProtector). Through this mechanism,
 users have complete control over which applications may use their email address
 for sending communications. Sending a user a message, therefore, requires
diff --git a/src/references/web3mail/methods/sendEmail.md b/src/references/web3mail/methods/sendEmail.md
index fc5c00fb..39d3cdfc 100644
--- a/src/references/web3mail/methods/sendEmail.md
+++ b/src/references/web3mail/methods/sendEmail.md
@@ -10,11 +10,11 @@ description:
 This method allows an authorized entity to send an email message to a user
 without needing to know their email address.
 
-The recipient email address is stored in a `protectedData` entity. The user
-receiving the email must explicitly authorize you to send them email
-communications and permission must be granted for the `Web3Mail` tool to use the
-`protectedData` entity containing their email address. This is best done by
-granting authorization to the Web3Mail app whitelist
+The recipient email address in a `protectedData` entity. The user receiving the
+email must explicitly authorize you to send them email communications and
+permission must be granted for the `Web3Mail` tool to use the `protectedData`
+entity containing their email address. This is best done by granting
+authorization to the Web3Mail app whitelist
 `0x781482C39CcE25546583EaC4957Fb7Bf04C277D2` as `authorizedApp`. Refer to the
 [Data Protector `grantAccess`](/references/dataProtector/dataProtectorCore/grantAccess)
 documentation for more details.
diff --git a/src/references/web3telegram.md b/src/references/web3telegram.md
index 06ea8929..f485ee1d 100644
--- a/src/references/web3telegram.md
+++ b/src/references/web3telegram.md
@@ -16,7 +16,7 @@ Web3Telegram offers a secure method to manage telegram communications via the
 blockchain. This mechanism helps protect the personal information of the
 telegram chat ID recipients through use of Ethereum addresses.
 
-The telegram chat ID address is stored as a `protectedData` entity using
+iExec's protocol the telegram chat ID as a `protectedData` entity using
 [iExec Data Protector](/references/dataProtector). Through this mechanism, users
 have complete control over which applications may use their
 [chat ID](/references/web3telegram/integration-guide#_1-get-your-users-to-retrieve-their-chat-id)
diff --git a/src/references/web3telegram/getting-started.md b/src/references/web3telegram/getting-started.md
index a6825d72..36fedb09 100644
--- a/src/references/web3telegram/getting-started.md
+++ b/src/references/web3telegram/getting-started.md
@@ -45,8 +45,8 @@ bun add @iexec/web3telegram
 **This package is an ESM package. Your project needs to use ESM too.**
 &nbsp;[**Read more**](https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c)
 
-If you use it with **Webpack**, some polyfills will be needed. You will find
-later a working project
+If you use it with **Webpack**, some polyfills will be needed. You will find a
+working project later.
 
 ### Instantiate SDK
 

From ed803546e13b877556f2de4cfec821185a9da8a5 Mon Sep 17 00:00:00 2001
From: Le-Caignec <robinlecaignec@yahoo.fr>
Date: Sun, 17 Aug 2025 23:36:31 +0200
Subject: [PATCH 18/27] chore: update GitHub Actions workflow to trigger on
 pull requests instead of push events

---
 .github/workflows/main.yml | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
index e48e0ac4..140780db 100644
--- a/.github/workflows/main.yml
+++ b/.github/workflows/main.yml
@@ -2,9 +2,7 @@ name: main-ci
 
 on:
   workflow_dispatch:
-  push:
-    paths-ignore:
-      - 'README.md'
+  pull_request:
 
 jobs:
   build:

From 7314c2a17b572c74ecd72646dead58b3052f1084 Mon Sep 17 00:00:00 2001
From: Le-Caignec <robinlecaignec@yahoo.fr>
Date: Mon, 18 Aug 2025 08:38:31 +0200
Subject: [PATCH 19/27] docs: add Vale documentation for quality checks and
 update .gitignore

---
 .github/workflows/vale.yml | 18 ++++++++++++++
 .gitignore                 |  3 +++
 .vale.ini                  | 10 ++++++++
 README.md                  | 51 ++++++++++++++++++++++++++++++++++++++
 4 files changed, 82 insertions(+)
 create mode 100644 .github/workflows/vale.yml
 create mode 100644 .vale.ini

diff --git a/.github/workflows/vale.yml b/.github/workflows/vale.yml
new file mode 100644
index 00000000..882fad4f
--- /dev/null
+++ b/.github/workflows/vale.yml
@@ -0,0 +1,18 @@
+name: Documentation Quality
+
+on:
+  pull_request:
+
+jobs:
+  vale:
+    name: Vale Documentation Quality Check
+    runs-on: ubuntu-latest
+    
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+        
+      - name: Run Vale
+        uses: errata-ai/vale-action@v2.1.1
+        with:
+          files: src/
diff --git a/.gitignore b/.gitignore
index 7b041670..0c19ae7e 100644
--- a/.gitignore
+++ b/.gitignore
@@ -12,3 +12,6 @@ components.d.ts
 
 #mac
 .DS_Store
+
+#vale
+.github/styles/*
diff --git a/.vale.ini b/.vale.ini
new file mode 100644
index 00000000..6d6ccd75
--- /dev/null
+++ b/.vale.ini
@@ -0,0 +1,10 @@
+StylesPath = .github/styles
+MinAlertLevel = suggestion
+Packages = Google
+
+[formats]
+md = markdown
+
+[*.md]
+BasedOnStyles = Vale, Google
+IgnorePatterns = README.md
diff --git a/README.md b/README.md
index 6b071c8c..302ae9bc 100644
--- a/README.md
+++ b/README.md
@@ -4,9 +4,59 @@
 
 - **Node.js**: Version 22 or higher
 - **npm**: Comes bundled with Node.js
+- **Vale** (optional): For documentation linting and quality checks
 
 ## ⚙️ Configuration
 
+### Documentation Quality with Vale
+
+We use [Vale](https://vale.sh/) to maintain high-quality documentation standards. Vale checks your writing for clarity, consistency, and adherence to our style guidelines, helping us maintain a coherent tone of voice, accurate terminology, and overall editorial quality across the project.
+
+#### Installing Vale
+
+**macOS:**
+
+```bash
+brew install Vale/tap/vale
+```
+
+**Linux (Snap):**
+
+```bash
+snap install vale
+```
+
+**Windows:**
+
+```bash
+choco install vale
+```
+
+#### Running Vale Locally
+
+```bash
+# Download and install external configuration sources
+vale sync
+
+# Check all documentation files
+vale src/
+
+# Check specific files
+vale src/get-started/helloWorld/1-overview.md
+
+# Get detailed output
+vale --output=line src/
+```
+
+#### Vale Rules
+
+Our Vale configuration uses the Google & Vale writing style guide, which helps ensure:
+
+- Clear and concise language
+- Consistent terminology
+- Professional tone
+- Accessibility best practices
+
 ### Environment Variables (Optional)
 
 Some features of the application require environment variables. This
@@ -138,6 +188,7 @@ Fork this repository and ensure you're working on the `main` branch:
 >   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
+> - **Documentation Quality**: Vale will automatically check your documentation for style and clarity
 
 ### Some conventions
 

From 2782f75bbd1c0571adad1a0ca2fb442b8518e641 Mon Sep 17 00:00:00 2001
From: Le-Caignec <robinlecaignec@yahoo.fr>
Date: Mon, 18 Aug 2025 08:59:01 +0200
Subject: [PATCH 20/27] docs: improve readability of Vale documentation and
 clean up whitespace in workflow file

---
 .github/workflows/vale.yml |  4 ++--
 README.md                  | 11 ++++++++---
 2 files changed, 10 insertions(+), 5 deletions(-)

diff --git a/.github/workflows/vale.yml b/.github/workflows/vale.yml
index 882fad4f..ac1060e8 100644
--- a/.github/workflows/vale.yml
+++ b/.github/workflows/vale.yml
@@ -7,11 +7,11 @@ jobs:
   vale:
     name: Vale Documentation Quality Check
     runs-on: ubuntu-latest
-    
+
     steps:
       - name: Checkout code
         uses: actions/checkout@v4
-        
+
       - name: Run Vale
         uses: errata-ai/vale-action@v2.1.1
         with:
diff --git a/README.md b/README.md
index 9ad4659a..97fdee71 100644
--- a/README.md
+++ b/README.md
@@ -10,7 +10,10 @@
 
 ### Documentation Quality with Vale
 
-We use [Vale](https://vale.sh/) to maintain high-quality documentation standards. Vale checks your writing for clarity, consistency, and adherence to our style guidelines, helping us maintain a coherent tone of voice, accurate terminology, and overall editorial quality across the project.
+We use [Vale](https://vale.sh/) to maintain high-quality documentation
+standards. Vale checks your writing for clarity, consistency, and adherence to
+our style guidelines, helping us maintain a coherent tone of voice, accurate
+terminology, and overall editorial quality across the project.
 
 #### Installing Vale
 
@@ -50,7 +53,8 @@ vale --output=line src/
 
 #### Vale Rules
 
-Our Vale configuration uses the Google & Vale writing style guide, which helps ensure:
+Our Vale configuration uses the Google & Vale writing style guide, which helps
+ensure:
 
 - Clear and concise language
 - Consistent terminology
@@ -188,7 +192,8 @@ Fork this repository and ensure you're working on the `main` branch:
 >   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
-> - **Documentation Quality**: Vale will automatically check your documentation for style and clarity
+> - **Documentation Quality**: Vale will automatically check your documentation
+>   for style and clarity
 
 ### Some conventions
 

From 436394463b3d286e471f7e06709c6cc7ac72353d Mon Sep 17 00:00:00 2001
From: Le-Caignec <robinlecaignec@yahoo.fr>
Date: Mon, 18 Aug 2025 13:05:55 +0200
Subject: [PATCH 21/27] chore: update documentation to standardize terminology
 and improve clarity

---
 .../config/vocabularies/Technical/accept.txt  | 190 ++++++++++++++++++
 .../config/vocabularies/Technical/reject.txt  |   2 +
 .gitignore                                    |   3 +-
 .vale.ini                                     |   6 +
 src/get-started/helloWorld.md                 |   6 +-
 src/get-started/helloWorld/1-overview.md      |  26 +--
 src/get-started/helloWorld/2-protectData.md   |   6 +-
 src/get-started/helloWorld/3-buildIApp.md     |  14 +-
 .../helloWorld/4-manageDataAccess.md          |   6 +-
 src/get-started/helloWorld/5-bonusChapter.md  |   4 +-
 src/get-started/overview/what-is-iapp.md      |  12 +-
 src/get-started/overview/what-is-iexec.md     |   4 +-
 .../overview/what-is-protected-data.md        |   2 +-
 .../overview/what-is-workerpool.md            |   2 +-
 .../protocol/proof-of-contribution.md         |  12 +-
 .../protocol/worker/manage-access.md          |   4 +-
 .../blockchain-explorer.md                    |   2 +-
 .../builder-dashboard.md                      |  20 +-
 .../tooling-and-explorers/iexec-explorer.md   |  10 +-
 .../subgraph-explorer.md                      |   4 +-
 src/get-started/welcome.md                    |   2 +-
 .../advanced/create-your-first-sgx-app.md     |   4 +-
 .../advanced/create-your-first-tdx-app.md     |   4 +-
 src/guides/build-iapp/advanced/overview.md    |   2 +-
 .../advanced/quick-start-for-developers.md    |   8 +-
 .../build-iapp/advanced/your-first-app.md     |   2 +-
 src/guides/build-iapp/build-&-deploy.md       |   8 +-
 src/guides/build-iapp/debugging.md            |   2 +-
 src/guides/build-iapp/inputs-and-outputs.md   |   2 +-
 src/guides/build-iapp/using-tdx.md            |  14 +-
 .../handle-schemas-dataset-types.md           |  14 +-
 src/guides/manage-data/manage-access.md       |   8 +-
 .../use-iapp/add-inputs-to-execution.md       |  10 +-
 .../use-iapp/different-ways-to-execute.md     |  19 +-
 src/guides/use-iapp/getting-started.md        |  25 ++-
 src/guides/use-iapp/how-to-pay-executions.md  |   6 +-
 src/guides/use-iapp/introduction.md           |  12 +-
 .../use-iapp/use-iapp-with-protected-data.md  |  24 +--
 src/index.md                                  |   4 +-
 .../dataProtector/advanced/apps-whitelist.md  |  12 +-
 .../addAppToAddOnlyAppWhitelist.md            |   4 +-
 .../dataProtectorCore/grantAccess.md          |   2 +-
 .../dataProtectorCore/protectData.md          |   2 +-
 .../collection/removeCollection.md            |   4 +-
 .../consume/consumeProtectedData.md           |  14 +-
 .../renting/rentProtectedData.md              |  10 +-
 .../subscription/subscribeToCollection.md     |  14 +-
 .../dataProtector/migrate-from-v1.md          |   2 +-
 src/references/glossary.md                    |   6 +-
 src/references/iapp-generator.md              |   2 +-
 .../iapp-generator/building-your-iexec-app.md |   2 +-
 src/references/iapp-generator/deserializer.md |   2 +-
 .../web3mail/advanced-configuration.md        |  10 +-
 .../web3telegram/advanced-configuration.md    |  12 +-
 54 files changed, 400 insertions(+), 203 deletions(-)
 create mode 100644 .github/styles/config/vocabularies/Technical/accept.txt
 create mode 100644 .github/styles/config/vocabularies/Technical/reject.txt

diff --git a/.github/styles/config/vocabularies/Technical/accept.txt b/.github/styles/config/vocabularies/Technical/accept.txt
new file mode 100644
index 00000000..7812612a
--- /dev/null
+++ b/.github/styles/config/vocabularies/Technical/accept.txt
@@ -0,0 +1,190 @@
+# Technical terms for iExec documentation
+
+# Function Names
+protectData
+grantAccess
+revokeAllAccess
+revokeOneAccess
+transferOwnership
+createCollection
+removeCollection
+removeProtectedDataFromCollection
+sendEmail
+sendTelegram
+getValue
+deserializer
+deserialize
+consumeProtectedData
+rentProtectedData
+subscribeToCollection
+buyProtectedData
+setProtectedDataForSale
+setProtectedDataToRenting
+setProtectedDataToSubscription
+setProtectedDataRentingParams
+setSubscriptionParams
+addToCollection
+removeProtectedDataFromCollection
+removeProtectedDataFromRenting
+removeProtectedDataForSale
+addAppToAddOnlyAppWhitelist
+createAddOnlyAppWhitelist
+getUserAddOnlyAppWhitelist
+getGrantedAccess
+getProtectedData
+getResultFromCompletedTask
+getCollectionOwners
+getCollectionsByOwner
+getCollectionSubscriptions
+getProtectedDataInCollections
+getProtectedDataPricingParams
+getRentals
+fetchMyContacts
+fetchUserContacts
+unpublish
+
+# Function Parameters
+authorizedApp
+authorizedUser
+grantedAccess
+collectionId
+appsWhitelist
+userWhitelist
+useVoucher
+voucherAddress
+voucherOwner
+subscriberAddress
+renterAddress
+apporder
+datasetorder
+workerpoolorder
+requestorder
+requesters
+workerpools
+apporders
+appmaxprice
+datasetmaxprice
+workerpoolmaxprice
+apprestrict
+requesterrestrict
+workerpoolrestrict
+datasetprice
+taskId
+dealId
+userAddress
+resultHash
+resultSeal
+enclaveSign
+workerpoolSign
+inputFiles
+zipFile
+encryptionKey
+multiaddr
+ipfsNode
+ipfsGateway
+emailSubject
+emailContent
+contentType
+senderName
+telegramContent
+//TODO: check
+param
+params
+args
+environnement
+pageSize
+subgraphUrl
+subgraph
+iexecOptions
+uploadMode
+allowDebug
+requiredSchema
+keypair
+collectionOwner
+isRentable
+isDistributed
+NFTs
+creationTimestamp
+transactionHash
+txHash
+boolean
+bigint
+newOwner
+maxPrice
+workerpoolorders
+
+# iExec/Web3 Terms
+iExec
+CPUs
+LLMs
+Agentic
+DApp
+DApps
+blockchain
+ethereum
+intel
+nano
+workerpool
+protectedData
+dataProtector
+iApp
+sconification
+middleware
+oracle
+MREnclave
+Gramine
+//TODO: check
+permissioning
+Permissioning
+arithmetics
+webservers
+Javascript
+Dockerizable
+Dockerize
+Dockerhub
+dockerized
+keystore
+Webpack
+json
+polyfills
+Buildx
+hardcoding
+npm
+Arweave
+cryptocurrency
+cryptocurrencies
+crypto
+onchain
+offchain
+//TODO: check
+mainchain
+Sidechain
+Bellecour
+Mainnet
+Testnet
+Metamask
+Binance
+Coinbase
+Uniswap
+Szabo
+presale
+presigned
+untrusted
+dev
+cryptocurrecny
+Unmatching
+incentivized
+Whitepaper
+deserialization
+enclaveChallenge
+Borsh
+Arbitrum
+Stargate
+Github
+subgraphs
+hackathons
+tokenization
+chipset
+auditable
+Composable
+Activable
diff --git a/.github/styles/config/vocabularies/Technical/reject.txt b/.github/styles/config/vocabularies/Technical/reject.txt
new file mode 100644
index 00000000..79c07ea1
--- /dev/null
+++ b/.github/styles/config/vocabularies/Technical/reject.txt
@@ -0,0 +1,2 @@
+# Terms to reject - currently empty
+# Add terms here that should always be flagged as errors
diff --git a/.gitignore b/.gitignore
index 0c19ae7e..0deadf0d 100644
--- a/.gitignore
+++ b/.gitignore
@@ -14,4 +14,5 @@ components.d.ts
 .DS_Store
 
 #vale
-.github/styles/*
+.github/styles/config/*
+!.github/styles/config/vocabularies/
diff --git a/.vale.ini b/.vale.ini
index 6d6ccd75..a2134c7d 100644
--- a/.vale.ini
+++ b/.vale.ini
@@ -2,9 +2,15 @@ StylesPath = .github/styles
 MinAlertLevel = suggestion
 Packages = Google
 
+# Define the Technical vocabulary for custom terminology
+Vocab = Technical
+
 [formats]
 md = markdown
 
 [*.md]
 BasedOnStyles = Vale, Google
 IgnorePatterns = README.md
+
+# Disable Vale.Terms to avoid case sensitivity issues
+Vale.Terms = NO
diff --git a/src/get-started/helloWorld.md b/src/get-started/helloWorld.md
index fa23f2e5..c7311d74 100644
--- a/src/get-started/helloWorld.md
+++ b/src/get-started/helloWorld.md
@@ -2,7 +2,7 @@
 title: Hello World Tutorial
 description:
   Kickstart your Web3 journey with iExec. In just 30 minutes, learn how to build
-  privacy-focused dApps, protect sensitive data, and manage data access.
+  privacy-focused DApp, protect sensitive data, and manage data access.
 ---
 
 <script setup>
@@ -12,7 +12,7 @@ import ChainSelector from '@/components/ChainSelector.vue'
 
 # 👋 Welcome to iExec
 
-> Reading time 🕒 2 mins
+> Reading time 🕒 2 min
 
 <div class="mb-0 p-6 bg-[var(--vp-c-bg-soft)] rounded-lg border border-[var(--vp-c-divider)]">
   <div class="flex">
@@ -23,7 +23,7 @@ import ChainSelector from '@/components/ChainSelector.vue'
 
 <div class="bg-gradient-to-r from-[#fcd15a] to-[#ffad4d] rounded-[6px] px-8 pb-4 text-gray-800 max-w-3xl mx-auto mb-6">
   <h2 class="text-2xl font-bold mt-0 border-none!">Start Your Web3 Privacy Journey</h2>
-  <p>And learn how to build Privacy-preserving decentralized applications (dApps) with iExec in this interactive guide.</p>
+  <p>And learn how to build Privacy-preserving decentralized applications (DApp) with iExec in this interactive guide.</p>
   <div class="mt-6 flex items-center gap-4">
     <span class="bg-gray-900 text-white px-4 py-2 rounded-full font-medium">☕ 30 minutes journey</span>
     <p>Perfect for hackathons 😊</p>
diff --git a/src/get-started/helloWorld/1-overview.md b/src/get-started/helloWorld/1-overview.md
index ff5d3ee7..4863a05b 100644
--- a/src/get-started/helloWorld/1-overview.md
+++ b/src/get-started/helloWorld/1-overview.md
@@ -2,22 +2,22 @@
 title: iExec Overview
 description:
   Explore how iExec's confidential computing toolkit helps developers build
-  privacy-preserving dApps. Learn how DataProtector and iApps let users control,
+  privacy-preserving iApp. Learn how DataProtector and iApp let users control,
   protect, and monetize sensitive data.
 ---
 
 # 🧐 iExec Overview
 
-> Reading time 🕒 8 mins
+> Reading time 🕒 8 min
 
 <div class="bg-gradient-to-r from-[#fcd15a] to-[#ffad4d] rounded-[6px] px-8 pb-4 text-gray-800 max-w-3xl mx-auto mb-6">
   <h2 class="text-2xl font-bold mt-0 border-none!">Let's start with the basics</h2>
   <p>and explore how iExec can help you build Privacy-preserving applications and securely manage sensitive data.</p>
 </div>
 
-## 👨‍💻 Building Privacy-preserving dApps with iExec
+## 👨‍💻 Building Privacy-preserving iApp with iExec
 
-<p>Imagine you're building a decentralized application (dApp) that needs to <strong> handle sensitive user data</strong>, for example:</p>
+<p>Imagine you're building a decentralized application (iApp) that needs to <strong> handle sensitive user data</strong>, for example:</p>
 <div class="bg-[var(--vp-c-bg-soft)] rounded-[6px] p-6 mb-6">
   <div class="flex flex-col gap-2.5">
     <div class="flex items-center gap-2 text-base">
@@ -60,7 +60,7 @@ description:
 </div>
 
 <div class="bg-gradient-to-r from-purple-400/10 to-purple-400/5 rounded-[6px] p-6 border-l-4 border-fuchsia-700 mb-6">
-  <p class="m-0!">This is where <span class="text-fuchsia-700 font-semibold">iExec</span> comes in! We provide tools to easily add <span class="text-fuchsia-700 font-semibold">privacy</span> and <span class="text-fuchsia-700 font-semibold">monetization</span> features into your dApp.</p>
+  <p class="m-0!">This is where <span class="text-fuchsia-700 font-semibold">iExec</span> comes in! We provide tools to easily add <span class="text-fuchsia-700 font-semibold">privacy</span> and <span class="text-fuchsia-700 font-semibold">monetization</span> features into your iApp.</p>
 </div>
 
 ## 👷 How do we Solve it?
@@ -84,14 +84,14 @@ Computing</a></span> technologies.
 
 iExec combines three fundamental elements that work together seamlessly:
 
-#### 1. Protect Data with our Devtool [DataProtector](/references/dataProtector/getting-started)
+#### 1. Protect Data with our DevTool [DataProtector](/references/dataProtector/getting-started)
 
 - Encrypt your sensitive data and store it securely on Arweave or IPFS
 - Only you control who can access it and when
 - Perfect for private information like research data, business analytics, or
   personal records
 
-#### 2. Compute Data with iExec Apps (iApps) Running in Secure Environment
+#### 2. Compute Data with iExec Apps (iApp) Running in Secure Environment
 
 - Special applications that can work with protected data
 - Run in secure environments (called TEEs) that keep your data private
@@ -115,17 +115,17 @@ inside stays **safe** and **private**.
 With a tool called **DataProtector**, your data becomes **protected** and can
 only be read and processed inside this secure room.
 
-Special applications called **iApps** (applications built to run in secure
+Special applications called **iApp** (applications built to run in secure
 environments) can enter the room to work with your data. You stay in **control**
 by setting **access rules** that only you can modify about who can access it and
 when.
 
-## 🔍 Building your First Privacy-preserving dApp
+## 🔍 Building your First Privacy-preserving iApp
 
 Let's meet Bob and Alice to understand how iExec enables Privacy-preserving
 applications:
 
-### 1. Meet Bob: the dApp Developer 👨‍💻
+### 1. Meet Bob: the iApp Developer 👨‍💻
 
 Bob is building a decentralized application that uses iExec's technology. His
 platform consists of:
@@ -135,7 +135,7 @@ platform consists of:
 - Thanks to DataProtector, end users can protect their data, manage access, and
   process it seamlessly.
 
-### 2. Meet Alice: the dApp User 👩‍💼
+### 2. Meet Alice: the iApp User 👩‍💼
 
 When using Bob's platform, Alice can:
 
@@ -144,7 +144,7 @@ When using Bob's platform, Alice can:
 - Authorize specific iExec Apps and persons like Bob to use her data in a secure
   environment
 
-Depending on the dApp's use case, Alice could:
+Depending on the iApp's use case, Alice could:
 
 - Apply algorithms to her data and get results confidentially
 - Share her data with other users privately (and get paid for it)
@@ -166,7 +166,7 @@ And many other use cases...
   </div>
   <div class="flex items-center gap-3">
     <span class="text-xl">📦</span>
-    <p class="m-0"><strong>iApps (iExec App):</strong> Special applications that can process protected data</p>
+    <p class="m-0"><strong>iApp (iExec App):</strong> Special applications that can process protected data</p>
   </div>
   <div class="flex items-center gap-3">
     <span class="text-xl">⛓️</span>
diff --git a/src/get-started/helloWorld/2-protectData.md b/src/get-started/helloWorld/2-protectData.md
index 0f6f743a..8c2d7526 100644
--- a/src/get-started/helloWorld/2-protectData.md
+++ b/src/get-started/helloWorld/2-protectData.md
@@ -15,7 +15,7 @@ import ProtectData from '@/modules/helloWorld/ProtectData.vue';
 
 <div class="bg-gradient-to-r from-[#fcd15a] to-[#ffad4d] rounded-[6px] px-8 pb-4 text-gray-800 max-w-3xl mx-auto mb-6">
   <h2 class="text-2xl font-bold mt-0 border-none!">Time to get practical</h2>
-  <p>Let's follow Alice as she learns how to protect her data using DataProtector on Bob's dApp, our developer tool for protecting data creation and management.</p>
+  <p>Let's follow Alice as she learns how to protect her data using DataProtector on Bob's iApp, our developer tool for protecting data creation and management.</p>
 </div>
 
 <div class="bg-gradient-to-r from-fuchsia-400/10 to-fuchsia-400/5 rounded-[6px] p-6 border-l-4 border-fuchsia-700 mb-6">
@@ -26,7 +26,7 @@ import ProtectData from '@/modules/helloWorld/ProtectData.vue';
 
 DataProtector is a developer tool built on top of our technology. It helps
 developers easily add data protection, management, and monetization features to
-their dApps with these key features:
+their DApp with these key features:
 
 - 🔐 **Data Privacy and Security**
 
@@ -40,7 +40,7 @@ their dApps with these key features:
   Allows users to manage access, enabling flexible control and monetization of
   data assets.
 
-- 🔌 **Seamless dApp Integration**
+- 🔌 **Seamless iApp Integration**
 
   Features an SDK for easy integration into your DApp, enhancing functionality
   and user experience.
diff --git a/src/get-started/helloWorld/3-buildIApp.md b/src/get-started/helloWorld/3-buildIApp.md
index 849e9c17..554dd493 100644
--- a/src/get-started/helloWorld/3-buildIApp.md
+++ b/src/get-started/helloWorld/3-buildIApp.md
@@ -7,15 +7,15 @@ description:
 
 # 🛠️ Build and Deploy your First iApp
 
-> Reading time 🕒 10 mins
+> Reading time 🕒 10 min
 
 <div class="bg-gradient-to-r from-[#fcd15a] to-[#ffad4d] rounded-[6px] px-8 pb-4 text-gray-800 max-w-3xl mx-auto mb-6">
   <h2 class="text-2xl font-bold mt-0 border-none!">Time to build!</h2>
-  <p>Let's build an iApp that can process protected data in a secure environment using the <a href="/references/iapp-generator" target="_blank" class="!text-gray-900 !font-bold underline hover:!text-black">iExec iApp generator tool</a>. This tool helps you create, test and deploy iApps with just a few commands.</p>
+  <p>Let's build an iApp that can process protected data in a secure environment using the <a href="/references/iapp-generator" target="_blank" class="!text-gray-900 !font-bold underline hover:!text-black">iExec iApp generator tool</a>. This tool helps you create, test and deploy iApp with just a few commands.</p>
 </div>
 
 If you wanna explore and deep dive in the CLI. You can check the
-[iapp-cli](https://github.com/iExecBlockchainComputing/iapp/tree/main/cli)
+[iApp-CLI](https://github.com/iExecBlockchainComputing/iapp/tree/main/cli)
 github repository. Follow the instructions carefully for a smooth development
 experience.
 
@@ -49,7 +49,7 @@ Before getting started, make sure you have:
   <p class="m-0!">Don't worry! All secrets used in this tutorial stay on your machine and aren’t shared with anyone. You’ll only need them to run the <code>iapp run</code> command.</p>
 </div>
 
-## 🚀 Types of iApps you Can Build
+## 🚀 Types of iApp you Can Build
 
 iExec enables you to build various types of Privacy-preserving applications.
 Here are some popular use cases:
@@ -373,7 +373,7 @@ Once you have your token, you can deploy your iApp.
   <p class="m-0!">📝 Make sure to save your <span class="text-fuchsia-700 font-semibold">iApp address</span> after deployment - you'll need it later!</p>
   <p class="m-0!">You can find your iApp address in the <code>iexec-app.json</code> file in your project folder.</p>
   <br>
-  <p class="m-0!">⚠️  If you encounter issues during deployment, make sure Docker's BuildKit feature is enabled and supports AMD64 architecture:</p>
+  <p class="m-0!">⚠️  If you encounter issues during deployment, make sure the Docker BuildKit feature is enabled and supports AMD64 architecture:</p>
 
 ```sh
 docker buildx inspect --bootstrap | grep -i platforms
@@ -403,8 +403,8 @@ protocol documentation [here](https://protocol.docs.iex.ec/).
 
 ## 🎯 Key Takeaways
 
-- 🔒 **iApps:** Special applications that run in TEEs to process protected data
-- 🛠️ **iApp CLI:** Command-line tool for building, testing, and deploying iApps
+- 🔒 **iApp:** Special applications that run in TEEs to process protected data
+- 🛠️ **iApp CLI:** Command-line tool for building, testing, and deploying iApp
 - 🔐 **Protected Data:** Can be integrated and processed securely in your iApp
 - ⛓️ **Deployment:** Apps are deployed on iExec protocol to run in trusted
   environments
diff --git a/src/get-started/helloWorld/4-manageDataAccess.md b/src/get-started/helloWorld/4-manageDataAccess.md
index e937396d..61d34b33 100644
--- a/src/get-started/helloWorld/4-manageDataAccess.md
+++ b/src/get-started/helloWorld/4-manageDataAccess.md
@@ -14,7 +14,7 @@ const { protectedDataAddress } = useWalletConnection();
 
 # 🔑 Manage Data Access
 
-> Reading time 🕒 6 mins
+> Reading time 🕒 6 min
 
 <div class="bg-gradient-to-r from-[#fcd15a] to-[#ffad4d] rounded-[6px] px-8 pb-4 text-gray-800 max-w-3xl mx-auto mb-6">
   <h2 class="text-2xl font-bold mt-0 border-none!">Control Your Data</h2>
@@ -97,8 +97,8 @@ iapp run <my-iapp-address> --protectedData {{ protectedDataAddress }}
 ## What's Next: Data Monetization
 
 We've completed the first step of the journey! You can now integrate the
-**DataProtector SDK** into your dApp, **secure your data**, **grant access** to
-users and iApps, and **process it safely**.
+**DataProtector SDK** into your iApp, **secure your data**, **grant access** to
+users and iApp, and **process it safely**.
 
 But here's where it gets even more exciting... **monetization!**.
 
diff --git a/src/get-started/helloWorld/5-bonusChapter.md b/src/get-started/helloWorld/5-bonusChapter.md
index 0897a677..5466264c 100644
--- a/src/get-started/helloWorld/5-bonusChapter.md
+++ b/src/get-started/helloWorld/5-bonusChapter.md
@@ -7,11 +7,11 @@ description:
 
 # 🎉 Bonus Chapter
 
-> Reading time 🕒 4 mins
+> Reading time 🕒 4 min
 
 <div class="bg-gradient-to-r from-[#fcd15a] to-[#ffad4d] rounded-[6px] px-8 pb-4 text-gray-800 max-w-3xl mx-auto mb-6">
   <h2 class="text-2xl font-bold mt-0 border-none!">Congratulations!</h2>
-  <p class="m-0!">You've successfully completed the Hello World journey and learned how to protect data, deploy iApps, and manage data access. Now it's time to claim your rewards! 🏆</p>
+  <p class="m-0!">You've successfully completed the Hello World journey and learned how to protect data, deploy iApp, and manage data access. Now it's time to claim your rewards! 🏆</p>
 </div>
 
 ## 🏁 Any Questions?
diff --git a/src/get-started/overview/what-is-iapp.md b/src/get-started/overview/what-is-iapp.md
index 29ca35c9..9a00386d 100644
--- a/src/get-started/overview/what-is-iapp.md
+++ b/src/get-started/overview/what-is-iapp.md
@@ -1,7 +1,7 @@
 ---
 title: What is an iApp?
 description:
-  Learn about iExec Applications (iApps) - confidential computing apps that
+  Learn about iExec Applications (iApp) - confidential computing apps that
   process sensitive data in secure TEE environments. Build privacy-preserving
   AI, data analysis, and Web3 apps.
 ---
@@ -12,9 +12,9 @@ An iExec Application (iApp) brings Turnkey Privacy to your regular application
 code. Your Python scripts, AI models, or data processors can securely process
 protected data inside a TEE (Trusted Execution Environment).
 
-## Why iApps Matter ?
+## Why iApp Matter ?
 
-iApps provide Turnkey Privacy capabilities. Process sensitive data while keeping
+iApp provide Turnkey Privacy capabilities. Process sensitive data while keeping
 it private and secure.
 
 Imagine you want to build:
@@ -41,7 +41,7 @@ Imagine you want to build:
 </div>
 
 Users have this data, but they won't trust your regular app with it. **With
-Turnkey Privacy iApps, they will.**
+Turnkey Privacy iApp, they will.**
 
 **You gain their trust. They gain their privacy. Everyone wins.**
 
@@ -72,7 +72,7 @@ Your code runs in a Trusted Execution Environment (TEE). This secure area exists
 inside specific processors (Intel SGX/TDX chipset). Everything stays private and
 protected there, even from the operating system.
 
-Authorized users trigger iApps that process protected data inside this private
+Authorized users trigger iApp that process protected data inside this private
 environment. Your iApp uses the data but never exposes it, not even to you.
 
 <div class="bg-[var(--vp-c-bg-soft)] rounded-[6px] p-6 mb-6">
@@ -126,7 +126,7 @@ the TEE execution environment.
 
 <div class="bg-gradient-to-r from-[#fcd15a] to-[#ffad4d] rounded-[6px] px-8 pb-4 text-gray-800 max-w-3xl mx-auto mb-6">
   <h2 class="text-2xl font-bold mt-0 border-none!">Time to build!</h2>
-  <p>Let's build an iApp that can process protected data in a secure environment using the <a href="/references/iapp-generator" target="_blank" class="!text-gray-900 !font-bold underline hover:!text-black">iExec iApp generator tool</a>. This tool helps you create, test and deploy iApps with just a few commands.</p>
+  <p>Let's build an iApp that can process protected data in a secure environment using the <a href="/references/iapp-generator" target="_blank" class="!text-gray-900 !font-bold underline hover:!text-black">iExec iApp generator tool</a>. This tool helps you create, test and deploy iApp with just a few commands.</p>
 </div>
 
 ### Quick Start Path
diff --git a/src/get-started/overview/what-is-iexec.md b/src/get-started/overview/what-is-iexec.md
index e093910e..3bf5a69f 100644
--- a/src/get-started/overview/what-is-iexec.md
+++ b/src/get-started/overview/what-is-iexec.md
@@ -24,7 +24,7 @@ combines:
 
 ### **Three Main Components:**
 
-1. **🤖 iApps (iExec Applications)**
+1. **🤖 iApp (iExec Applications)**
    - Confidential computing applications
    - Run in secure enclaves (TEEs)
    - Process encrypted data without exposing it
@@ -36,7 +36,7 @@ combines:
 
 3. **⚙️ Worker Network**
    - Distributed computing providers
-   - Execute iApps securely
+   - Execute iApp securely
    - Earn <TokenSymbol /> tokens for contributions
 
 ## 🚀 **Key Features**
diff --git a/src/get-started/overview/what-is-protected-data.md b/src/get-started/overview/what-is-protected-data.md
index 29846cb8..92a48250 100644
--- a/src/get-started/overview/what-is-protected-data.md
+++ b/src/get-started/overview/what-is-protected-data.md
@@ -130,7 +130,7 @@ manage and monetize their data within the Web3 ecosystem effortlessly.
     <div class="flex items-center gap-3">
       <span class="text-xl font-bold text-fuchsia-700">5.</span>
       <div>
-        <strong>Compute:</strong> Authorized users can compute on your data with authorized iApps
+        <strong>Compute:</strong> Authorized users can compute on your data with authorized iApp
       </div>
     </div>
   </div>
diff --git a/src/get-started/overview/what-is-workerpool.md b/src/get-started/overview/what-is-workerpool.md
index 3ef69aa9..fa8ffde6 100644
--- a/src/get-started/overview/what-is-workerpool.md
+++ b/src/get-started/overview/what-is-workerpool.md
@@ -1,7 +1,7 @@
 ---
 title: What is a Workerpool?
 description:
-  Learn about workerpools in iExec - the computing resources that execute iApps
+  Learn about workerpools in iExec - the computing resources that execute iApp
 ---
 
 # What is a Workerpool?
diff --git a/src/get-started/protocol/proof-of-contribution.md b/src/get-started/protocol/proof-of-contribution.md
index b3d592e5..a594403b 100644
--- a/src/get-started/protocol/proof-of-contribution.md
+++ b/src/get-started/protocol/proof-of-contribution.md
@@ -130,7 +130,7 @@ building consensus. In order to do so, the application just has to provide the
 path to the deterministic file using a specific entry
 `deterministic-output-path` in `${IEXEC_OUT}/computed.json`.
 
-Alternatively, if the application is used in a doracle context (the results are
+Alternatively, if the application is used in a oracle context (the results are
 designed to be processed on-chain by receiver smart-contracts), then the value
 of this callback must be specified in `${IEXEC_OUT}/computed.json` under the
 entry `callback-data`.
@@ -445,7 +445,7 @@ struct AppOrder
 }
 ```
 
-- `app` Address of the smartcontract describing the application. Must be
+- `app` Address of the smart contract describing the application. Must be
   registered in the AppRegistry.
 - `appprice` Price of a run of the application.
 - `volume` Number of run authorized (by this order).
@@ -478,7 +478,7 @@ struct DatasetOrder
 }
 ```
 
-- `dataset` Address of the smartcontract describing the dataset. Must be
+- `dataset` Address of the smart contract describing the dataset. Must be
   registered in the DatasetRegistry.
 - `datasetprice` Price of a use of the dataset.
 - `volume` Number of authorized uses (by this order).
@@ -513,7 +513,7 @@ struct WorkerpoolOrder
 }
 ```
 
-- `workerpool` Address of the smartcontract describing the worker pool. Must be
+- `workerpool` Address of the smart contract describing the worker pool. Must be
   registered in the WorkerpoolRegistry.
 - `workerpoolprice` Price of an execution on the worker pool.
 - `volume` Number of executions proposed (by this order).
@@ -555,11 +555,11 @@ struct RequestOrder
 }
 ```
 
-- `app` Address of the smartcontract describing the application. Must be
+- `app` Address of the smart contract describing the application. Must be
   registered in the AppRegistry.
 - `appmaxprice` Maximum price allowed by the requester for the payment of the
   application.
-- `dataset` Address of the smartcontract describing the dataset. Must be
+- `dataset` Address of the smart contract describing the dataset. Must be
   registered in the DatasetRegistry. Null if no dataset is required.
 - `datasetmaxprice` Maximum price allowed by the requester for the payment of
   the dataset (if any).
diff --git a/src/get-started/protocol/worker/manage-access.md b/src/get-started/protocol/worker/manage-access.md
index bba873b3..de601f30 100644
--- a/src/get-started/protocol/worker/manage-access.md
+++ b/src/get-started/protocol/worker/manage-access.md
@@ -49,7 +49,7 @@ your workerpool:
 | `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)                                   |
+| `apprestrict`       | restrict the workerpool usage to a specific app (1)                                   |
 | `datasetrestrict`   | restrict the workerpool usage to a specific dataset (1)                               |
 | `requesterrestrict` | restrict the workerpool usage to a specific requester (1)                             |
 
@@ -94,7 +94,7 @@ iexec orderbook workerpool <your workerpool address>
 
 Copy the `orderHash` of the order you want to remove
 
-Unpublish the `workerpoolorder` from the iExec Marketplace
+To unpublish the `workerpoolorder` from the iExec Marketplace
 
 ```bash
 iexec order unpublish --workerpool <orderHash>
diff --git a/src/get-started/tooling-and-explorers/blockchain-explorer.md b/src/get-started/tooling-and-explorers/blockchain-explorer.md
index 51acadb7..c891f704 100644
--- a/src/get-started/tooling-and-explorers/blockchain-explorer.md
+++ b/src/get-started/tooling-and-explorers/blockchain-explorer.md
@@ -39,7 +39,7 @@ publicly auditable.
 
 ::: tip 💡 Dev Tip
 
-Use **Bellecour** for development and testing as it's a gasless blockchain, then
+Use **Bellecour** for development and testing as it's a gas-free blockchain, then
 deploy to **Arbitrum** for production workloads.
 
 :::
diff --git a/src/get-started/tooling-and-explorers/builder-dashboard.md b/src/get-started/tooling-and-explorers/builder-dashboard.md
index e5f4687e..798161f7 100644
--- a/src/get-started/tooling-and-explorers/builder-dashboard.md
+++ b/src/get-started/tooling-and-explorers/builder-dashboard.md
@@ -2,7 +2,7 @@
 title: Builder Dashboard
 description:
   Monitor iExec applications with the powerful Builder Dashboard. Manage your
-  iApps and your manage vouchers
+  iApp and your manage vouchers
 ---
 
 # 🏗️ Builder Dashboard
@@ -11,7 +11,7 @@ The **Builder Dashboard** is your comprehensive development hub for iExec
 protocol. Monitor voucher usage, track your remaining compute capacity for TEE
 iApp runs, and view execution history—all in one place. This powerful interface
 streamlines your development workflow and provides deep insights on your
-confidential iApps deployed on the protocol.
+confidential iApp deployed on the protocol.
 
 <ImageViewer
   :image-url-dark="builderDashboardImage"
@@ -33,7 +33,7 @@ confidential iApps deployed on the protocol.
   <FeatureCard
     icon="mdi:apps"
     title="Confidential iApp Monitoring"
-    description="Monitor deployed iApps, track execution statistics, unique users"
+    description="Monitor deployed iApp, track execution statistics, unique users"
     icon-color="text-green-500"
   />
 </CardGrid>
@@ -96,21 +96,21 @@ monitoring with detailed task execution history and real-time balance tracking.
 ## 📱 Confidential iApp Management
 
 The second screen provides comprehensive management and analytics for your
-deployed confidential iApps with detailed statistics and user insights.
+deployed confidential iApp with detailed statistics and user insights.
 
 <ImageViewer
   :image-url-dark="myIappsViewImage"
-  image-alt="My Confidential iApps Dashboard"
-  link-url="https://builder.iex.ec/iapps"
-  caption="🔗 Manage Your iApps"
+  image-alt="My Confidential iApp Dashboard"
+  link-url="https://builder.iex.ec/iApp"
+  caption="🔗 Manage Your iApp"
 />
 
-### My Confidential iApps Overview
+### My Confidential iApp Overview
 
 <div class="bg-gradient-to-r from-blue-400/10 to-blue-400/5 rounded-[6px] p-6 border-l-4 border-blue-700 my-6">
   <h4 class="!mt-0 !mb-2">📱 iApp Portfolio Metrics</h4>
   <ul class="!mb-0">
-    <li><strong>Deployed Applications</strong>: Complete list of all your confidential iApps currently deployed</li>
+    <li><strong>Deployed Applications</strong>: Complete list of all your confidential iApp currently deployed</li>
     <li><strong>Execution Statistics</strong>: See exactly how many times each iApp has been executed</li>
     <li><strong>Unique Users</strong>: Track total unique users who have run each application</li>
     <li><strong>Revenue Insights</strong>: Track earnings and profitability per application</li>
@@ -122,7 +122,7 @@ deployed confidential iApps with detailed statistics and user insights.
 <CardGrid>
   <FeatureCard
     icon="mdi:apps"
-    title="Deployed iApps"
+    title="Deployed iApp"
     description="View all your confidential applications with deployment status, versions, and metadata"
     icon-color="text-blue-500"
   />
diff --git a/src/get-started/tooling-and-explorers/iexec-explorer.md b/src/get-started/tooling-and-explorers/iexec-explorer.md
index 93b981b7..af44feb9 100644
--- a/src/get-started/tooling-and-explorers/iexec-explorer.md
+++ b/src/get-started/tooling-and-explorers/iexec-explorer.md
@@ -31,9 +31,9 @@ explore apps and protectedData—all in one powerful dashboard.
   
   <FeatureCard
     icon="mdi:apps"
-    title="iApps Listing"
+    title="iApp Listing"
     description="Explore the catalog of trusted execution environment (TEE) applications, including their use cases and ownership details"
-    link-url="#iapps-listing"
+    link-url="#iApp-listing"
     icon-color="text-green-500"
   />
   
@@ -137,7 +137,7 @@ Browse and analyze all tasks across the iExec network:
 - **Execution Environment**: See which workerpool nodes are processing your
   tasks and their TEE capabilities (TDX, SGX)
 - **Data Flow**: Track which protected datasets are securely accessed by
-  authorized iApps
+  authorized iApp
 - **Result Management**:
   - **Download Results**: Access completed task outputs directly from the
     Explorer interface
@@ -145,13 +145,13 @@ Browse and analyze all tasks across the iExec network:
     requester specifications
   - **Result Verification**: Validate computation correctness and integrity
 
-## 📱 iApps Listing
+## 📱 iApp Listing
 
 <ImageViewer
   :image-url-dark="appViewImage"
   image-alt="App View"
   link-url="https://explorer.iex.ec/bellecour/apps"
-  caption="🔗 Explore iApps Marketplace"
+  caption="🔗 Explore iApp Marketplace"
 />
 
 Explore the iExec application marketplace:
diff --git a/src/get-started/tooling-and-explorers/subgraph-explorer.md b/src/get-started/tooling-and-explorers/subgraph-explorer.md
index 7b3768b8..cc1fef66 100644
--- a/src/get-started/tooling-and-explorers/subgraph-explorer.md
+++ b/src/get-started/tooling-and-explorers/subgraph-explorer.md
@@ -21,7 +21,7 @@ data through GraphQL queries.
 ## 🎯 What is the Graph?
 
 The Graph is a decentralized protocol for indexing and querying blockchain data.
-It enables developers to build and publish open APIs called **subgraphs** that
+It enables developers to build and publish open API called **subgraphs** that
 applications can query using GraphQL. This makes it easy to access blockchain
 data without having to run your own indexing infrastructure.
 
@@ -127,7 +127,7 @@ explore the available data and construct complex queries.
 
 Here are some example queries you can try in the GraphQL explorer:
 
-#### Query iApps
+#### Query iApp
 
 ```graphql
 query {
diff --git a/src/get-started/welcome.md b/src/get-started/welcome.md
index 7e10224a..562aa134 100644
--- a/src/get-started/welcome.md
+++ b/src/get-started/welcome.md
@@ -52,7 +52,7 @@ actionable:
     <div class="flex items-center gap-3">
       <span class="text-xl">🔧</span>
       <div>
-        <strong>Activable Tools:</strong> Composable toolkit, SDKs, and ready-to-use components for straightforward development
+        <strong>Available Tools:</strong> Composable toolkit, SDK, and ready-to-use components for straightforward development
       </div>
     </div>
   </div>
diff --git a/src/guides/build-iapp/advanced/create-your-first-sgx-app.md b/src/guides/build-iapp/advanced/create-your-first-sgx-app.md
index b53a4584..161c84f2 100644
--- a/src/guides/build-iapp/advanced/create-your-first-sgx-app.md
+++ b/src/guides/build-iapp/advanced/create-your-first-sgx-app.md
@@ -80,7 +80,7 @@ Make sure your `chain.json` content is as follows:
 }
 ```
 
-If you start from a new firectory tree, you will need to replay the following
+If you start from a new directory tree, you will need to replay the following
 steps from [Build your first application](./your-first-app):
 
 - [Write the app](./your-first-app.md#write-the-app) Javascript or Python source
@@ -195,7 +195,7 @@ Congratulations, you just built your Scone TEE application.
 
 You may have noticed the `tee-debug` flag in the image name, the built image is
 actually in TEE debug mode, this allows you to have some debug features while
-developping the app.
+developing the app.
 
 Once you are happy with the debug app, contact us to go to production!
 
diff --git a/src/guides/build-iapp/advanced/create-your-first-tdx-app.md b/src/guides/build-iapp/advanced/create-your-first-tdx-app.md
index 1047ab3b..93956d87 100644
--- a/src/guides/build-iapp/advanced/create-your-first-tdx-app.md
+++ b/src/guides/build-iapp/advanced/create-your-first-tdx-app.md
@@ -32,7 +32,7 @@ application need to be changed in order to run securely in a TEE. Only two files
 need to be changed compared to the usual SGX workflow: `chain.json` and
 `iexec.json`.
 
-iApps for the TDX framework follow the same format as non-TEE applications;
+iApp for the TDX framework follow the same format as non-TEE applications;
 follow the instructions on [Build your first application](./your-first-app) to
 create and Dockerize your iApp.
 
@@ -97,7 +97,7 @@ Deploy the app with the standard command:
 iexec app deploy
 ```
 
-To execute the app in TDX, ddd `--tag tee,tdx` to the `iexec app run` and select
+To execute the app in TDX, add `--tag tee,tdx` to the `iexec app run` and select
 the TDX workerpool (`tdx-labs.pools.iexec.eth`).
 
 ```bash
diff --git a/src/guides/build-iapp/advanced/overview.md b/src/guides/build-iapp/advanced/overview.md
index f3cc0be7..da776665 100644
--- a/src/guides/build-iapp/advanced/overview.md
+++ b/src/guides/build-iapp/advanced/overview.md
@@ -1,7 +1,7 @@
 ---
 title: Advanced iApp Building
 description:
-  Legacy, low-level guides for building confidential iApps (Docker, SGX, TDX,
+  Legacy, low-level guides for building confidential iApp (Docker, SGX, TDX,
   SCONE/Gramine, E2E encryption)
 ---
 
diff --git a/src/guides/build-iapp/advanced/quick-start-for-developers.md b/src/guides/build-iapp/advanced/quick-start-for-developers.md
index 32908455..5b1027a1 100644
--- a/src/guides/build-iapp/advanced/quick-start-for-developers.md
+++ b/src/guides/build-iapp/advanced/quick-start-for-developers.md
@@ -15,15 +15,15 @@ Requirements:
 [![npm version](https://img.shields.io/badge/nodejs-%3E=18.0.0-brightgreen.svg)](https://nodejs.org/en/)
 
 ```bash
-npm -g install iexec # install the cli
+npm -g install iexec # install the CLI
 iexec --version
 iexec --help
 ```
 
 ## Create your identity on the blockchain
 
-On the blockchain, your identity is defined by your **wallet,** constisting of
-cryptochraphically encrypted **private key** and **public address.** What you
+On the blockchain, your identity is defined by your **wallet,** consisting of
+cryptographically encrypted **private key** and **public address.** What you
 own on the blockchain is associated with your address. The applications you
 deploy on iExec are associated with your wallet.
 
@@ -207,7 +207,7 @@ Useful options:
 
 - `--args <args>` specify the app execution arguments
 - `--watch` watch execution status changes
-- `--workerpool <address>` specify the workerpool to use (eg:
+- `--workerpool <address>` specify the workerpool to use (for example:
   `--workerpool prod-v8-learn.main.pools.iexec.eth`)
 
 Discover more option with `iexec app run --help`
diff --git a/src/guides/build-iapp/advanced/your-first-app.md b/src/guides/build-iapp/advanced/your-first-app.md
index b12802da..824b15bf 100644
--- a/src/guides/build-iapp/advanced/your-first-app.md
+++ b/src/guides/build-iapp/advanced/your-first-app.md
@@ -354,7 +354,7 @@ You can pass input files to the app using `--input-files <list of URL>` option.
 With
 `--input-files https://example.com/file-A.txt,https://example.com/file-B.zip`
 the iExec worker will download the files before running the app in `IEXEC_IN`,
-and let the app access them throug variables:
+and let the app access them through variables:
 
 - `file-A.txt` as`IEXEC_INPUT_FILE_NAME_1`
 - `file-B.zip` as`IEXEC_INPUT_FILE_NAME_2`
diff --git a/src/guides/build-iapp/build-&-deploy.md b/src/guides/build-iapp/build-&-deploy.md
index 06f99b98..ac6a28dc 100644
--- a/src/guides/build-iapp/build-&-deploy.md
+++ b/src/guides/build-iapp/build-&-deploy.md
@@ -6,7 +6,7 @@ description:
 
 # Create and Deploy an iApp
 
-iApps (iExec Applications) are decentralized applications that run on the iExec
+iApp (iExec Applications) are decentralized applications that run on the iExec
 network. They use confidential computing to ensure data privacy and security
 while providing scalable off-chain computation.
 
@@ -22,8 +22,8 @@ iApp Generator handles all the low-level complexity for you.
   familiar programming languages while the generator handles all TEE-specific
   configurations.
 - **Access to TEEs easily** - No need to dive into low-level requirements,
-  create iApps that connect to TEEs in minutes.
-- **Check and deploy iApps quickly** - iApp Generator checks that your iApp
+  create iApp that connect to TEEs in minutes.
+- **Check and deploy iApp quickly** - iApp Generator checks that your iApp
   complies with the iExec Framework and streamlines its deployment.
 
 ## Prerequisites
@@ -222,7 +222,7 @@ specify your app version, and push both standard and TEE-compatible images:
 
 ## Real Examples
 
-Here are some real-world examples of iApps to help you understand how they work
+Here are some real-world examples of iApp to help you understand how they work
 in practice.
 
 ### Email Notification iApp
diff --git a/src/guides/build-iapp/debugging.md b/src/guides/build-iapp/debugging.md
index 6101f034..17e9c5a2 100644
--- a/src/guides/build-iapp/debugging.md
+++ b/src/guides/build-iapp/debugging.md
@@ -167,7 +167,7 @@ except Exception as e:
 
 ## What's Next?
 
-Continue improving your iApps:
+Continue improving your iApp:
 
 - **[Inputs and Outputs](/guides/build-iapp/inputs-and-outputs)** - Handle data
   in TEE
diff --git a/src/guides/build-iapp/inputs-and-outputs.md b/src/guides/build-iapp/inputs-and-outputs.md
index f2775e46..1012a2e6 100644
--- a/src/guides/build-iapp/inputs-and-outputs.md
+++ b/src/guides/build-iapp/inputs-and-outputs.md
@@ -1,7 +1,7 @@
 ---
 title: Inputs and Outputs
 description:
-  Understand the different input types and output formats for iApps in the TEE
+  Understand the different input types and output formats for iApp in the TEE
   environment
 ---
 
diff --git a/src/guides/build-iapp/using-tdx.md b/src/guides/build-iapp/using-tdx.md
index 642e93c9..1992e9e7 100644
--- a/src/guides/build-iapp/using-tdx.md
+++ b/src/guides/build-iapp/using-tdx.md
@@ -1,7 +1,7 @@
 ---
 title: Using TDX (Experimental)
 description:
-  Enable Intel TDX for enhanced TEE security in iApps - experimental feature
+  Enable Intel TDX for enhanced TEE security in iApp - experimental feature
 ---
 
 # 🛡️ Using TDX (Experimental)
@@ -15,8 +15,8 @@ instabilities, limited compatibility, and potential outages.
 :::
 
 **Intel TDX (Trust Domain Extensions) is the next generation of TEE
-technology.** This guide shows you how to enable TDX in your iApps and
-understand the differences from the default SGX implementation.
+technology.** This guide shows you how to enable TDX in your iApp and understand
+the differences from the default SGX implementation.
 
 ## What is TDX?
 
@@ -123,8 +123,8 @@ await dataProtector.core.processProtectedData({
 
 :::warning Protected Data Requirements
 
-**TDX iApps may require TDX-compatible protected data.** Check compatibility
-before using protected data with TDX iApps.
+**TDX iApp may require TDX-compatible protected data.** Check compatibility
+before using protected data with TDX iApp.
 
 :::
 
@@ -137,7 +137,7 @@ documentation for TDX-specific requirements.
 ### 1. **Local Testing**
 
 ```bash
-# Test locally (same as regular iApps)
+# Test locally (same as regular iApp)
 iapp test --protectedData "mock_name"
 
 # TDX only affects remote deployment/execution
@@ -189,4 +189,4 @@ EXPERIMENTAL_TDX_APP=true iapp run <app-address>
 - **[Inputs and Outputs](/guides/build-iapp/inputs-and-outputs)** - Handle data
   in TEE environment
 - **[App Access Control and Pricing](/guides/build-iapp/manage-access)** -
-  Deploy production-ready iApps
+  Deploy production-ready iApp
diff --git a/src/guides/manage-data/handle-schemas-dataset-types.md b/src/guides/manage-data/handle-schemas-dataset-types.md
index fce355ce..0158242b 100644
--- a/src/guides/manage-data/handle-schemas-dataset-types.md
+++ b/src/guides/manage-data/handle-schemas-dataset-types.md
@@ -1,7 +1,7 @@
 ---
 title: Handle Schemas and Dataset Types
 description:
-  Learn how schemas work in DataProtector and how to use them in your iApps
+  Learn how schemas work in DataProtector and how to use them in your iApp
 ---
 
 # 🏷️ Handle Schemas and Dataset Types
@@ -10,9 +10,9 @@ description:
 data.**
 
 They define the structure and types of your data automatically when you protect
-it, making it easy for iApps to know what they're working with.
+it, making it easy for iApp to know what they're working with.
 
-Think of schemas as **data fingerprints** - they tell iApps "this protected data
+Think of schemas as **data fingerprints** - they tell iApp "this protected data
 contains an email address and a phone number" without revealing the actual
 values.
 
@@ -59,7 +59,7 @@ console.log('📍 Address:', protectedData.address);
 
 ::: info Schema Structure
 
-The schema automatically maps your data structure to types that iApps can
+The schema automatically maps your data structure to types that iApp can
 understand and validate.
 
 :::
@@ -93,7 +93,7 @@ MIME types manually.
 
 ### 🎯 **For iApp Development**
 
-Schemas let your iApps validate and process data safely:
+Schemas let your iApp validate and process data safely:
 
 ```ts twoslash
 import { IExecDataProtectorDeserializer } from '@iexec/dataprotector-deserializer';
@@ -110,7 +110,7 @@ const preferences = await deserializer.getValue(
 
 ### 🛡️ **For Type Safety**
 
-Prevents your iApps from processing incompatible data types.
+Prevents your iApp from processing incompatible data types.
 
 ### 🔍 **For Data Discovery**
 
@@ -240,7 +240,7 @@ const fileData = await dataProtectorCore.protectData({
 }
 ```
 
-## Using Schemas in iApps
+## Using Schemas in iApp
 
 Once you have protected data with a schema, you'll want to process it inside an
 iApp.
diff --git a/src/guides/manage-data/manage-access.md b/src/guides/manage-data/manage-access.md
index 13863327..7b37b486 100644
--- a/src/guides/manage-data/manage-access.md
+++ b/src/guides/manage-data/manage-access.md
@@ -11,7 +11,7 @@ applications?**
 
 DataProtector lets you encrypt data and control access through orders -
 specifying who can use it, how many times, and at what price. Protected data is
-only accessible in secure enclaves (TEEs) by authorized users and iApps.
+only accessible in secure enclaves (TEEs) by authorized users and iApp.
 
 ## Installation
 
@@ -63,7 +63,7 @@ console.log('Protected data address:', protectedData.address);
 ### What you Can Protect
 
 **Data**: Any kind of data you want to keep private and make available for
-computations by authorized users and iApps.
+computations by authorized users and iApp.
 
 **Supported types**: Common data types like text, numbers, true/false values,
 and files. See the [full list here](/references/dataProtector/types).
@@ -81,7 +81,7 @@ for detailed formatting instructions.
 
 ### Debug Mode Option
 
-Debug mode lets you test with debug iApps during development. As "debug" iApps
+Debug mode lets you test with debug iApp during development. As "debug" iApp
 don't have the same security standards, we recommend using this mode only during
 iApp development.
 
@@ -153,7 +153,7 @@ data. No random code can touch it.
 
 **Pro tip**: Use app whitelists for production. Instead of a single app address,
 you can specify a whitelist contract that contains multiple app versions. Very
-useful for when you need to upgrade your iApps, without losing all the granted
+useful for when you need to upgrade your iApp, without losing all the granted
 access.
 
 ```ts
diff --git a/src/guides/use-iapp/add-inputs-to-execution.md b/src/guides/use-iapp/add-inputs-to-execution.md
index c9c6d3ba..eb6d321e 100644
--- a/src/guides/use-iapp/add-inputs-to-execution.md
+++ b/src/guides/use-iapp/add-inputs-to-execution.md
@@ -7,9 +7,9 @@ description:
 
 # 📥 Add Inputs to iApp Execution
 
-iApps can accept various types of inputs to customize their behavior and provide
+iApp 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.
+inputs to your iApp executions using various iExec tools and SDK.
 
 ## Types of Inputs
 
@@ -310,7 +310,7 @@ const taskResult = await dataProtectorCore.getResultFromCompletedTask({
 
 You can combine different types of inputs for complex executions.
 
-## How Secrets Work in iApps
+## How Secrets Work in iApp
 
 Inside the iApp, secrets are available as environment variables:
 
@@ -333,8 +333,8 @@ const dbPassword = process.env.IEXEC_SECRET_2; // 'database-password'
 Now that you understand how to add inputs to iApp executions:
 
 - Learn about
-  [Using iApps with Protected Data](/guides/use-iapp/use-iapp-with-protected-data)
+  [Using iApp with Protected Data](/guides/use-iapp/use-iapp-with-protected-data)
 - Explore
-  [Different Ways to Execute](/guides/use-iapp/different-ways-to-execute) iApps
+  [Different Ways to Execute](/guides/use-iapp/different-ways-to-execute) iApp
 - Check out our
   [How to Pay for Executions](/guides/use-iapp/how-to-pay-executions) guide
diff --git a/src/guides/use-iapp/different-ways-to-execute.md b/src/guides/use-iapp/different-ways-to-execute.md
index 2cd2afd3..bd9f25dc 100644
--- a/src/guides/use-iapp/different-ways-to-execute.md
+++ b/src/guides/use-iapp/different-ways-to-execute.md
@@ -1,12 +1,11 @@
 ---
-title: Different Ways to Execute iApps
-description:
-  Learn about various methods for executing iApps on the iExec network
+title: Different Ways to Execute iApp
+description: Learn about various methods for executing iApp on the iExec network
 ---
 
-# ⚡ Different Ways to Execute iApps
+# ⚡ Different Ways to Execute iApp
 
-There are multiple ways to execute iApps on the iExec network. This guide covers
+There are multiple ways to execute iApp 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.
 
@@ -25,7 +24,7 @@ designed for testing and development purposes on the Bellecour testnet.
 
 ## Method 1: Using the iExec SDK Library
 
-The iExec SDK provides a modular JavaScript interface for executing iApps.
+The iExec SDK provides a modular JavaScript interface for executing iApp.
 
 ```ts twoslash
 import { IExec, utils } from 'iexec';
@@ -80,8 +79,8 @@ iexec app run 0x456def...
 
 ## Method 3: Using the iApp Generator CLI
 
-The iApp Generator CLI provides a streamlined way to execute iApps, especially
-for developers who have built their own iApps.
+The iApp Generator CLI provides a streamlined way to execute iApp, especially
+for developers who have built their own iApp.
 
 > **Note**: For installation instructions, see the
 > [iApp Generator Getting Started guide](/references/iapp-generator/getting-started).
@@ -104,12 +103,12 @@ iapp test
 
 - **iExec Library**: For JavaScript applications and web3 integration
 - **iExec CLI**: For quick testing and automation scripts
-- **iApp Generator CLI**: For developers who have built their own iApps
+- **iApp Generator CLI**: For developers who have built their own iApp
 
 ## Next Steps
 
 - Learn how to
-  [use iApps with protected data](/guides/use-iapp/use-iapp-with-protected-data)
+  [use iApp with protected data](/guides/use-iapp/use-iapp-with-protected-data)
 - Discover how to
   [add inputs to execution](/guides/use-iapp/add-inputs-to-execution)
 - Understand [how to pay for executions](/guides/use-iapp/how-to-pay-executions)
diff --git a/src/guides/use-iapp/getting-started.md b/src/guides/use-iapp/getting-started.md
index 12aa52eb..c6be7e09 100644
--- a/src/guides/use-iapp/getting-started.md
+++ b/src/guides/use-iapp/getting-started.md
@@ -1,13 +1,12 @@
 ---
-title: Getting Started with iApps
-description:
-  Learn the basics of finding and executing iApps on the iExec network
+title: Getting Started with iApp
+description: Learn the basics of finding and executing iApp on the iExec network
 ---
 
-# 🚀 Getting Started with iApps
+# 🚀 Getting Started with iApp
 
 Welcome to secure, privacy-preserving computation! This guide shows you how to
-use iApps on the iExec confidential computing network.
+use iApp on the iExec confidential computing network.
 
 ## Prerequisites
 
@@ -43,11 +42,11 @@ bun add -g iexec
 
 Ready to dive in? Let's get started with finding and executing your first iApp!
 
-## Overview: How to Use iApps
+## Overview: How to Use iApp
 
-Using iApps involves these main steps:
+Using iApp involves these main steps:
 
-1. **Find iApps** - Browse available applications in the
+1. **Find iApp** - Browse available applications in the
    [iExec Explorer](/get-started/tooling-and-explorers/iexec-explorer)
 2. **Prepare Data** - Set up any required protected data or inputs
 3. **Execute** - Run the iApp
@@ -55,7 +54,7 @@ Using iApps involves these main steps:
 
 ### Understanding Orders
 
-iApps are executed through a marketplace system where different actors publish
+iApp are executed through a marketplace system where different actors publish
 orders:
 
 - **App orders** - Published by developers with pricing and availability
@@ -75,18 +74,18 @@ section.
 For step-by-step instructions, check out these guides:
 
 - **[Different Ways to Execute](/guides/use-iapp/different-ways-to-execute)** -
-  iExec cli, lib, and other execution methods
-- **[Use iApps with Protected Data](/guides/use-iapp/use-iapp-with-protected-data)** -
+  iExec CLI, lib, and other execution methods
+- **[Use iApp with Protected Data](/guides/use-iapp/use-iapp-with-protected-data)** -
   Working with sensitive data securely
 - **[Add Inputs to Execution](/guides/use-iapp/add-inputs-to-execution)** - How
-  to provide data and parameters to iApps
+  to provide data and parameters to iApp
 - **[How to Pay for Executions](/guides/use-iapp/how-to-pay-executions)** -
   Understanding costs and payment options
 
 ## Quick Start
 
 Ready to jump in? Follow the execution guides for detailed instructions on how
-to use iApps.
+to use iApp.
 
 <script setup>
 import ImageViewer from '@/components/ImageViewer.vue';
diff --git a/src/guides/use-iapp/how-to-pay-executions.md b/src/guides/use-iapp/how-to-pay-executions.md
index 08eb9754..e3d0fcbe 100644
--- a/src/guides/use-iapp/how-to-pay-executions.md
+++ b/src/guides/use-iapp/how-to-pay-executions.md
@@ -12,7 +12,7 @@ and cost management strategies.
 
 ## Payment Methods Overview
 
-iExec supports multiple payment methods for executing iApps:
+iExec supports multiple payment methods for executing iApp:
 
 1. **RLC Tokens**: Direct payment using <TokenSymbol /> tokens
 2. **Vouchers**: Pre-funded vouchers for simplified payment
@@ -127,7 +127,7 @@ has sufficient funds for this transfer to proceed.
 
 :::
 
-#### Using Someone Else's Voucher
+#### Using Someone Else Voucher
 
 ```ts twoslash
 import { IExecDataProtectorCore, getWeb3Provider } from '@iexec/dataprotector';
@@ -493,7 +493,7 @@ Now that you understand payment methods:
 - Learn about
   [Adding Inputs to Execution](/guides/use-iapp/add-inputs-to-execution)
 - Explore
-  [Using iApps with Protected Data](/guides/use-iapp/use-iapp-with-protected-data)
+  [Using iApp with Protected Data](/guides/use-iapp/use-iapp-with-protected-data)
 - Review the pricing information above for detailed cost analysis
 
 <script setup>
diff --git a/src/guides/use-iapp/introduction.md b/src/guides/use-iapp/introduction.md
index 5aef1167..bf9e72c1 100644
--- a/src/guides/use-iapp/introduction.md
+++ b/src/guides/use-iapp/introduction.md
@@ -1,11 +1,11 @@
 ---
-title: Introduction to Using iApps
+title: Introduction to Using iApp
 description:
-  Learn how to use iExec Applications (iApps) to securely process protected data
+  Learn how to use iExec Applications (iApp) to securely process protected data
   in a privacy-safe environment
 ---
 
-# 📝 Introduction to Using iApps
+# 📝 Introduction to Using iApp
 
 In the iExec network, multiple actors work together in a coordinated process to
 ensure secure, decentralized computation. Here's how the ecosystem operates:
@@ -22,7 +22,7 @@ ensure secure, decentralized computation. Here's how the ecosystem operates:
 
 ### Network Assets
 
-- **📱 iApps**: Applications that process the data securely
+- **📱 iApp**: 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
@@ -80,9 +80,9 @@ protected throughout the computation.
 
 ## Getting Started
 
-Ready to start using iApps? Check out our
+Ready to start using iApp? Check out our
 [Getting Started Guide](/guides/use-iapp/getting-started) to learn how to find,
-execute, and interact with iApps on the iExec network.
+execute, and interact with iApp on the iExec network.
 
 <script setup>
 import TokenSymbol from '@/components/TokenSymbol.vue'
diff --git a/src/guides/use-iapp/use-iapp-with-protected-data.md b/src/guides/use-iapp/use-iapp-with-protected-data.md
index 3a501a1b..2bdb23a0 100644
--- a/src/guides/use-iapp/use-iapp-with-protected-data.md
+++ b/src/guides/use-iapp/use-iapp-with-protected-data.md
@@ -1,25 +1,25 @@
 ---
-title: Use iApps with Protected Data
+title: Use iApp with Protected Data
 description:
-  Learn how to securely process protected data using iApps on the iExec network
+  Learn how to securely process protected data using iApp on the iExec network
 ---
 
-# 🔒 Use iApps with Protected Data
+# 🔒 Use iApp with Protected Data
 
 Protected data is the cornerstone of privacy-preserving computation on iExec.
-This guide shows you how to use iApps with protected data, from granting access
+This guide shows you how to use iApp with protected data, from granting access
 to processing and retrieving results.
 
-## Understanding Protected Data and iApps
+## Understanding Protected Data and iApp
 
 Protected data is encrypted information that can only be processed by authorized
-iApps within Trusted Execution Environments (TEEs). The data remains
-confidential throughout the entire computation process.
+iApp within Trusted Execution Environments (TEEs). The data remains confidential
+throughout the entire computation process.
 
 ### The Workflow
 
 1. **Protect Your Data**: Encrypt sensitive information using the Data Protector
-2. **Grant Access**: Authorize specific iApps to process your data
+2. **Grant Access**: Authorize specific iApp to process your data
 3. **Execute iApp**: Run the iApp with your protected data
 4. **Retrieve Results**: Get the computation results while data remains private
 
@@ -92,9 +92,9 @@ const { address: paymentDataAddress } = await dataProtectorCore.protectData({
 });
 ```
 
-## Step 2: Grant Access to iApps
+## Step 2: Grant Access to iApp
 
-iApps need explicit authorization to access your protected data.
+iApp need explicit authorization to access your protected data.
 
 ### Grant Access to a Specific iApp
 
@@ -453,10 +453,10 @@ const taskResult = await dataProtectorCore.getResultFromCompletedTask({
 
 ## Next Steps
 
-Now that you understand how to use iApps with protected data:
+Now that you understand how to use iApp with protected data:
 
 - Learn about
-  [Different Ways to Execute](/guides/use-iapp/different-ways-to-execute) iApps
+  [Different Ways to Execute](/guides/use-iapp/different-ways-to-execute) iApp
 - Explore [How to Pay for Executions](/guides/use-iapp/how-to-pay-executions)
 - Check out our
   [Add Inputs to Execution](/guides/use-iapp/add-inputs-to-execution) guide
diff --git a/src/index.md b/src/index.md
index 71ae80b7..dbd9dbb9 100644
--- a/src/index.md
+++ b/src/index.md
@@ -27,13 +27,13 @@ features:
       data. Ready-to-use privacy toolkit for developers.
     link: /guides/manage-data/manage-access
   - icon: 🤖
-    title: Build iApps
+    title: Build iApp
     details:
       iApp Generator builds confidential applications that run in secure TEEs.
       Custom confidentiality integration without managing infrastructure.
     link: /guides/build-iapp/build-&-deploy
   - icon: ⚡
-    title: Use iApps
+    title: Use iApp
     details:
       Execute privacy-preserving apps like Web3Mail and Web3Telegram. Use what
       others built, extend what you need.
diff --git a/src/references/dataProtector/advanced/apps-whitelist.md b/src/references/dataProtector/advanced/apps-whitelist.md
index 2f22aab4..c71c0db2 100644
--- a/src/references/dataProtector/advanced/apps-whitelist.md
+++ b/src/references/dataProtector/advanced/apps-whitelist.md
@@ -3,12 +3,12 @@ title: Apps Whitelist
 description:
   Understand the Apps Whitelist mechanism for consuming protected data in the
   iExec DataProtector Sharing module. Learn about the Trusted Execution
-  Environment (TEE) dApp and whitelist usage for secure data delivery.
+  Environment (TEE) iApp and whitelist usage for secure data delivery.
 ---
 
 # Apps Whitelist <ChainNotSupportedBadge />
 
-In order to consume a protected data, an iExec TEE dApp needs to be provided.
+In order to consume a protected data, an iExec TEE iApp needs to be provided.
 
 ::: tip
 
@@ -35,7 +35,7 @@ The story goes as follow:
 
 Built for the needs of
 [Content Creator use case](https://demo.iex.ec/content-creator/), this iExec TEE
-dApp is simple:
+iApp is simple:
 
 1. Download the protected data from IPFS. It expects to find a property named
    `file` in the protected data.
@@ -63,14 +63,14 @@ contract.
 **Whitelist address:** `0x256bcd881c33bdf9df952f2a0148f27d439f2e64`
 
 This whitelist contains current and past versions of the "Protected data
-delivery dApp"
+delivery iApp"
 
 See it in
 [https://blockscout-bellecour.iex.ec/](https://blockscout-bellecour.iex.ec/address/0x256bcd881c33bdf9df952f2a0148f27d439f2e64).
 
-### dApp
+### iApp
 
-**Most recent dApp from this whitelist:**
+**Most recent iApp from this whitelist:**
 `0x1cb7D4F3FFa203F211e57357D759321C6CE49921`
 
 See it in
diff --git a/src/references/dataProtector/advanced/apps-whitelist/addAppToAddOnlyAppWhitelist.md b/src/references/dataProtector/advanced/apps-whitelist/addAppToAddOnlyAppWhitelist.md
index db370135..bbc717b1 100644
--- a/src/references/dataProtector/advanced/apps-whitelist/addAppToAddOnlyAppWhitelist.md
+++ b/src/references/dataProtector/advanced/apps-whitelist/addAppToAddOnlyAppWhitelist.md
@@ -1,13 +1,13 @@
 ---
 title: addAppToAddOnlyAppWhitelist
 description:
-  Method to add an app (iExec TEE dApp) into the AddOnlyAppWhitelist for secure
+  Method to add an app (iExec TEE iApp) into the AddOnlyAppWhitelist for secure
   data access control.
 ---
 
 # addAppToAddOnlyAppWhitelist <ChainNotSupportedBadge />
 
-Method to add an app (iExec TEE dApp) into the `AddOnlyAppWhitelist`.
+Method to add an app (iExec TEE iApp) into the `AddOnlyAppWhitelist`.
 
 ::: warning
 
diff --git a/src/references/dataProtector/dataProtectorCore/grantAccess.md b/src/references/dataProtector/dataProtectorCore/grantAccess.md
index e83d8eb4..a8df83f4 100644
--- a/src/references/dataProtector/dataProtectorCore/grantAccess.md
+++ b/src/references/dataProtector/dataProtectorCore/grantAccess.md
@@ -96,7 +96,7 @@ iExec uses the ENS `web3mail.apps.iexec.eth` for the latest version of the
 Web3Mail decentralized application.
 
 iExec also maintains a whitelist for current and past versions of Web3Mail
-dApps. Granting access to this whitelist allows use of an email `protectedData`
+iApp. Granting access to this whitelist allows use of an email `protectedData`
 with all versions of the Web3Mail application, ensuring you only have to grant
 this access once. The ETH address for this whitelist is
 **0x781482C39CcE25546583EaC4957Fb7Bf04C277D2**.
diff --git a/src/references/dataProtector/dataProtectorCore/protectData.md b/src/references/dataProtector/dataProtectorCore/protectData.md
index f3355d9a..973f233c 100644
--- a/src/references/dataProtector/dataProtectorCore/protectData.md
+++ b/src/references/dataProtector/dataProtectorCore/protectData.md
@@ -389,7 +389,7 @@ details on the transaction using the [iExec explorer](https://explorer.iex.ec).
 
 Under the hood, your protected data will be **compressed as a zip file**. In
 this zip file, you'll find back all of your protected fields, each field being
-serialized with a tool called `borsh`. You can find more details here:
+serialized with a tool called `Borsh`. You can find more details here:
 [deserializer](/references/iapp-generator/deserializer).
 
 This is mainly returned for debug purpose.
diff --git a/src/references/dataProtector/dataProtectorSharing/collection/removeCollection.md b/src/references/dataProtector/dataProtectorSharing/collection/removeCollection.md
index b84d719f..17a565e7 100644
--- a/src/references/dataProtector/dataProtectorSharing/collection/removeCollection.md
+++ b/src/references/dataProtector/dataProtectorSharing/collection/removeCollection.md
@@ -10,8 +10,8 @@ description:
 
 Method to remove one of your collections in the Data Sharing smart contract.
 
-By removing a collection, we mean to burn the associated NFT, ie. to **transfer
-it to the zero address**.
+By removing a collection, we mean to burn the associated NFT, that is, to
+**transfer it to the zero address**.
 
 ## Usage
 
diff --git a/src/references/dataProtector/dataProtectorSharing/consume/consumeProtectedData.md b/src/references/dataProtector/dataProtectorSharing/consume/consumeProtectedData.md
index 7467cbce..53615b2f 100644
--- a/src/references/dataProtector/dataProtectorSharing/consume/consumeProtectedData.md
+++ b/src/references/dataProtector/dataProtectorSharing/consume/consumeProtectedData.md
@@ -8,7 +8,7 @@ description:
 
 # consumeProtectedData <ChainNotSupportedBadge />
 
-Method to consume a protected data, ie. visualize it or download it.
+Method to consume a protected data, that is, visualize it or download it.
 
 This method does a few things under the hood:
 
@@ -16,8 +16,8 @@ This method does a few things under the hood:
 - Push the public key to iExec SMS (Secret Management Service) (For more info,
   see
   [iExec Protocol documentation](https://protocol.docs.iex.ec/for-developers/confidential-computing/access-confidential-assets#secret-management-service-sms))
-- Wait for the consuming task to be executed by a worker. The iExec TEE dApp
-  being executed is the one given with the `app` parameter. The iExec TEE dApp
+- Wait for the consuming task to be executed by a worker. The iExec TEE iApp
+  being executed is the one given with the `app` parameter. The iExec TEE iApp
   will get the protected data from IPFS, encrypt it with the public key
   generated in the first step, and re-upload it to IPFS.
 - Retrieve the encrypted data from IPFS and decrypt it with the private key
@@ -81,8 +81,8 @@ const consumeProtectedDataResult =
 
 **Type:** `AddressOrENS`
 
-Address or ENS of the iExec TEE dApp that will be used to consume the protected
-data. This iExec TEE dApp is the one that runs within an iExec worker.
+Address or ENS of the iExec TEE iApp that will be used to consume the protected
+data. This iExec TEE iApp is the one that runs within an iExec worker.
 
 ```ts twoslash
 import {
@@ -102,7 +102,7 @@ const consumeProtectedDataResult =
 
 ::: tip
 
-For this `app` parameter you can use the "Protected data delivery TEE dApp":
+For this `app` parameter you can use the "Protected data delivery TEE iApp":
 
 ```
 0x1cb7D4F3FFa203F211e57357D759321C6CE49921
@@ -120,7 +120,7 @@ For more details, see
 
 ::: tip
 
-If you want to provide **your own TEE dApp**, you will need to create a
+If you want to provide **your own TEE iApp**, you will need to create a
 whitelist that contains your app.
 
 For more details, see
diff --git a/src/references/dataProtector/dataProtectorSharing/renting/rentProtectedData.md b/src/references/dataProtector/dataProtectorSharing/renting/rentProtectedData.md
index a599853b..cfd1516c 100644
--- a/src/references/dataProtector/dataProtectorSharing/renting/rentProtectedData.md
+++ b/src/references/dataProtector/dataProtectorSharing/renting/rentProtectedData.md
@@ -32,11 +32,11 @@ const rentResult = await dataProtectorSharing.rentProtectedData({
 ::: tip
 
 Technically, `price` and `duration` parameters could be avoided. It is mainly a
-protection against front-running "attacks", ie. if the collection owner changes
-the price **at the same time** you rent the protected data, you would end up
-paying more than expected. Passing the `price` here allows the SDK to ensure
-you're paying the right price. If prices don't match, the SDK will throw an
-error.
+protection against front-running "attacks", that is, if the collection owner
+changes the price **at the same time** you rent the protected data, you would
+end up paying more than expected. Passing the `price` here allows the SDK to
+ensure you're paying the right price. If prices don't match, the SDK will throw
+an error.
 
 :::
 
diff --git a/src/references/dataProtector/dataProtectorSharing/subscription/subscribeToCollection.md b/src/references/dataProtector/dataProtectorSharing/subscription/subscribeToCollection.md
index 5d51a636..7b7f0c50 100644
--- a/src/references/dataProtector/dataProtectorSharing/subscription/subscribeToCollection.md
+++ b/src/references/dataProtector/dataProtectorSharing/subscription/subscribeToCollection.md
@@ -37,18 +37,18 @@ const { txHash } = await dataProtectorSharing.subscribeToCollection({
 ::: tip
 
 Technically, `price` and `duration` parameters could be avoided. It is mainly a
-protection against front-running "attacks", ie. if the collection owner changes
-the price **at the same time** you subscribe to the collection, you would end up
-paying more than expected. Passing the `price` here allows the SDK to ensure
-you're paying the right price. If prices don't match, the SDK will throw an
-error.
+protection against front-running "attacks", that is, if the collection owner
+changes the price **at the same time** you subscribe to the collection, you
+would end up paying more than expected. Passing the `price` here allows the SDK
+to ensure you're paying the right price. If prices don't match, the SDK will
+throw an error.
 
 :::
 
 ## Pre-conditions
 
-- The collection must be available for subscription, ie. the collection owner
-  must have set a price and a duration.
+- The collection must be available for subscription, that is, the collection
+  owner must have set a price and a duration.
 
 ## Parameters
 
diff --git a/src/references/dataProtector/migrate-from-v1.md b/src/references/dataProtector/migrate-from-v1.md
index 3ecf36cf..6e8ae51c 100644
--- a/src/references/dataProtector/migrate-from-v1.md
+++ b/src/references/dataProtector/migrate-from-v1.md
@@ -132,7 +132,7 @@ The serialization of the data protected by `protectData()` has been changed to
 support a wider range of numbers, and extend the support for processing
 protected data in non-JS-based applications.
 
-The new serialization mechanism is based on the [borsh](https://borsh.io/)
+The new serialization mechanism is based on the [Borsh](https://borsh.io/)
 specification.
 
 Consequently, the data schemas associated with protected data have changed.
diff --git a/src/references/glossary.md b/src/references/glossary.md
index 00f8945f..9be08c24 100644
--- a/src/references/glossary.md
+++ b/src/references/glossary.md
@@ -106,7 +106,7 @@ the smart contracts on the blockchain.
 
 ### Explorer (iExec Explorer)
 
-Tracks and displays all transactions occuring on iExec’s platform. It provides
+Tracks and displays all transactions occurring on iExec’s platform. It provides
 detailed information on the latest deals, tasks, apps, and datasets deployed.
 
 ### ERC-20
@@ -333,7 +333,7 @@ See” Confidential Computing ” for more information
 
 Explain the purpose and technology behind a project. Producing a whitepaper is a
 key step for a crypto startup to help investors understand technical information
-about its concept; whitepapers usually include a roadmap for how the project
+about its concept; whitepaper usually include a roadmap for how the project
 plans to grow and succeed. iExec’s whitepaper is available
 [here](https://www.iex.ec/whitepaper)
 
@@ -361,7 +361,7 @@ requesters.
 
 X in xRLC stands for eXternal.
 
-A xRLC is the native token of iExec sidechains (it means it is used as ETH on
+A xRLC is the native token of iExec sidechain (it means it is used as ETH on
 ethereum mainnet). A xRLC is a RLC bridged on an external sidechain and only the
 bridge can mint\* xRLC.
 
diff --git a/src/references/iapp-generator.md b/src/references/iapp-generator.md
index fc5dc478..3fcbb33b 100644
--- a/src/references/iapp-generator.md
+++ b/src/references/iapp-generator.md
@@ -35,7 +35,7 @@ SGX/TDX secure enclaves where data stays private during processing.
 
 ### 1. **Learn the Concepts**
 
-Start here to understand what iApps are and how they work:
+Start here to understand what iApp are and how they work:
 
 - **[What Is an iApp?](/get-started/overview/what-is-iapp)** - Core concepts and
   TEE overview
diff --git a/src/references/iapp-generator/building-your-iexec-app.md b/src/references/iapp-generator/building-your-iexec-app.md
index b3491741..f3314326 100644
--- a/src/references/iapp-generator/building-your-iexec-app.md
+++ b/src/references/iapp-generator/building-your-iexec-app.md
@@ -160,7 +160,7 @@ within the iExec network.
 
 ::: info
 
-💡 A **workerpool** is a decentralized network of nodes that execute iApps
+💡 A **workerpool** is a decentralized network of nodes that execute iApp
 securely within a **Trusted Execution Environment (TEE)**.
 
 :::
diff --git a/src/references/iapp-generator/deserializer.md b/src/references/iapp-generator/deserializer.md
index 2bb5d4e6..2b280c5b 100644
--- a/src/references/iapp-generator/deserializer.md
+++ b/src/references/iapp-generator/deserializer.md
@@ -32,7 +32,7 @@ deserialize a protected data.
 Under the hood, protected data are **zip files** replicating the tree structure
 of the original data object. iExec's protocol stores each value in a dedicated
 file, binary values are stored as is while boolean, numbers, and strings are
-serialized with borsh.
+serialized with Borsh.
 
 To access a value from a protected data, your app will need to unzip the iExec
 dataset file at `$IEXEC_IN/$IEXEC_DATASET_FILENAME`. Then for `'bool'`, `'f64'`,
diff --git a/src/references/web3mail/advanced-configuration.md b/src/references/web3mail/advanced-configuration.md
index 1eccb10f..177b2205 100644
--- a/src/references/web3mail/advanced-configuration.md
+++ b/src/references/web3mail/advanced-configuration.md
@@ -21,12 +21,12 @@ import { type Web3MailConfigOptions } from '@iexec/web3mail';
 ### dappAddressOrENS
 
 The Ethereum contract address or ENS (Ethereum Name Service) for the web3mail
-dApp.
+iApp.
 
 If not provided, the default ENS `web3mail.apps.iexec.eth` pointing to the
-latest version of the web3mail dApp provided by iExec will be used.
+latest version of the web3mail iApp provided by iExec will be used.
 
-You can find the corresponding dApp address with Bellecour explorer:
+You can find the corresponding iApp address with Bellecour explorer:
 [https://explorer.iex.ec/bellecour/search/web3mail.apps.iexec.eth](https://explorer.iex.ec/bellecour/search/web3mail.apps.iexec.eth).
 
 ```ts twoslash
@@ -41,9 +41,9 @@ const web3mail = new IExecWeb3mail(web3Provider, {
 
 ### dappWhitelistAddress
 
-The Ethereum contract address for the web3mail dApps whitelist. By granting
+The Ethereum contract address for the web3mail iApp whitelist. By granting
 access to a whitelist, email address owners ensure their email is still
-available to consumers even after a new version of web3mail dApp gets released.
+available to consumers even after a new version of web3mail iApp gets released.
 
 If not provided, the default whitelist smart contract address provided by iExec
 will be used.
diff --git a/src/references/web3telegram/advanced-configuration.md b/src/references/web3telegram/advanced-configuration.md
index c18a4a38..b5229405 100644
--- a/src/references/web3telegram/advanced-configuration.md
+++ b/src/references/web3telegram/advanced-configuration.md
@@ -2,7 +2,7 @@
 title: Advanced Configuration
 description:
   Explore the advanced configuration options for integrating Web3Telegram. Learn
-  how to customize the dApp address, whitelist, subgraph, IPFS node, and more
+  how to customize the iApp address, whitelist, subgraph, IPFS node, and more
   for secure Telegram communication on the iExec blockchain.
 ---
 
@@ -21,12 +21,12 @@ import { type Web3TelegramConfigOptions } from '@iexec/web3telegram';
 ### dappAddressOrENS
 
 The Ethereum contract address or ENS (Ethereum Name Service) for the
-web3telegram dApp.
+web3telegram iApp.
 
 If not provided, the default ENS `web3telegram.apps.iexec.eth` pointing to the
-latest version of the web3telegram dApp provided by iExec will be used.
+latest version of the web3telegram iApp provided by iExec will be used.
 
-You can find the corresponding dApp address with Bellecour explorer:
+You can find the corresponding iApp address with Bellecour explorer:
 [https://explorer.iex.ec/bellecour/search/web3telegram.apps.iexec.eth](https://explorer.iex.ec/bellecour/search/web3telegram.apps.iexec.eth).
 
 ```ts twoslash
@@ -41,9 +41,9 @@ const web3telegram = new IExecWeb3telegram(web3Provider, {
 
 ### dappWhitelistAddress
 
-The Ethereum contract address for the web3telegram dApps whitelist. By granting
+The Ethereum contract address for the web3telegram iApp whitelist. By granting
 access to a whitelist, Chat Id owners ensure their Chat Id is still available to
-consumers even after a new version of web3telegram dApp gets released.
+consumers even after a new version of web3telegram iApp gets released.
 
 If not provided, the default whitelist smart contract address provided by iExec
 will be used.

From 0236eb74b31d8e1294f44ca767d615c05150e51b Mon Sep 17 00:00:00 2001
From: Le-Caignec <robinlecaignec@yahoo.fr>
Date: Mon, 18 Aug 2025 13:06:29 +0200
Subject: [PATCH 22/27] docs: enhance clarity and readability in various
 documentation files by fixing whitespace and rephrasing sentences

---
 .../tooling-and-explorers/blockchain-explorer.md          | 4 ++--
 .../build-iapp/advanced/quick-start-for-developers.md     | 6 +++---
 .../dataProtector/dataProtectorCore/grantAccess.md        | 8 ++++----
 3 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/src/get-started/tooling-and-explorers/blockchain-explorer.md b/src/get-started/tooling-and-explorers/blockchain-explorer.md
index c891f704..064acc19 100644
--- a/src/get-started/tooling-and-explorers/blockchain-explorer.md
+++ b/src/get-started/tooling-and-explorers/blockchain-explorer.md
@@ -39,8 +39,8 @@ publicly auditable.
 
 ::: tip 💡 Dev Tip
 
-Use **Bellecour** for development and testing as it's a gas-free blockchain, then
-deploy to **Arbitrum** for production workloads.
+Use **Bellecour** for development and testing as it's a gas-free blockchain,
+then deploy to **Arbitrum** for production workloads.
 
 :::
 
diff --git a/src/guides/build-iapp/advanced/quick-start-for-developers.md b/src/guides/build-iapp/advanced/quick-start-for-developers.md
index 5b1027a1..08a45b38 100644
--- a/src/guides/build-iapp/advanced/quick-start-for-developers.md
+++ b/src/guides/build-iapp/advanced/quick-start-for-developers.md
@@ -23,9 +23,9 @@ iexec --help
 ## Create your identity on the blockchain
 
 On the blockchain, your identity is defined by your **wallet,** consisting of
-cryptographically encrypted **private key** and **public address.** What you
-own on the blockchain is associated with your address. The applications you
-deploy on iExec are associated with your wallet.
+cryptographically encrypted **private key** and **public address.** What you own
+on the blockchain is associated with your address. The applications you deploy
+on iExec are associated with your wallet.
 
 Let's set up your wallet.
 
diff --git a/src/references/dataProtector/dataProtectorCore/grantAccess.md b/src/references/dataProtector/dataProtectorCore/grantAccess.md
index a8df83f4..67462f07 100644
--- a/src/references/dataProtector/dataProtectorCore/grantAccess.md
+++ b/src/references/dataProtector/dataProtectorCore/grantAccess.md
@@ -95,10 +95,10 @@ data.
 iExec uses the ENS `web3mail.apps.iexec.eth` for the latest version of the
 Web3Mail decentralized application.
 
-iExec also maintains a whitelist for current and past versions of Web3Mail
-iApp. Granting access to this whitelist allows use of an email `protectedData`
-with all versions of the Web3Mail application, ensuring you only have to grant
-this access once. The ETH address for this whitelist is
+iExec also maintains a whitelist for current and past versions of Web3Mail iApp.
+Granting access to this whitelist allows use of an email `protectedData` with
+all versions of the Web3Mail application, ensuring you only have to grant this
+access once. The ETH address for this whitelist is
 **0x781482C39CcE25546583EaC4957Fb7Bf04C277D2**.
 
 :::

From d45d09c0e98c854dde47504a20c3a8ab78a68317 Mon Sep 17 00:00:00 2001
From: Le-Caignec <robinlecaignec@yahoo.fr>
Date: Mon, 18 Aug 2025 13:10:55 +0200
Subject: [PATCH 23/27] chore: update .gitignore to simplify style
 configuration exclusions

---
 .gitignore | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.gitignore b/.gitignore
index 0deadf0d..f7adcebd 100644
--- a/.gitignore
+++ b/.gitignore
@@ -14,5 +14,5 @@ components.d.ts
 .DS_Store
 
 #vale
-.github/styles/config/*
+.github/styles/*
 !.github/styles/config/vocabularies/

From d10581a14cbc7f203e5edc8f68f945cf945c4985 Mon Sep 17 00:00:00 2001
From: Le-Caignec <robinlecaignec@yahoo.fr>
Date: Mon, 18 Aug 2025 15:22:09 +0200
Subject: [PATCH 24/27] docs: add Vale report generation instructions and
 enhance documentation on Oracle protocol

---
 .gitignore                                    |   1 +
 .vitepress/sidebar.ts                         |  12 +-
 README.md                                     |  26 ++
 src/get-started/protocol/oracle.md            | 327 ++++++++++++++++
 .../protocol/proof-of-contribution.md         | 359 +++++++++---------
 5 files changed, 541 insertions(+), 184 deletions(-)
 create mode 100644 src/get-started/protocol/oracle.md

diff --git a/.gitignore b/.gitignore
index f7adcebd..a8039465 100644
--- a/.gitignore
+++ b/.gitignore
@@ -16,3 +16,4 @@ components.d.ts
 #vale
 .github/styles/*
 !.github/styles/config/vocabularies/
+vale-report.txt
diff --git a/.vitepress/sidebar.ts b/.vitepress/sidebar.ts
index db1c5bf1..cf83a599 100644
--- a/.vitepress/sidebar.ts
+++ b/.vitepress/sidebar.ts
@@ -110,19 +110,23 @@ export function getSidebar() {
             link: '/get-started/protocol/proof-of-contribution',
           },
           {
-            text: '💸 Pay Per Task Model',
+            text: 'Pay Per Task Model',
             link: '/get-started/protocol/pay-per-task',
           },
           {
-            text: '⚙️ Workers & Workerpools',
+            text: 'Oracle',
+            link: '/get-started/protocol/oracle',
+          },
+          {
+            text: 'Workers & Workerpools',
             collapsed: true,
             items: [
               {
-                text: '🚀 Worker Quick Start',
+                text: 'Worker Quick Start',
                 link: '/get-started/protocol/worker/quick-start',
               },
               {
-                text: '🔒 Manage Workerpool Access',
+                text: 'Manage Workerpool Access',
                 link: '/get-started/protocol/worker/manage-access',
               },
             ],
diff --git a/README.md b/README.md
index 97fdee71..8c4701cd 100644
--- a/README.md
+++ b/README.md
@@ -49,6 +49,9 @@ vale src/get-started/helloWorld/1-overview.md
 
 # Get detailed output
 vale --output=line src/
+
+# Generate comprehensive report with statistics
+vale --output=line src/ > vale-report.txt 2>&1
 ```
 
 #### Vale Rules
@@ -61,6 +64,29 @@ ensure:
 - Professional tone
 - Accessibility best practices
 
+#### Vale Statistics and Reports
+
+Generate comprehensive reports to track documentation quality:
+
+**Current Statistics (as of latest run):**
+
+- **Total Issues**: 2,731
+- **Top Issues**:
+  - Headings capitalization (622)
+  - Acronyms explanation (472)
+  - Passive voice (460)
+  - Word choice (294)
+  - Parentheses usage (244)
+
+**Files with Most Issues:**
+
+1. `proof-of-contribution.md` (323 issues)
+2. `glossary.md` (143 issues)
+3. `quick-start-for-developers.md` (75 issues)
+
+**Quality Score**: Based on the number of issues per file, we can calculate a
+quality percentage and track improvements over time.
+
 ### Environment Variables (Optional)
 
 Some features of the application require environment variables. This
diff --git a/src/get-started/protocol/oracle.md b/src/get-started/protocol/oracle.md
new file mode 100644
index 00000000..fc6ecb85
--- /dev/null
+++ b/src/get-started/protocol/oracle.md
@@ -0,0 +1,327 @@
+---
+description: A flexible and secure Oracle Solution
+---
+
+# iExec Oracle
+
+> A flexible and secure Oracle Solution
+
+## Why do we need Oracles?
+
+The Ethereum blockchain provides a global trustless computer: given some input
+and the smart contract code, the blockchain guarantees execution according to
+the Ethereum specification, by replicating the execution across thousands of
+nodes and implementing a consensus mechanism across all these nodes. Hence the
+execution of the contract decentralizes, and will happen without the need to
+trust any single actor.
+
+Unfortunately decentralizing the execution is not sufficient. To be of any
+real-world use, a smart contract most often requires access to external,
+real-world information. For example an insurance smart contract could require
+data about the weather to trigger payment, or a hedging contract could require
+pricing data. This information is already available in the digital world: the
+web 2.0 is full of nice APIs that provide all kinds of data. It is however not
+straightforward to put this information on the blockchain: if the update message
+comes from a single wallet, then this wallet controls the whole execution
+outcome. It means the smart contract has to trust an off-chain actor \(the owner
+of an Ethereum wallet\) to provide such information, which defeats the purpose
+of decentralization: now the information provider becomes the trusted third
+party that decentralization was supposed to do away with in the first place!
+
+Oracles are systems designed to solve this problem: providing the blockchain
+with data from the real world in the most secure and robust way possible. It
+turns out we at iExec have been working on this problem for a long time. Indeed
+an update to an Oracle \(for example the price of a stock or the average
+temperature for a day\) can appear as the result of a specific type of
+off-chain computation, one that would involve calling an API and processing the
+response to return the final result. As a result the iExec infrastructure is
+perfectly suited to build an efficient and secure Oracle system: the iExec
+Oracle.
+
+## The iExec solution: the Decentralized Oracle \(Oracle\)
+
+For two years iExec has been working on the design of the
+[Proof of Contribution protocol](/get-started/key-concepts/proof-of-contribution.md),
+which provides a flexible and highly robust solution to the problem of off-chain
+computation. At its core it is a simple Schelling game between off-chain
+computation providers \(Workers\): a given number of Workers are randomly chosen
+in a much bigger group, and receive the same computation. Each of them
+proposes a result, and the result that proposed by the biggest number of
+workers becomes the overall computation result \(see PoCo documentation for
+more details\).
+
+The PoCo is both flexible and robust: the trust level for the computation \(e.g.
+for the Oracle update in the Oracle case\) can set arbitrarily, and
+determines the number of replications. It also includes a coherent on-chain
+incentive mechanism, that protects the whole system against any \(financially
+sustainable\) attack. Last but not least, it is cheap and scalable: the more
+Workers join the iExec platform, the more secure and the cheaper running a
+Oracle will be. iExec Oracle relies on random sampling among all the Workers on
+the iExec platform, along with an on-chain consensus algorithm and an integrated
+trust score system to make an attack on the Oracle result exponentially
+expensive.
+
+iExec Oracle builds on top of the decentralized cloud computing platform
+developed by iExec to allow developers to easily create robust and secure
+decentralized oracle. Building an Oracle with iExec is therefore extremely
+simple: just create a dApp with the logic of the Oracle \(querying an API,
+processing different results into a final one\); the iExec platform will
+automatically replicate it across many different workers; then the PoCo will
+realize a consensus on the different values. The whole process is simple and as
+secure as you wish - provided enough money pays for each execution / oracle
+update.
+
+### Why you should use iExec Oracle
+
+iExec Oracle allows you to create your own Oracle, with custom logic, while
+benefiting from the security guarantees of the whole iExec platform.
+
+- It is secure. You can set the desired level of trust for your Oracle
+  execution. The conjunction of random sampling and iExec’s built-in incentive
+  and reputation systems makes your Oracle highly secured.
+- It is easy-to-use. It relies on 2 years of research and development to make
+  the iExec platform simple and developer friendly. Creating your own
+  personalized Decentralized Oracle only takes a simple dockerized application
+  and a few lines of Solidity!
+- It is cheap. It does not rely on bribing or incentivizing honest behavior,
+  only on random sampling and a powerful reputation system to make attack
+  impractical.
+
+## How does it work?
+
+### Background: task execution on the iExec platform
+
+The iExec architecture is two-sided: the on-chain part is a set of smart
+contracts that implement the PoCo, handle the incentive and adjudication
+systems; and the off-chain part consists of workers, that provide computing
+resources to execute the tasks, and schedulers, that dispatch the tasks to
+execute between the workers of the worker-pool they manage. Each side of the
+iExec platform \(worker-pool, computation requester\) create and sign orders
+that describe the kind of transaction they are willing to enter \(type of
+hardware, minimum price, etc…\). When several orders of different types are
+compatible they match together on the blockchain, to create a deal. Once a
+deal creates, the scheduler that is part of the deal will choose a set of
+workers in his workerpool to execute the task. Each worker will download the
+dApp \(a docker container\) and run it. Upon execution of the task, each worker
+sends back two values on the blockchain:
+
+- a hash of the result.
+- after consensus reaches, the corresponding result.
+
+A normal execution ends when the deal finalizes; all the stakeholders are
+paid, and the computation requester is free to download the data pointed to by
+the results field of the `Deal` object on the blockchain.
+
+### iExec d'Oracle: general architecture
+
+An iExec Oracle can appear as an “on-chain API”: fundamentally it is a simple
+value-store smart contract, with accessors for other smart contracts to get its
+data, and an internal mechanism to update the data in the most secure way
+possible. The Oracle architecture consists of two parts: an on-chain smart
+contract and a classical iExec dApp \(packaged in a docker container\).
+
+**Off-chain component:**
+
+The off-chain part of a Oracle is a classical iExec dApp, that will execute
+on the iExec platform and replicate on several workers as part of an iExec
+computation deal. It contains the oracle logic, for example to query a web API
+and process the result. Whenever an operator wishes to update the Oracle, it
+requests a computation like in a normal iExec deal, specifying the Oracle app as
+dApp, and the parameters if applicable. The Oracle result writes in the
+`${IEXEC_OUT}/computed.json` file by the dApp, under the `callback_data` key.
+
+```bash
+$ cat ${IEXEC_OUT}/computed.json
+{ 'callback-data': '0x48656c6c6f2c20776f726c6421'}
+```
+
+When the computation ends the worker will send both this `callback-data`
+\(containing the oracle result\) on the blockchain. The `callback-data` value is
+stored in the `resultsCallback` field of the `Task` object in the `IexecProxy`
+smart contract.
+
+**On-chain component:**
+
+The on-chain part is the Oracle contract. Anyone can request an update of its
+internal state by sending the id of a task corresponding to the execution of the
+corresponding dApp. With this id, the Oracle contract will query the blockchain
+and retrieve the deal object. It then checks that the execution passes the
+Oracle requirements \(trust level, execution tag, that the app is right\). If it
+does the Oracle contract then decodes the value in the results field and update
+its fields accordingly. The value is then accessible like a normal value on a
+smart contract.
+
+## Example: development and workflow of a price-feed application
+
+A simple example of Oracle is available on Github. The following section goes
+through its different components, explaining what each of them does.
+
+### The PriceFeed dApp
+
+The PriceFeed dApp is a simple Node.js script, available at
+[Kaiko PriceFeed Source](https://github.com/iExecBlockchainComputing/iexec-apps/blob/master/offchain-computing/offchain-tee-kaiko-pricefeed/src/app.py).
+Given a set of parameters, the application encodes its result so that it can be
+interpreted by the corresponding Oracle smart contract, stores it in
+`${IEXEC_OUT}/computed.json`, and stores the hash of this encoded value to
+perform the consensus. The Worker will then send these values on-chain as part
+of the task finalization, where they will be accessible by the Oracle smart
+contract.
+
+For example, given the parameters `"BTC USD 9 2019-04-11T13:08:32.605Z"` the
+price-oracle application will:
+
+- Retrieve the price of BTC in USD at 2019-04-11T13:08:32.605Z
+- Multiply this value by `10e9` \(to capture the price value more accurately as
+  it will represent by an integer onchain\)
+- Encode the date, the description \(`"btc-usd-9"`\) and the value using
+  `abi.encode`
+- Store this result in `${IEXEC_OUT}/computed.json` under the `callback-data`
+  key
+
+iExec will then achieve PoCo consensus on the hash of the `callback-data` value,
+and will then submit `callback-data` values on-chain, in the `Task` object on
+the `IexecProxy` smart contract.
+
+Once your oracle dApp writes, you can build it into a Docker image and make
+it available on the iExec platform as explained here.
+
+### The Oracle generic contract
+
+Every Oracle must inherit from the `IexecDoracle` contract \(source available on
+[Github](https://github.com/iExecBlockchainComputing/iexec-Oracle-base) and
+[npm](https://www.npmjs.com/package/iexec-Oracle-base)\).
+
+This contract stores the following fields:
+
+```text
+IexecInterfaceToken public iexecproxy;
+address             public m_authorizedApp;
+address             public m_authorizedDataset;
+address             public m_authorizedWorkerpool;
+bytes32             public m_requiredtag;
+uint256             public m_requiredtrust;
+```
+
+In particular, the `m_authorizedApp` must be the address of the smart contract
+of the Oracle dApp, and the `m_requiredtag` describes the parameters of the
+iExec `Task` necessary to validate the Oracle update.
+
+The Oracle exposes mainly three internal functions, that may use by the
+contracts that inherit from it:
+
+A constructor:
+
+```text
+constructor(address _iexecproxy) public
+```
+
+A function to initialize/update the settings:
+
+```text
+function _iexecDoracleUpdateSettings(
+        address _authorizedApp
+,       address _authorizedDataset
+,       address _authorizedWorkerpoo
+,       bytes32 _requiredtag
+,       uint256 _requiredtrust
+)
+internal
+```
+
+The update function, that takes in input a task id, and reads the `Task` object
+data from the `IexecProxy` smart contract to perform the required checks (the
+execution must complete; the app, the dataset, and the workerpool must be
+authorized; the trust level and tags mus be valid). The `IexecProxy` already
+checked that the hash of the `resultsCallback` is equal to the `resultDigest`
+\(over which the consensus reached\). If the task passes the checks then it
+returns the `results` field of the `Task` object, i.e. the result of the Oracle
+dApp computation.
+
+```text
+function _iexecDoracleGetVerifiedResult(bytes32 _doracleCallId)
+internal view returns (bytes memory)
+```
+
+A Oracle smart contract should inherit from the generic `IexecDOracle` contract,
+and expose two main functionalities:
+
+- An update function, that will call the internal \(and inherited\)
+  `_iexecDoracleGetVerifiedResult` function and process its result to update the
+  Oracle contract internal state.
+- One or several accessor functions, that allows other smart contract to access
+  the oracle value\(s\).
+
+### The PriceOracle Oracle contract
+
+In the PriceFeed example, the
+[PriceOracle](https://github.com/iExecBlockchainComputing/iexec-Oracle-base/blob/bb4c04dc77c822d16d7ca8baed99f5626e44d7be/contracts/example/PriceOracle.sol)
+smart contract consists of three parts:
+
+- Its internal state description: a `TimedValue` struct storing the oracle data
+  for a given value, and a `values` field that maps an index of the form
+  `“BTC-USD-9”` to the corresponding `TimedValue` struct value.
+
+```text
+struct TimedValue
+{
+        bytes32 oracleCallID;
+        uint256 date;
+        uint256 value;
+        string  details;
+}
+
+mapping(bytes32 => TimedValue) public values;
+```
+
+This also allows to read the resulting prices. For example, to get the most
+recent price of BTC in USD with 9 place precision \(as described above\), query
+`values(keccak256(bytes("BTC-USD-9")))` from the Oracle contract and this will
+return a structure containing the value, the associated date, and the details of
+the request.
+
+- The update function `processResult`, that takes the task id of an execution of
+  the Oracle dApp, calls the internal `_iexecDoracleGetVerifiedResult` and
+  processes the result to update the `values` map.
+
+```text
+function processResult(bytes32 _oracleCallID)
+public
+{
+        uint256       date;
+        string memory details;
+        uint256       value;
+
+        // Parse results
+        (date, details, value) = decodeResults(_iexecDoracleGetVerifiedResult(_oracleCallID));
+
+        // Process results
+        bytes32 id = keccak256(bytes(details));
+        require(values[id].date < date, "new-value-is-too-old");
+        emit ValueChange(id, _oracleCallID, values[id].date, values[id].value, date, value);
+        values[id].oracleCallID = _oracleCallID;
+        values[id].date         = date;
+        values[id].value        = value;
+        values[id].details      = details;
+}
+```
+
+The PriceFeed Oracle also declares an event `ValueChange`, that fires
+whenever an update creates.
+
+- An `updateEnv` function, that can use by the owner of the Oracle to update
+  its parameters. It simply calls the `_iexecDoracleUpdateSettings` function of
+  its parent `IexecDoracle` contract.
+
+```text
+function updateEnv(
+        address _authorizedApp
+,       address _authorizedDataset
+,       address _authorizedWorkerpool
+,       bytes32 _requiredtag
+,       uint256 _requiredtrust
+)
+public onlyOwner
+{
+        _iexecDoracleUpdateSettings(_authorizedApp, _authorizedDataset, _authorizedWorkerpool, _requiredtag, _requiredtrust);
+}
+```
diff --git a/src/get-started/protocol/proof-of-contribution.md b/src/get-started/protocol/proof-of-contribution.md
index a594403b..5af1ae70 100644
--- a/src/get-started/protocol/proof-of-contribution.md
+++ b/src/get-started/protocol/proof-of-contribution.md
@@ -12,64 +12,63 @@ description:
 
 The iExec platform provides a network where application providers, workers, and
 users can gather and work together. The fully decentralized nature of iExec
-implies that no single agent is trusted by default, and that those agents
+implies that the system trusts no single agent by default, and that those agents
 require incentives to contribute correctly.
 
-In this context, Proof-of-Contribution (PoCo) is the protocol used by iExec for
-consensus over off-chain computing.
+In this context, Proof-of-Contribution (PoCo) is the protocol that iExec uses
+for consensus over off-chain computing.
 
 ## Protocol
 
 ### Objectives
 
-PoCo is a protocol designed to provide trust in an open and decentralized
-environment of untrusted machines.
+PoCo is a protocol that provides trust in an open and decentralized environment
+of untrusted machines.
 
 In addition to providing trust, PoCo also orchestrates the different
-contributions to the iExec network, ensuring payments are always fair and
+contributions to the iExec network and ensures payments are always fair and
 timely.
 
-A major quality of PoCo lies in the fact that it is a modular protocol. It comes
-with features that are context-specific.
+A major quality of PoCo is its modular design. It comes with features that are
+context-specific.
 
 ### Result consolidation
 
 PoCo relies on replication to achieve result consolidation. This is purely a
 software solution that enforces a confidence level on the result.
-[This confidence level can be customized by the requester.](proof-of-contribution.md#replication-and-trust)
+[The requester can customize this confidence level.](proof-of-contribution.md#replication-and-trust)
 
-This layer also supports the onchain consolidation of execution results carried
-out in Trusted Execution Environments (TEE) such as Intel SGX.
+This layer also supports the onchain consolidation of execution results that
+Trusted Execution Environments (TEE) such as Intel SGX carry out.
 
 ### Secure payment
 
-Once a deal is sealed on the iExec Marketplace, requester funds are locked to
-ensure all resource providers are paid for their contributions. Resources can
-take the form of data, applications or computing power.
+Once the iExec Marketplace seals a deal, the system locks requester funds to
+ensure all resource providers receive payment for their contributions. Resources
+can take the form of data, applications or computing power.
 
 Workers must achieve consensus on the execution result to get the requester’s
-funds. If consensus is not achieved, the requester is reimbursed.
+funds. If consensus is not achieved, the system reimburses the requester.
 
 Worker and scheduler must stake RLC to participate as computing providers. Bad
 behaviour from an actor results in a loss of stake.
 
-This is essential on the public blockchain, but all values can be set to 0 for
+This is essential on the public blockchain, but you can set all values to 0 for
 private blockchain networks.
 
 ### Permissioning
 
-For an execution to happen, a deal must be signed between the different parties
-involved. A permission mechanism can be used to control access to applications,
-datasets and worker pools.
+For an execution to happen, the different parties involved must sign a deal. A
+permission mechanism controls access to applications, datasets and worker pools.
 
-The secure payment layer can be disabled for a private blockchain, or it can
-also be used in the context of the public blockchain to increase security. An
+You can disable the secure payment layer for a private blockchain, or you can
+also use it in the context of the public blockchain to increase security. An
 example of permissioning is dataset restriction for a specific application.
 
 ### Overview
 
-PoCo describes the succession of contributions that are required to achieve
-consensus on a given result. Its logic is detailed in two blog articles:
+PoCo describes the succession of contributions that you need to achieve
+consensus on a given result. Two blog articles detail its logic:
 
 - [PoCo series #1: Initial PoCo description](https://medium.com/iex-ec/about-trust-and-agents-incentives-4651c138974c)
 - [PoCo series #3: Updated PoCo description](https://medium.com/iex-ec/poco-series-3-poco-protocole-update-a2c8f8f30126)
@@ -82,13 +81,14 @@ Below are the details of the implementations:
 
 **1. Deal:**
 
-[A deal is sealed by the Clerk.](proof-of-contribution.md#brokering) This marks
-the beginning of the execution. An event is created to notify the worker pool’s
-scheduler.
+[The Clerk seals a deal.](proof-of-contribution.md#brokering) This marks the
+beginning of the execution. The system creates an event to notify the worker
+pool’s scheduler.
 
-The consensus timer starts when the deal is signed. The corresponding task must
-be completed before the end of this countdown. Otherwise, the scheduler gets
-punished by a loss of stake and reputation, and the user reimbursed.
+The consensus timer starts when the parties sign the deal. The corresponding
+task must complete before the end of this countdown. Otherwise, the scheduler
+gets punished by a loss of stake and reputation, and the system reimburses the
+user.
 
 **2. Initialization:**
 
@@ -102,47 +102,47 @@ _taskid_.`bytes32 taskid = keccak256(abi.encodePacked(_dealid, idx));`
 The scheduler designates workers that participate in this task. The scheduler’s
 Ethereum wallet signs a message containing the worker’s Ethereum address, the
 taskid, and (optionally) the Ethereum address of the worker's enclave. If the
-worker doesn't use an enclave, this field must be filled with `address(0)`.
+worker doesn't use an enclave, you must fill this field with `address(0)`.
 
-This Ethereum signature (authorization) is sent to the worker through an
-off-chain channel implemented by the middleware.
+This Ethereum signature (authorization) goes to the worker through an off-chain
+channel implemented by the middleware.
 
 **4. Task computation:**
 
-Once the authorization is received and verified, the worker computes the
-requested tasks. Results from this execution are placed in the `/iexec_out`
-folder. The following values are then computed:
+Once the worker receives and verifies the authorization, the worker computes the
+requested tasks. Results from this execution go in the `/iexec_out` folder. The
+following values are then computed:
 
 - _bytes32 digest_: a digest (sha256) of the result folder.
-- _bytes32 hash_: the hash of the _digest_, used to produce a consensus
-- _bytes32 seal_: the salted hash of the _digest_, used to prove a worker’s knew
-  the _digest_ value before it is published.
+- _bytes32 hash_: the hash of the _digest_, that produces consensus
+- _bytes32 seal_: the salted hash of the _digest_, that proves a worker’s knew
+  the _digest_ value before publishing it.
   `resultHash == keccak256(abi.encodePacked( taskid, resultDigest))`
   `resultSeal == keccak256(abi.encodePacked(worker, taskid, resultDigest))`
 
 In computer science, a deterministic algorithm is an algorithm which, given a
 particular input, will always produce the same output.
 
-Both the `digest`, the `hash` and the `seal` are automatically computed based on
-the output of the application. If the output is not entirely deterministic, then
-the application can specify a deterministic file that should be used for
-building consensus. In order to do so, the application just has to provide the
-path to the deterministic file using a specific entry
-`deterministic-output-path` in `${IEXEC_OUT}/computed.json`.
+Both the `digest`, the `hash` and the `seal` compute automatically based on the
+output of the application. If the output is not entirely deterministic, then the
+application can specify a deterministic file that should use for building
+consensus. In order to do so, the application just has to provide the path to
+the deterministic file using a specific entry `deterministic-output-path` in
+`${IEXEC_OUT}/computed.json`.
 
-Alternatively, if the application is used in a oracle context (the results are
-designed to be processed on-chain by receiver smart-contracts), then the value
-of this callback must be specified in `${IEXEC_OUT}/computed.json` under the
-entry `callback-data`.
+Alternatively, if you use the application in an oracle context (the results are
+designed to process on-chain by receiver smart-contracts), then the value of
+this callback must specify the value of in `${IEXEC_OUT}/computed.json` under
+the entry `callback-data`.
 
-If a TEE was used to produce the result, the post-processing enclave will
-automatically produce an `enclave-signature` entry that contains the enclave
-signature (of the resultHash and resultSeal). TEE certification of results is
-transparent to the application developer.
+If a TEE produces the result, the post-processing enclave will automatically
+produce an `enclave-signature` entry that contains the enclave signature (of the
+resultHash and resultSeal). TEE certification of results is transparent to the
+application developer.
 
 **5. Contribution:**
 
-Once the execution has been performed, the worker pushes its contribution using
+Once the worker performs the execution, the worker pushes its contribution using
 the `contribute` method. The contribution contains:
 
 - _bytes32 taskid_
@@ -151,49 +151,50 @@ the `contribute` method. The contribution contains:
 - _address enclaveChallenge_
 
 The address of the enclave (specified in the scheduler’s authorization). If no
-enclave is specified, this parameter should be set to `address(0)`.
+enclave specifies, you should set this parameter to `address(0)`.
 
 - _bytes enclaveSign_
 
-The enclave signature. This is required if the `enclaveChallenge` is not
-`address(0)`. Otherwise, it should be set to the empty byte string `0x`.
+The enclave signature. You need this if the `enclaveChallenge` is not
+`address(0)`. Otherwise, you should set it to the empty byte string `0x`.
 
 - _bytes workerpoolSign_
 
-The signature computed by the scheduler at step 2.
+The scheduler computes the signature at step 2.
 
 **6. Consensus:**
 
-During the contribution, the consensus is updated and verified. Contributions
-are possible until the consensus is reached, at which point the contributions
-are closed. We then enter a 2h reveal phase.
+During the contribution, the system updates and verifies the consensus.
+Contributions are possible until the system reaches consensus, at which point
+the contributions close. We then enter a 2h reveal phase.
 
 **7. Reveal:**
 
 During the reveal phase, workers that have contributed to the consensus must
-call the `reveal` method with the `resultDigest`. This verifies that the
-`resultHash` and `resultSeal` they provided are valid. Failure to reveal is
-equivalent to a bad contribution, and results in a loss of stake and reputation.
+call the `reveal` method with the `resultDigest`. This verification confirms
+that the `resultHash` and `resultSeal` they provided are valid. Failure to
+reveal is equivalent to a bad contribution, and results in a loss of stake and
+reputation.
 
 **8. Finalize:**
 
-Once all contributions have been revealed, or at the end of the reveal period if
+Once the system reveals all contributions, or at the end of the reveal period if
 some (but not all) reveals are missing, the scheduler must call the `finalize`
-method. This finalizes the task, rewards good contribution and punishes bad
-ones. This must be called before the end of the consensus timer.
+method. This task finalization, rewards good contribution and punishes bad ones.
+You must call this before the end of the consensus timer.
 
 ### Staking and Payment
 
 Among the objectives of PoCo, we want to ensure a worker that contributes
-correctly is rewarded and, at the same time, that a requester won’t be charged
-unless a consensus is achieved. This is achieved by locking the requester’s
+correctly receives a reward and, at the same time, that a requester won’t pay
+unless the system achieves consensus. This locking achieves the requester’s
 funds for the duration of the consensus, and unlocking them depending on the
 outcome.
 
-Staking is used to prevent bad behavior and encourage good contributions.
+Staking prevents bad behavior and encourage good contributions.
 
 Your account, managed by the `Escrow` part of the `IexecClerk`, separates
-between `balance.stake` (available, can be withdrawn) and `balanced.locked`
+between `balance.stake` (available, can be withdrawn) and `balance.locked`
 (unavailable, frozen by a running task). The `Escrow` exposes the following
 mechanism:
 
@@ -206,29 +207,29 @@ mechanism:
 `unlock`: Moves value from the `balance.lock` back to the `balance.stake`
 
 - Unlock the requester stake when consensus fails
-- Unlock the scheduler stake when consensus is achieved
+- Unlock the scheduler stake when the system achieves consensus
 - Unlock the worker stake when they contributed to a successful consensus
 
 `seize`: Confiscate value from `balance.lock`
 
-- Seize the requester stake when the consensus is achieved (payment)
+- Seize the requester stake when the system achieves consensus (payment)
 - Seize the scheduler stake when consensus fails (send to the reward kitty)
 - Seize the worker stake when a contribution fails (redistributed to the other
   workers in the task)
 
 `reward`: Award value to the `balance.stake`
 
-- Reward the scheduler when consensus is achieved
+- Reward the scheduler when the system achieves consensus
 - Reward the worker when they contributed to a successful consensus
 - Reward the app and dataset owner
 
-The requester payment is composed of 3 parts, one for the worker pool, one for
-the application and one for the dataset. When a consensus is finalized, the
-payment is seized from the requester and the application and dataset owners are
-rewarded accordingly. The worker pool part is put inside the `totalReward`.
-Stake from the losing workers is also added to the `totalReward`. The scheduler
-takes a fixed portion of the `totalReward` as defined in the worker pool smart
-contract (`schedulerRewardRatioPolicy`).
+The requester payment consists of 3 parts, one for the worker pool, one for the
+application and one for the dataset. When a consensus finalizes, the payment
+seizes from the requester and the application and dataset owners are rewarded
+accordingly. The worker pool part puts inside the `totalReward`. Stake from the
+losing workers also adds to the `totalReward`. The scheduler takes a fixed
+portion of the `totalReward` as defined in the worker pool smart contract
+(`schedulerRewardRatioPolicy`).
 
 The remaining reward is then divided between the successful workers
 proportionally to the impact their contribution made on the consensus. If there
@@ -241,43 +242,43 @@ The scheduler also gets part of the reward kitty.
 `REVEAL_DEADLINE_RATIO = 2`
 
 Parameters of the consensus timer. They express the number of reference timers
-(category duration) that are dedicated to each phase. These settings correspond
-to a 70%-20%-10% distribution between the contribution phase, the reveal phase
-and the finalize phase.
+(category duration) that dedicate to each phase. These settings correspond to a
+70%-20%-10% distribution between the contribution phase, the reveal phase and
+the finalize phase.
 
 - `FINAL_DEADLINE_RATIO` This describes the total duration of the consensus. At
-  the end of this timer the consensus must be finalized. If it is not, the user
-  can make a claim to get a refund.
+  the end of this timer the consensus must finalize. If it is not, the user can
+  make a claim to get a refund.
 - `CONTRIBUTION_DEADLINE_RATIO` This describes the duration of the contribution
   period. The consensus can finalize before that, but no contribution will be
-  allowed after the timer to ensure enough time is left for the reveal and
+  allowed after the timer to ensure enough time leaves for the reveal and
   finalize steps.
 - `REVEAL_DEADLINE_RATIO` This describes the duration of the reveal period.
   Whenever a contribution triggers a consensus, a reveal period of this duration
-  is reserved for the workers to reveal their contribution. Note that this
-  period will necessarily start before the end of the contribution phase.
+  reserves for the workers to reveal their contribution. Note that this period
+  will necessarily start before the end of the contribution phase.
 
 Let's consider a task of category GigaPlus, which reference duration is 1 hour.
-If the task was submitted at 9:27AM, the contributions must be sent before
-4:27PM (16:27). Whenever a contribution triggers a consensus, a 2 hours long
-reveal period will start. Whatever happens, the consensus has to be achieved by
-7:27PM (19:27).
+If the task submitted at 9:27AM, the contributions must send before 4:27PM
+(16:27). Whenever a contribution triggers a consensus, a 2 hours long reveal
+period will start. Whatever happens, the consensus has to achieve by 7:27PM
+(19:27).
 
 `WORKERPOOL_STAKE_RATIO = 30`
 
-Percentage of the worker pool price that has to be staked by the scheduler. For
+Percentage of the worker pool price that has to stake by the scheduler. For
 example, for a `20 RLC` task, with an additional `1 RLC` for the application and
 `5 RLC` for the dataset, the worker will have to lock `26 RLC` in total and the
 scheduler will have to lock (stake) `30% * 20 = 6 RLC`.
 
-This stake is lost and transferred to the reward kitty if the consensus is not
+This stake loses and transferred to the reward kitty if the consensus is not
 finalized by the end of the consensus timer.
 
 `KITTY_RATIO = 10`
 
 Percentage of the reward kitty for the scheduler per successful execution. If
-the reward kitty contains 42 RLC when a finalize is called, then the scheduler
-will get 4.2 extra RLC and the reward kitty will be left with 37.8 RLC.
+the reward kitty contains 42 RLC when a finalize calls, then the scheduler will
+get 4.2 extra RLC and the reward kitty will leave with 37.8 RLC.
 
 `KITTY_MIN = 1 RLC`
 
@@ -307,15 +308,15 @@ and `workerStakeRatioPolicy = 5%`.
   - The third worker (`score = 300 → power = 99`) contributes `42`. It also
     locks `7 RLC`.
 - After the third contribution, the value `42` has reached a `99.87%`
-  likelihood. Consensus is achieved and the two workers who contributed toward
-  `42` have to reveal.
+  likelihood. Consensus achieves and the two workers who contributed toward `42`
+  have to reveal.
 - After both workers reveal, the scheduler finalizes the task:
-  - The requester locked value of `21 RLC` is seized.
+  - The requester locked value of `21 RLC` seizes.
   - The dataset owner gets `1 RLC` for the use of its dataset.
-  - Stake from the scheduler is unlocked.
+  - Stake from the scheduler unlocks.
   - Stakes from workers 2 and 3 are also unlocked.
-  - The first worker stake is seized, and it loses a third of its score. The
-    corresponding `7 RLC` are added to the `totalReward`.
+  - The first worker stake seizes, and it loses a third of its score. The
+    corresponding `7 RLC` add to the `totalReward`.
   - We now have `totalReward = 27 RLC`:
     - We save 5% for the scheduler, `workersReward = 95% * 27 = 25.65 RLC`
     - Worker 2 has weight `log2(32) = 5` and worker 3 has a weight
@@ -341,10 +342,10 @@ the scoring function [[Trust2018]](proof-of-contribution.md#references).
 Each worker’s contribution has an associated credibility. This credibility
 derives from the worker’s history score. As described in
 [[Trust2018]](proof-of-contribution.md#references), a worker score is a positive
-integer that is incremented for each valid and verified contribution. In case of
-bad contribution, a worker loses one third of it’s score. This credibility can
-be expressed as a likelihood percentage but also as a weight value that can be
-used to detect consensus without resorting to floating point arithmetics, more
+integer that increments for each valid and verified contribution. In case of bad
+contribution, a worker loses one third of it’s score. This credibility can
+express as a likelihood percentage but also as a weight value that can be used
+to detect consensus without resorting to floating point arithmetics, more
 details in [[Trust2018]](proof-of-contribution.md#references).
 
 ### Requiring a trust level
@@ -354,12 +355,12 @@ way to combine worker’s contribution and to evaluate a result’s likelihood,
 requester can ask for the level of trust as an input for the PoCo processing, to
 impose a certain quality of service. The trust level corresponds to a minimum
 correctness likelihood that a result must achieve to be valid. For example, a
-trust level of 0 means any contribution would be accepted, regardless of the
-score of the worker proposing it. On the other hand a trust level of 99.99%
-means a result will only be accepted if the contribution towards it result shows
-a correctness probability higher than 99.99%.
+trust level of 0 means any contribution would accept, regardless of the score of
+the worker proposing it. On the other hand a trust level of 99.99% means a
+result will only accept if the contribution towards it result shows a
+correctness probability higher than 99.99%.
 
-The trust level is expressed, on-chain, by an integer `trust` such that
+The trust level expresses, on-chain, by an integer `trust` such that
 `threshold = 1 - 1 / trust`.
 
 | **Trust** | **PoCo enforced confidence threshold** |
@@ -399,18 +400,17 @@ interaction. We considered on-chain and off-chain approach and finally went for
 a solution where both the pairing and the order book are off-chain. It might
 sound counterintuitive, but it has many advantages.
 
-If the orders and the pairing are handled off-chain, how can we build an
-on-chain agreement knowing that all parties have agreed? Is there a threat to
-the platform security?
+If the orders and the pairing handle off-chain, how can we build an on-chain
+agreement knowing that all parties have agreed? Is there a threat to the
+platform security?
 
 This option relies on the use of cryptographic signatures for order
 authentication. We represent orders using structures containing all the required
 details. The hash of this structure uniquely identifies the order. The structure
 by itself is worthless as anyone could write and publish it. However, if we add
 a valid cryptographic signature (of the identifying hash), then the origin of
-the order can be certified with the same level of security as if it was
-published on-chain. This role is fulfilled by a smart-contract called the
-iExecClerk.
+the order can certify with the same level of security as if it was published
+on-chain. This role fulfills a smart-contract called the iExecClerk.
 
 An overview of the iExecODB (Open Decentralized Brokering) is available in this
 blog article:
@@ -423,7 +423,7 @@ As discussed earlier, iExec introduces the offchain signature of orders as a new
 core element of the iExec Open Decentralized Brokering, the iExec Clerk should
 match these orders. There are 4 types of orders corresponding to the 4 actors
 involved: the worker pool, the application, the dataset and the requester. Each
-order types has to follow a specific structure and is signed using
+order types has to follow a specific structure and uses
 [EIP-712](https://eips.ethereum.org/EIPS/eip-712) structure signature mechanism.
 
 ### Orders description
@@ -452,11 +452,11 @@ struct AppOrder
 - `tag` Special requirements for the application (see
   [tag](proof-of-contribution.md#tag)).
 - `datasetrestrict` Matching restrictions. Dataset or group of datasets that can
-  be matched. Let null value to disable.
+  match. Let null value to disable.
 - `workerpoolrestrict` Matching restrictions. Workerpool or group of worker
-  pools that can be matched. Let null value to disable.
+  pools that can match. Let null value to disable.
 - `requesterrestrict` Matching restrictions. Requester or group of requesters
-  that can be matched. Let null value to disable.
+  that can match. Let null value to disable.
 - `salt` A random value to ensure order uniqueness.
 - `sign` cryptographic signature of the order, the smart contract is securely
   linked to application owner.
@@ -484,12 +484,12 @@ struct DatasetOrder
 - `volume` Number of authorized uses (by this order).
 - `tag` Special requirements of the dataset (see
   [tag](proof-of-contribution.md#tag)).
-- `apprestrict` Matching restrictions. App or group of apps that can be matched.
-  Let null value to disable.
+- `apprestrict` Matching restrictions. App or group of apps that can match. Let
+  null value to disable.
 - `workerpoolrestrict` Matching restrictions. Workerpool or group of workerpools
-  that can be matched. Let null value to disable.
+  that can match. Let null value to disable.
 - `requesterrestrict` Matching restrictions. Requester or group of requesters
-  that can be matched. Let null value to disable.
+  that can match. Let null value to disable.
 - `salt` A random value to ensure order uniqueness.
 - `sign` cryptographic signature of the order, the smart contract is securely
   linked to dataset owner.
@@ -521,12 +521,12 @@ struct WorkerpoolOrder
   [tag](proof-of-contribution.md#tag)).
 - `category` Order category.
 - `trust` Trust level used to consolidated results.
-- `apprestrict` Matching restrictions. App or group of apps that can be matched.
-  Let null value to disable.
+- `apprestrict` Matching restrictions. App or group of apps that can match. Let
+  null value to disable.
 - `datasetrestrict` Matching restrictions. Dataset or group of datasets that can
-  be matched. Let null value to disable.
+  match. Let null value to disable.
 - `requesterrestrict` Matching restrictions. Requester or group of requesters
-  that can be matched. Let null value to disable.
+  that can match. Let null value to disable.
 - `salt` A random value to ensure order uniqueness.
 - `sign` cryptographic signature of the order, the smart contract is securely
   linked to worker pool manager.
@@ -560,11 +560,11 @@ struct RequestOrder
 - `appmaxprice` Maximum price allowed by the requester for the payment of the
   application.
 - `dataset` Address of the smart contract describing the dataset. Must be
-  registered in the DatasetRegistry. Null if no dataset is required.
+  registered in the DatasetRegistry. Null if no dataset requires.
 - `datasetmaxprice` Maximum price allowed by the requester for the payment of
   the dataset (if any).
 - `workerpool` Matching restrictions. Worker pool or group of worker pools that
-  are allowed to run tasks from this order. Leave null value to disable check.
+  can run tasks from this order. Leave null value to disable check.
 - `workerpoolmaxprice` Maximum price allowed by the requester for the payment of
   the execution (scheduler + workers).
 - `requester` Address of the requester (paying for the executions).
@@ -577,7 +577,7 @@ struct RequestOrder
 - `beneficiary` Address of the beneficiary of the computation. Used to require
   output data encryption.
 - `callback` Address to callback with the results (following EIP1154 interface).
-  Let empty (null) if no callback is required. Learn more about the callback
+  Let empty (null) if no callback requires. Learn more about the callback
   mechanism.
 - `params` Parameters of the application (application specific).
 - `salt` A random value to ensure order uniqueness.
@@ -604,18 +604,18 @@ feature.
 | …                                                                    | …                      |
 | `0x8000000000000000000000000000000000000000000000000000000000000000` | —                      |
 
-For orders matching, the worker pool order must enable all bits that are enabled
-in any of the app order, dataset order and requester order. Meaning that if the
-app order tag is `0x12 = 0x10 | 0x02`, the dataset order is `0x81 = 0x80 | 0x01`
-and the requester order is `0x03 = 0x02 | 0x01`, then the worker pool order
-must, at least, have a tag `0x93 = 0x80 | 0x10 | 0x02 | 0x01`.
+For orders matching, the worker pool order must enable all bits that enable in
+any of the app order, dataset order and requester order. Meaning that if the app
+order tag is `0x12 = 0x10 | 0x02`, the dataset order is `0x81 = 0x80 | 0x01` and
+the requester order is `0x03 = 0x02 | 0x01`, then the worker pool order must, at
+least, have a tag `0x93 = 0x80 | 0x10 | 0x02 | 0x01`.
 
 ### Matching Conditions
 
-In order to trigger an execution, a deal must be registered by the iExec Clerk.
-Deals are produced when orders are successfully matched by the clerk. A match
-requires 3 or 4 orders depending on the requester requirements, the dataset
-order is optional.
+In order to trigger an execution, a deal must register by the iExec Clerk. Deals
+are formed when orders are successfully matched by the clerk. A match requires 3
+or 4 orders depending on the requester requirements, the dataset order is
+optional.
 
 Orders compatibility required:
 
@@ -649,7 +649,7 @@ require(tag & ~_workerpoolorder.tag == 0x0);
 require(tag & ~_workerpoolorder.tag == 0x0);
 ```
 
-**5. If TEE tag is required, then application must be TEE compatible.**
+**5. If TEE tag requires, then application must be TEE compatible.**
 
 ```text
 require((tag ^ _apporder.tag)[31] & 0x01 == 0x0);
@@ -709,7 +709,7 @@ require(_checkIdentity(_datasetorder.requesterrestrict, _requestorder.requester,
 require(_checkIdentity(_workerpoolorder.requesterrestrict, _requestorder.requester, GROUPMEMBER_PURPOSE));
 ```
 
-**13. All resources must be registered in the corresponding registries.**
+**13. All resources must register in the corresponding registries.**
 
 ```text
 require(m_appregistry.isRegistered(_apporder.app));
@@ -717,7 +717,7 @@ require(m_datasetregistry.isRegistered(_datasetorder.dataset));
 require(m_workerpoolregistry.isRegistered(_workerpoolorder.workerpool));
 ```
 
-**14. All orders must be signed or presigned.**
+**14. All orders must sign or presigned.**
 
 ```text
 require(_checkPresignatureOrSignature(App(_apporder.app).m_owner(), _apporder.hash(), _apporder.sign));
@@ -735,7 +735,7 @@ require(_checkPresignatureOrSignature(_requestorder.requester, _requestorder.has
 **[Requester] How do I enable PoCo’s consolidation of results?**
 
 A requester can enable the trust layer of the PoCo by setting the trust value in
-the requestorder. As described here, the trust is defined with the required
+the requestorder. As described here, the trust defines with the required
 confidence level. If the requester wants à 99.99% confidence level on the
 results, it must set the `trust` field to `10000`.
 
@@ -744,7 +744,7 @@ determinism?**
 
 The PoCo requires an application to be deterministic for the replication layer
 to provide trust in the result. If an application is not deterministic,
-consensus cannot be achieved and replication is not necessary.
+consensus cannot achieve and replication is not necessary.
 
 In order to obtain a result, the requester must prevent replication by asking a
 `trust` value of `0`. To protect your result, the requester can ask to run in an
@@ -763,8 +763,8 @@ encrypted with, you have to set up the beneficiary address in the
 RequesterOrder.
 
 An application can only perform result encryption inside an enclave. No
-encryption key will be provided by the SMS to an application that doesn't run
-outside an enclave.
+encryption key provides the SMS to an application that doesn't run outside an
+enclave.
 
 **[Dataset owner] How do I limit the usage of my dataset to a specific
 application?**
@@ -772,20 +772,20 @@ application?**
 iExec’s Data wallet and Data store is a complete solution to monetize valuable
 datasets preserving privacy. Before uploading a dataset you should encrypt it
 using the iExec SDK. Through this process, the encryption key becomes the
-valuable data that has to be protected.
+valuable data that needs protection.
 
-The encryption key must be stored in an SMS and the address of the corresponding
-SMS recorded in the directory. The SMS stores this encryption key and will only
+The encryption key must store in an SMS and the address of the corresponding SMS
+recorded in the directory. The SMS stores this encryption key and will only
 communicate it to an application running in an enclave.
 
 Before a worker runs this application, the worker must first prove that its
 access is legitimate by providing the scheduler authorization. The SMS will
 verify that this authorization’s signature is valid and that the corresponding
-task is registered onchain. This means that any deal signed in the iExec Clerk
-will grant access to the dataset’s encryption key.
+task registers onchain. This means that any deal signed in the iExec Clerk will
+grant access to the dataset’s encryption key.
 
 Therefore, in order to restrict the dataset’s usage, the dataset owner should
-set up restriction before signing a brokering order. This is done through the
+set up restriction before signing a brokering order. This happens through the
 `apprestrict` field of the datasetorder. The dataset owner can deploy a
 `SimpleGroup` smart contract, have the `apprestrict` field point to it, and then
 whitelisting the applications that will have access to the dataset’s encryption
@@ -794,7 +794,7 @@ key.
 **[Scheduler] How do I protect myself from non-deterministic applications?**
 
 When a scheduler publishes an order, it makes a commitment to achieve consensus
-on any task that is part of a deal made. While everything is done to ensure an
+on any task that is part of a deal made. While everything happens to ensure an
 application cannot hurt a worker pool’s machines, not reaching the consensus
 would cause a loss of stake for the scheduler. The scheduler must therefore take
 action to prevent this.
@@ -809,59 +809,58 @@ A scheduler could therefore emit two kinds of workerpoolorder:
 - A workerpoolorder offering execution with the PoCo’s trust layer disabled
   (`trust = 0`) and accepting all applications (`apprestrict = 0`)
 - A workerpoolorder offering secure execution of whitelisted tasks. The
-  application whitelist would use the `GroupInterface` to be verified by the
-  iExec Clerk. This group could either be managed by the scheduler or by a
-  certification authority that would check application's determinism.
+  application whitelist would use the `GroupInterface` to verify by the iExec
+  Clerk. This group could either manage the scheduler or by a certification
+  authority that would check application's determinism.
 
 ## Other technical choices
 
 ### Callback
 
 Some requesters might want an onchain callback with the result of the execution.
-The callback mechanism is based on
-[[EIP-1154]](proof-of-contribution.md#references-1). The result is a `bytes`
-value that is set during the `finalize`. The `IexecProxy` implements both side
-of the [[EIP-1154]](proof-of-contribution.md#references-1).
+The callback mechanism uses [[EIP-1154]](proof-of-contribution.md#references-1).
+The result is a `bytes` value that is set during the `finalize`. The
+`IexecProxy` implements both side of the
+[[EIP-1154]](proof-of-contribution.md#references-1).
 
 **Pull:**
 
-Results are identified by their `taskid` and can be pulled through the
-`resultFor` method.
+Results identify by their `taskid` and can pull through the `resultFor` method.
 
 **Push:**
 
 In order to use the push approach, the requester can use the `callback` field to
 specify the address of a smart contract that implements the `receiveResult`
 method specified in [[EIP-1154]](proof-of-contribution.md#references-1). This
-method will be called during the finalization with a minimum of 200000 nanoRLC
-gas to proceed [[*]](proof-of-contribution.md#references-1).
+method calls during the finalization with a minimum of 200000 nanoRLC gas to
+proceed [[*]](proof-of-contribution.md#references-1).
 
 In order to protect the scheduler and the workers, any error raised during this
-callback will be disregarded and will not prevent the finalization from
-happening. The same mechanism goes for the callback running out of gas.
+callback ignores and will not prevent the finalization from happening. The same
+mechanism goes for the callback running out of gas.
 
 ### Consensus & Reveal duration
 
 When orders match, IexecClerk records the deal which details the parameters of
-the task. If a consensus on a result is achieved before the countdown, the task
-is successful. After the countdown, as no consensus is reached, the execution is
+the task. If a consensus on a result achieves before the countdown, the task is
+successful. After the countdown, as no consensus reaches, the execution is
 failed. The duration of the consensus timer is a balance between the quality of
 service offered to the requester (short timer) and the margin available for the
 scheduler and the worker to achieve consensus (and go through the reveal
 process).
 
-The maximum duration of a task is governed by the category the task fits in.
-While the consensus duration can obviously not be shorter than the task runtime,
-a significant margin is required for the scheduler to do its job correctly.
-Multiple workers are likely to contribute and extra time must be planed for the
-revealing and finalization steps.
+The maximum duration of a task governs the category the task fits in. While the
+consensus duration can obviously not be shorter than the task runtime, a
+significant margin requires for the scheduler to do its job correctly. Multiple
+workers are likely to contribute and extra time must plan for the revealing and
+finalization steps.
 
-The consensus timer starts when the deal is recorded by the IexecClerk.
+The consensus timer starts when the deal records the IexecClerk.
 
 In case of failure, the requester can claim the refund.
 
 In the v3-alpha version, this timer lasts for 10 category runtime, for all
-category. The reveal timer starts whenever a consensus is reached and determines
+category. The reveal timer starts whenever a consensus reaches and determines
 the time frame the workers have to reveal their contributions. This should be
 long enough for worker to have time to reveal while not being too long so that
 the requester waits too long for its result or the consensus fails because the
@@ -878,9 +877,9 @@ that would not reach consensus to drain money from the scheduler. This would
 force the scheduler to whitelist all applications thus reducing the usability of
 the platform. Seized stake from the scheduler goes into a specific account
 called the _reward kitty_. No one controls this account, nor can withdraw from
-it. However, the tokens are not burned. Whenever a task is finalized, the
-scheduler that organized the execution of this task is rewarded by the requester
-and also gets a small part of the reward kitty.
+it. However, the tokens are not burned. Whenever a task finalizes, the scheduler
+that organized the execution of this task receives a reward by the requester and
+also gets a small part of the reward kitty.
 
 As described in the protocol parameters section, this reward is
 `reward = kitty.percentage(KITTY_RATIO).max(KITTY_MIN).min(kitty)`.

From 15fdf880b84568f2149a4344ffc34ba4f1156710 Mon Sep 17 00:00:00 2001
From: Le-Caignec <robinlecaignec@yahoo.fr>
Date: Mon, 18 Aug 2025 16:02:48 +0200
Subject: [PATCH 25/27] chore: update Vale workflow configuration to enhance
 spell checking and grammar validation

---
 .github/workflows/vale.yml | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/.github/workflows/vale.yml b/.github/workflows/vale.yml
index ac1060e8..96a15394 100644
--- a/.github/workflows/vale.yml
+++ b/.github/workflows/vale.yml
@@ -13,6 +13,15 @@ jobs:
         uses: actions/checkout@v4
 
       - name: Run Vale
+        # Vale runs spell checking and basic grammar validation
+        # - reporter: github-pr-check provides concise feedback in PR comments
+        # - fail_on_error: false prevents workflow failures on minor issues
+        # - filter_mode: added only checks files changed in the PR
+        # - vale_flags: sets minimum alert level to suggestions only
         uses: errata-ai/vale-action@v2.1.1
         with:
           files: src/
+          reporter: github-pr-check
+          fail_on_error: false
+          filter_mode: added
+          vale_flags: "--minAlertLevel=suggestion"

From 57baa94aedd7a59151a97d575a05c2076c4f2cbf Mon Sep 17 00:00:00 2001
From: Le-Caignec <robinlecaignec@yahoo.fr>
Date: Mon, 18 Aug 2025 16:05:06 +0200
Subject: [PATCH 26/27] chore: standardize Vale workflow configuration by using
 consistent quote style for flags

---
 .github/workflows/vale.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/vale.yml b/.github/workflows/vale.yml
index 96a15394..077a8f96 100644
--- a/.github/workflows/vale.yml
+++ b/.github/workflows/vale.yml
@@ -24,4 +24,4 @@ jobs:
           reporter: github-pr-check
           fail_on_error: false
           filter_mode: added
-          vale_flags: "--minAlertLevel=suggestion"
+          vale_flags: '--minAlertLevel=suggestion'

From ef1a14514efc1d9ecaeb238ce9b24e2c837d54bd Mon Sep 17 00:00:00 2001
From: Le-Caignec <robinlecaignec@yahoo.fr>
Date: Mon, 18 Aug 2025 16:24:53 +0200
Subject: [PATCH 27/27] chore: remove outdated Vale statistics section from
 README and clean up configuration file

---
 .vale.ini |  3 ---
 README.md | 23 -----------------------
 2 files changed, 26 deletions(-)

diff --git a/.vale.ini b/.vale.ini
index a2134c7d..d8034b30 100644
--- a/.vale.ini
+++ b/.vale.ini
@@ -11,6 +11,3 @@ md = markdown
 [*.md]
 BasedOnStyles = Vale, Google
 IgnorePatterns = README.md
-
-# Disable Vale.Terms to avoid case sensitivity issues
-Vale.Terms = NO
diff --git a/README.md b/README.md
index cf7d2594..5c8b2bfd 100644
--- a/README.md
+++ b/README.md
@@ -64,29 +64,6 @@ ensure:
 - Professional tone
 - Accessibility best practices
 
-#### Vale Statistics and Reports
-
-Generate comprehensive reports to track documentation quality:
-
-**Current Statistics (as of latest run):**
-
-- **Total Issues**: 2,731
-- **Top Issues**:
-  - Headings capitalization (622)
-  - Acronyms explanation (472)
-  - Passive voice (460)
-  - Word choice (294)
-  - Parentheses usage (244)
-
-**Files with Most Issues:**
-
-1. `proof-of-contribution.md` (323 issues)
-2. `glossary.md` (143 issues)
-3. `quick-start-for-developers.md` (75 issues)
-
-**Quality Score**: Based on the number of issues per file, we can calculate a
-quality percentage and track improvements over time.
-
 ### Environment Variables (Optional)
 
 Some features of the application require environment variables. This