address reviews

aimen-djari · aimen-djari · commit c890a624e898 · 2025-08-28T09:13:47.000+01:00
diff --git a/CHECKLIST.md b/CHECKLIST.md
diff --git a/src/get-started/helloWorld/1-overview.md b/src/get-started/helloWorld/1-overview.md
@@ -17,7 +17,7 @@ description:
 
 ## 👨‍💻 Building Privacy-preserving iApp with iExec
 
-<p>Imagine you're building a decentralized app (iApp) that needs to <strong> handle sensitive user data</strong>, for example:</p>
+<p>Imagine you're building a decentralized app (dApp) 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">
@@ -179,5 +179,5 @@ And many other use cases...
 </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!">Now that you understand the fundamentals, dive into protecting your first piece of data with Alice.</p>
+  <p class="m-0!">Now that you understand the fundamentals, dive into protecting your first data with Alice.</p>
 </div>
diff --git a/src/get-started/helloWorld/2-protectData.md b/src/get-started/helloWorld/2-protectData.md
@@ -1,8 +1,8 @@
 ---
 title: Protect Data
 description:
-  Learn how to protect your data using iExec's DataProtector Software
-  Development Kit (SDK) in this hands-on tutorial step.
+  Learn how to protect your data using iExec's DataProtector SDK in this
+  hands-on tutorial step.
 ---
 
 <script setup>
@@ -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>Follow Alice as she learns how to protect her data using DataProtector on Bob's iApp, the developer tool for protecting data creation and management.</p>
+  <p>Follow Alice as she learns how to protect her data using DataProtector on Bob's dApp, the 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">
@@ -178,7 +178,8 @@ const { address: protectedDataAddress } = await dataProtectorCore.protectData({
 - 🔒 **DataProtector** ensures data protection, management, and confidentiality
 
 - 📦 **Protected Data** - DataProtector encrypts and stores data on
-  decentralized storage
+  decentralized storage such as [ar.io](https://ar.io) or
+  [IPFS](https://ipfs.io)
 
 - ⛓️ **Ownership** iExec's protocol writes ownership on the blockchain and links
   it to your wallet
diff --git a/src/get-started/helloWorld/3-buildIApp.md b/src/get-started/helloWorld/3-buildIApp.md
@@ -15,7 +15,7 @@ description:
 </div>
 
 If you wanna explore and deep dive in the command-line tool. You can check the
-[iApp-CLI (Command Line Interface)](https://github.com/iExecBlockchainComputing/iapp/tree/main/cli)
+[iApp Generator ](https://github.com/iExecBlockchainComputing/iapp/tree/main/cli)
 GitHub repository. Follow the instructions carefully for a smooth development
 experience.
 
@@ -54,14 +54,14 @@ Before getting started, make sure you have:
 iExec enables you to build various types of Privacy-preserving applications.
 Here are some popular use cases:
 
-### 📧 Web3 mail
+### 📧 Web3Mail
 
 Send privacy-preserving emails to registered Ethereum account holders without
 knowing or storing their email addresses.
 [Github](https://github.com/iExecBlockchainComputing/web3mail-sdk/tree/main/dapp)
 | [Documentation](/references/web3mail)
 
-### 💬 Web3 telegram
+### 💬 Web3Telegram
 
 Send privacy-preserving Telegram messages without knowing or storing their
 Telegram handles.
diff --git a/src/get-started/overview/iapp.md b/src/get-started/overview/iapp.md
@@ -149,8 +149,7 @@ the TEE execution environment.
 - **Docker**: Your application must be containerized
 - **Input/Output**: Define clear input and output schemas
 - **TEE Compatibility**: Ensure your code runs in secure enclaves
-- **Network Access**: Configure any external Application Programming Interface
-  (API) calls or dependencies
+- **Network Access**: Configure any external API calls or dependencies
 
 ## Next Steps
 
diff --git a/src/get-started/overview/protected-data.md b/src/get-started/overview/protected-data.md
@@ -112,7 +112,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">2.</span>
       <div>
-        <strong>Share:</strong> Authorize specific users and apps to access your data
+        <strong>Share:</strong> Authorize specific users and iApps to access your data
       </div>
     </div>
     <div class="flex items-center gap-3">
diff --git a/src/get-started/overview/rlc.md b/src/get-started/overview/rlc.md
@@ -43,7 +43,7 @@ contributions.
 ### For holders
 
 **Clear positioning:** More developers using iExec's privacy tools means more
-RLC utility in real apps. iExec builds actionable privacy, not just protocols.
+RLC utility in real dApps. iExec builds actionable privacy, not just protocols.
 
 ## 💰 Transparent Payment Flow
 
@@ -53,7 +53,7 @@ transparently distributed to all iExec protocol participants:
 <div class="bg-gradient-to-r from-blue-50 to-blue-100 dark:from-blue-900/20 dark:to-blue-800/20 rounded-lg px-4 border border-blue-200 dark:border-blue-700 my-0">
   <h4 class="text-lg font-semibold text-blue-800 dark:text-blue-200">🔍 How Your RLC Payment is Distributed</h4>
   
-  **1. App Provider** - Gets paid for providing the confidential app
+  **1. App Provider** - Gets paid for providing the iApp
   
   **2. Protected Data Provider** - Gets paid for providing access to protected confidential datasets
   
@@ -64,7 +64,7 @@ transparently distributed to all iExec protocol participants:
 defined by each provider (iApp, Protected Data, Worker) in their marketplace
 orders.
 
-**🔒 RLC Staking:** To run a task on the protocol (executing an app with
+**🔒 RLC Staking:** To run a task on the protocol (executing an iApp with
 protected data on a decentralized workerpool), you need to **lock RLC** in the
 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
diff --git a/src/get-started/quick-start.md b/src/get-started/quick-start.md
@@ -41,7 +41,7 @@ privacy-first applications.
 
 <ProjectCard
     title="Vue.js Starter"
-    description="Vue 3 Composition Application Programming Interface (API) template with TypeScript and optimized build configuration for iExec apps."
+    description="Vue 3 Composition API template with TypeScript and optimized build configuration for iExec apps."
     icon="logos:vue"
     status="coming-soon"
     statusLabel="Coming Soon"
diff --git a/src/get-started/tooling-and-explorers/iexec-explorer.md b/src/get-started/tooling-and-explorers/iexec-explorer.md
@@ -141,9 +141,8 @@ Browse and analyze all tasks across the iExec network:
   workerpool for each task
 - **Real-time Progress**: Monitor task status from queued → running → completed
   with detailed state transitions
-- **Execution Environment**: See which workerpool nodes are processing your
-  tasks and their Trusted Execution Environment (TEE) capabilities (Trust Domain
-  Extensions - TDX, Software Guard Extensions - SGX)
+- **Execution Environment**: See which workers are processing your tasks and
+  their TEE capabilities (SGX, TDX)
 - **Data Flow**: Track which protected datasets are securely accessed by
   authorized iApp
 - **Result Management**:
diff --git a/src/get-started/welcome.md b/src/get-started/welcome.md
@@ -21,7 +21,7 @@ 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 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. Privacy should be <span class="text-fuchsia-700 font-semibold">plug-and-play simple</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. iExec believes privacy should be <span class="text-fuchsia-700 font-semibold">plug-and-play simple</span>, not an afterthought.</p>
 </div>
 
 ## 🛠️ How iExec works
diff --git a/src/guides/build-iapp/advanced/access-confidential-assets.md b/src/guides/build-iapp/advanced/access-confidential-assets.md
@@ -10,7 +10,7 @@ description:
 ::: warning
 
 Before going any further, make sure you managed to
-[Build your first app with Scone framework](build-your-first-sgx-iapp.md).
+[Build your first iApp with Scone framework](build-your-first-sgx-iapp.md).
 
 :::
 
diff --git a/src/guides/build-iapp/advanced/build-your-first-sgx-iapp.md b/src/guides/build-iapp/advanced/build-your-first-sgx-iapp.md
@@ -10,13 +10,6 @@ description:
 In this tutorial, you will learn how to build and run a Confidential Computing
 app with the Scone TEE framework.
 
-::: warning
-
-Before going any further, make sure you managed to
-[Build and Test your iApp](../build-&-test).
-
-:::
-
 ::: tip Prerequisites:
 
 - [Docker](https://docs.docker.com/install/) 17.05 or higher on the daemon and
@@ -44,13 +37,8 @@ docker login registry.scontain.com
 Before going further, your `<docker-hub-user>/hello-world:1.0.0` image built
 previously is required.
 
-If you missed that part, please go back to
-[Build and Test your iApp](../build-&-test).
-
-For this tutorial, you can reuse the same directory tree or create a new one.
-
-To create a new directory tree, execute the following commands in
-`~/iexec-projects/`.
+For this tutorial, create a new directory tree. Execute the following commands
+in `~/iexec-projects/`:
 
 ```bash
 cd ~/iexec-projects
@@ -301,7 +289,7 @@ docker run -it --rm \
             --verbose \
             && echo -e "\n------------------\n" \
             && echo "successfully built TEE docker image => ${IMG_TO}" \
-            && echo "app mrenclave.fingerprint is $(docker run --rm -e SCONE_HASH=1 ${IMG_TO})"
+            && echo "application mrenclave.fingerprint is $(docker run --rm -e SCONE_HASH=1 ${IMG_TO})"
 ```
 
 ```bash [Python]
@@ -329,7 +317,7 @@ docker run -it --rm \
             --verbose \
             && echo -e "\n------------------\n" \
             && echo "successfully built TEE docker image => ${IMG_TO}" \
-            && echo "app mrenclave.fingerprint is $(docker run --rm -e SCONE_HASH=1 ${IMG_TO})"
+            && echo "application mrenclave.fingerprint is $(docker run --rm -e SCONE_HASH=1 ${IMG_TO})"
 ```
 
 :::
diff --git a/src/references/dataProtector/dataProtectorSharing/consume/consumeProtectedData.md b/src/references/dataProtector/dataProtectorSharing/consume/consumeProtectedData.md
@@ -82,9 +82,9 @@ const consumeProtectedDataResult =
 
 **Type:** `AddressOrENS`
 
-Address or Ethereum Name Service (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.
+Address or Ethereum Name Service (ENS) of the 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 {
diff --git a/src/references/glossary.md b/src/references/glossary.md
@@ -64,7 +64,7 @@ for more information
 
 ### Decentralized App (DApp)
 
-An app built on a decentralized network that combines a smart contract and a
+A dApp built on a decentralized network that combines a smart contract and a
 frontend user interface. A DApp has its backend code running on a decentralized
 peer-to-peer network. Contrast this with a traditional app where the backend
 code is running in fully controlled environments.
