fix: lisibility & ton

Le-Caignec · Le-Caignec · commit bedd5913260f · 2025-08-17T23:14:04.000+02:00
diff --git 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
@@ -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
@@ -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
@@ -54,15 +54,15 @@ 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>
     <p class="m-0"><strong>Decentralized Infrastructure:</strong> No single point of failure. Your app runs across a distributed network of workers.</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>
-    <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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
 
