diff --git a/src/get-started/helloWorld/1-overview.md b/src/get-started/helloWorld/1-overview.md
index 692adc8..01264e9 100644
--- a/src/get-started/helloWorld/1-overview.md
+++ b/src/get-started/helloWorld/1-overview.md
@@ -11,13 +11,13 @@ description:
 > 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>
+  <h2 class="text-2xl font-bold mt-0 border-none!">Start with the basics</h2>
+  <p>and explore how iExec can help you build Privacy-preserving apps and securely manage sensitive data.</p>
 </div>
 
 ## 👨‍💻 Building Privacy-preserving iApp with iExec
 
-<p>Imagine you're building a decentralized application (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">
@@ -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 iApp.</p>
+  <p class="m-0!">This is where <span class="text-fuchsia-700 font-semibold">iExec</span> comes in. iExec provides 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?
@@ -76,7 +76,7 @@ Execution Environment (TEE)</a></span> and
 Computing</a></span> technologies.
 
 <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!">Our technology allows users to control the <span class="text-fuchsia-700 font-semibold">ownership</span>,
+  <p class="m-0!">The technology allows users to control the <span class="text-fuchsia-700 font-semibold">ownership</span>,
   <span class="text-fuchsia-700 font-semibold">confidentiality</span>, and <span class="text-fuchsia-700 font-semibold">monetization</span> of their data and digital assets within the <span class="text-fuchsia-700 font-semibold">Web3</span> ecosystem.</p>
 </div>
 
@@ -104,7 +104,7 @@ iExec combines three fundamental elements that work together seamlessly:
 - Provides transparent governance rules for data access
 
 <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!">By merging <span class="text-fuchsia-700 font-semibold">blockchain technology</span> with <span class="text-fuchsia-700 font-semibold">confidential computing</span>, we've pioneered <span class="text-fuchsia-700 font-semibold"><a target="_blank" href="https://www.iex.ec/academy/iexec-decentralized-confidential-computing">DeCC</a></span> (Decentralized Confidential Computing) to take <span class="text-fuchsia-700 font-semibold">privacy</span> and <span class="text-fuchsia-700 font-semibold">security</span> to the next level in <span class="text-fuchsia-700 font-semibold">Web3</span> ecosystems.</p>
+  <p class="m-0!">By merging <span class="text-fuchsia-700 font-semibold">blockchain technology</span> with <span class="text-fuchsia-700 font-semibold">confidential computing</span>, iExec pioneered <span class="text-fuchsia-700 font-semibold"><a target="_blank" href="https://www.iex.ec/academy/iexec-decentralized-confidential-computing">DeCC</a></span> (Decentralized Confidential Computing) to take <span class="text-fuchsia-700 font-semibold">privacy</span> and <span class="text-fuchsia-700 font-semibold">security</span> to the next level in <span class="text-fuchsia-700 font-semibold">Web3</span> ecosystems.</p>
 </div>
 
 ### 🧸 DeCC Explained Like You're 5
@@ -174,10 +174,10 @@ And many other use cases...
   </div>
   <div class="flex items-center gap-3">
     <span class="text-xl">🔌</span>
-    <p class="m-0"><strong>Wide Application:</strong> From AI to finance, enabling confidential data processing across various industries</p>
+    <p class="m-0"><strong>Wide application:</strong> From AI to finance, enabling confidential data processing across various industries</p>
   </div>
 </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, let's 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
index 8c2d752..a167ef0 100644
--- a/src/get-started/helloWorld/2-protectData.md
+++ b/src/get-started/helloWorld/2-protectData.md
@@ -1,5 +1,5 @@
 ---
-title: Let's Protect Data
+title: Protect Data
 description:
   Learn how to protect your data using iExec's DataProtector SDK in this
   hands-on tutorial step.
@@ -9,17 +9,17 @@ description:
 import ProtectData from '@/modules/helloWorld/ProtectData.vue';
 </script>
 
-# 🛡️ Let's Protect Data
+# 🛡️ Protect Data
 
 > Reading time: 6 minutes
 
 <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 iApp, our 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">
-  <p class="m-0!"><strong>Protected data</strong> is encrypted data that remains confidential throughout its entire lifecycle - during storage, transfer and processing.</p>
+  <p class="m-0!"><strong>Protected data</strong> refers to encrypted data that remains confidential throughout its entire lifecycle - during storage, transfer and processing.</p>
 </div>
 
 ## 🧩 DataProtector, Key Features
@@ -45,7 +45,7 @@ their DApp with these key features:
   Features an SDK for easy integration into your DApp, enhancing functionality
   and user experience.
 
-## 🧩 Let's Create Protected Data
+## 🧩 Create protected data
 
 <ProtectData />
 
@@ -77,12 +77,12 @@ const { address: protectedDataAddress } = await dataProtectorCore.protectData({
 
 For this tutorial, you can try out the code directly in our interactive
 CodeSandbox demo
-[here](https://codesandbox.io/p/github/iExecBlockchainComputing/dataprotector-sandbox/main?file=%2Fsrc%2FApp.tsx&preventWorkspaceRedirect=true).
+[try the interactive DataProtector sandbox](https://codesandbox.io/p/github/iExecBlockchainComputing/dataprotector-sandbox/main?file=%2Fsrc%2FApp.tsx&preventWorkspaceRedirect=true).
 Here's a quick overview of what happened when you clicked the **Protect Data**
 button:
 
-![alt](/assets/hello-world/dataprotector_light.png){.light-only}
-![alt](/assets/hello-world/dataprotector_dark.png){.dark-only}
+![DataProtector workflow diagram showing the 4-step process: SDK called, data encrypted with symmetric key, protected data address returned to user, and protected data encrypted and stored on decentralized storage](/assets/hello-world/dataprotector_light.png){.light-only}
+![DataProtector workflow diagram showing the 4-step process: SDK called, data encrypted with symmetric key, protected data address returned to user, and protected data encrypted and stored on decentralized storage](/assets/hello-world/dataprotector_dark.png){.dark-only}
 
 <div class="flex flex-col gap-2.5 my-6">
   <div class="flex items-center gap-3">
@@ -91,7 +91,7 @@ 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">2</span>
-    <span>The data is encrypted with a symmetric key</span>
+    <span>DataProtector encrypts the data with a symmetric key</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">3</span>
@@ -107,7 +107,7 @@ 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">6</span>
-    <span>The protected data address is returned to the user</span>
+    <span>The system returns the protected data address to the user</span>
   </div>
 </div>
 
@@ -177,7 +177,9 @@ const { address: protectedDataAddress } = await dataProtectorCore.protectData({
 
 - 🔒 **DataProtector** ensures data protection, management, and confidentiality
 
-- 📦 **Protected Data** is encrypted and stored on decentralized storage
+- 📦 **Protected Data** - DataProtector encrypts and stores data on
+  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
@@ -185,5 +187,5 @@ const { address: protectedDataAddress } = await dataProtectorCore.protectData({
 - 🔌 **Integration** is simple with our developer tools
 
 <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 chapter, we'll show you how to build, deploy, and run an iApp to process your protected data. Let's go! 🚀</p>
+  <p class="m-0!">In the next chapter, learn how to build, deploy, and run an iApp to process your protected data.</p>
 </div>
diff --git a/src/get-started/helloWorld/3-buildIApp.md b/src/get-started/helloWorld/3-buildIApp.md
index 32da000..c571efb 100644
--- a/src/get-started/helloWorld/3-buildIApp.md
+++ b/src/get-started/helloWorld/3-buildIApp.md
@@ -5,18 +5,18 @@ description:
   processing protected data in this comprehensive tutorial.
 ---
 
-# 🛠️ Build and Deploy your First iApp
+# 🛠️ Build and deploy your first iApp
 
 > 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 iApp with just a few commands.</p>
+  <h2 class="text-2xl font-bold mt-0 border-none!">Time to build</h2>
+  <p>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)
-github repository. Follow the instructions carefully for a smooth development
+If you wanna explore and deep dive in the command-line tool. You can check the
+[iApp Generator ](https://github.com/iExecBlockchainComputing/iapp/tree/main/cli)
+GitHub repository. Follow the instructions carefully for a smooth development
 experience.
 
 ## 📋 Prerequisites
@@ -46,29 +46,29 @@ Before getting started, make sure you have:
 </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">
-  <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>
+  <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 iApp 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:
 
-### 📧 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.
 [Github](https://github.com/iExecBlockchainComputing/web3telegram-sdk/tree/main/dapp)
 | [Documentation](/references/web3telegram)
 
-### 🌐 Content Delivery
+### 🌐 Content delivery
 
 Transfer, sell or rent protected content to authorized users.
 [Github](https://github.com/iExecBlockchainComputing/dataprotector-sdk/tree/main/packages/protected-data-delivery-dapp)
@@ -171,7 +171,7 @@ You will be prompted with the following message:
     '🐳 Added Dockerfile',
     '⚙️ Added iExec configuration'
   ]"
-  :successMessage="'Your iApp is ready!'"
+  :successMessage="'Your iApp is ready'"
 />
 
 <div class="flex flex-col gap-2.5 my-6">
@@ -196,7 +196,7 @@ You will be prompted with the following message:
 </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">
-  <p class="m-0!">We recommend selecting <span class="text-fuchsia-700 font-semibold">"Hello World"</span> to quickly discover how iApp works! use <span class="text-fuchsia-700 font-semibold">advanced</span> only if you are familiar with iExec.</p>
+  <p class="m-0!">We recommend selecting <span class="text-fuchsia-700 font-semibold">"Hello World"</span> to quickly discover how iApp works. Use <span class="text-fuchsia-700 font-semibold">advanced</span> only if you are familiar with iExec.</p>
 </div>
 
 - An iApp project is setup with the selected language
@@ -288,7 +288,7 @@ simulating how it will run in the iExec network's TEE environment.
   <p class="m-0!">- If you get <code>Error: Failed to locate iApp project root</code>: Ensure you are in your project folder before proceeding.</p>
 </div>
 
-### 🧩 Using Arguments
+### 🧩 Using arguments
 
 You can pass arguments to your iApp using the `--args` option. This allows you
 to provide necessary inputs during runtime (you can use your name for example).
@@ -297,7 +297,7 @@ to provide necessary inputs during runtime (you can use your name for example).
 iapp test --args your-name
 ```
 
-### 🔒 Using Protected Data
+### 🔒 Using protected data
 
 You can pass a protectedData that you are authorized to process to your iApp
 using the `--protectedData` option.
@@ -370,7 +370,7 @@ Once you have your token, you can deploy your iApp.
 </template>
 
 <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">
-  <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!">📝 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 the Docker BuildKit feature is enabled and supports AMD64 architecture:</p>
@@ -401,7 +401,7 @@ allowing it to run securely in a **Trusted Execution Environment (TEE)** for
   <p class="m-0!">🎉 Congratulations! You've successfully deployed and run your first iApp on iExec. This is a significant milestone - your application is now ready to securely process confidential data in a trusted environment.</p>
 </div>
 
-## 🎯 Key Takeaways
+## 🎯 Key takeaways
 
 - 🔒 **iApp:** Special applications that run in TEEs to process protected data
 - 🛠️ **iApp CLI:** Command-line tool for building, testing, and deploying iApp
@@ -410,7 +410,7 @@ allowing it to run securely in a **Trusted Execution Environment (TEE)** for
   environments
 
 <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!">Next up: Alice will learn how to authorize the iApp and Bob to access and use her protected data!  🚀</p>
+  <p class="m-0!">Next up: Alice will learn how to authorize the iApp and Bob to access and use her protected data.</p>
 </div>
 
 <script setup>
diff --git a/src/get-started/overview/iapp.md b/src/get-started/overview/iapp.md
index fd99fd9..58364cb 100644
--- a/src/get-started/overview/iapp.md
+++ b/src/get-started/overview/iapp.md
@@ -65,8 +65,9 @@ Turnkey Privacy iApp, they will.**
 ## How it Works
 
 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.
+inside specific processors (Intel Software Guard Extensions (SGX)/Trust Domain
+Extensions (TDX) chipset). Everything stays private and protected there, even
+from the operating system.
 
 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.
diff --git a/src/get-started/overview/protected-data.md b/src/get-started/overview/protected-data.md
index 4cc854d..4a39f5d 100644
--- a/src/get-started/overview/protected-data.md
+++ b/src/get-started/overview/protected-data.md
@@ -6,7 +6,7 @@ description:
   controls, and secure data monetization.
 ---
 
-# Protected Data
+# Protected data
 
 Protected Data refers to any data encrypted using the **iExec Data Protector
 tool**. This Turnkey Privacy encryption solution enables users to protect,
@@ -16,9 +16,9 @@ manage and monetize their data within the Web3 ecosystem effortlessly.
   <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
+## Key concepts
 
-### Data Governance
+### Data governance
 
 <div class="mb-4"></div>
 
@@ -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 applications 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">
@@ -136,7 +136,7 @@ manage and monetize their data within the Web3 ecosystem effortlessly.
   </div>
 </div>
 
-## Use Cases
+## Use cases
 
 <div class="grid grid-cols-1 md:grid-cols-2 gap-6 my-6">
   <div class="bg-[var(--vp-c-bg-soft)] rounded-[6px] p-6 flex flex-col gap-2">
@@ -188,7 +188,7 @@ manage and monetize their data within the Web3 ecosystem effortlessly.
   <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
+## Next steps
 
 <div class="bg-[var(--vp-c-bg-soft)] rounded-[6px] p-6 mb-6">
   <div class="flex flex-col gap-4">
diff --git a/src/get-started/overview/rlc.md b/src/get-started/overview/rlc.md
index ebcb51a..efd1b9a 100644
--- a/src/get-started/overview/rlc.md
+++ b/src/get-started/overview/rlc.md
@@ -3,7 +3,7 @@ title: RLC Token
 description:
   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.
+  it drives privacy-first Web3 apps.
 ---
 
 <div class="flex flex-col items-center mb-8">
@@ -14,8 +14,8 @@ description:
 
 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.
+requires RLC. Every app execution requires RLC. The more builders use iExec
+tools, the more utility RLC gains in real apps.
 
 ::: tip Info
 
@@ -30,21 +30,20 @@ payments on this network.
 **Stack adoption = token usage.** When developers build with iExec tools, RLC
 gets used. More privacy apps deployed means more RLC demand.
 
-### For Users
+### For users
 
-Every confidential computation you run uses RLC. That's how we keep your data
-private while making it usable.
+Every confidential computation you run uses RLC. That's how iExec keeps your
+data private while making it usable.
 
-### For Providers
+### For providers
 
 Build apps, provide data, or run workers. All earn RLC when people use your
 contributions.
 
-### For Holders
+### For holders
 
 **Clear positioning:** More developers using iExec's privacy tools means more
-RLC utility in real applications. We're building actionable privacy, not just
-protocols.
+RLC utility in real dApps. iExec builds actionable privacy, not just protocols.
 
 ## 💰 Transparent Payment Flow
 
@@ -54,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 application
+  **1. App Provider** - Gets paid for providing the iApp
   
   **2. Protected Data Provider** - Gets paid for providing access to protected confidential datasets
   
@@ -65,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 application 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/overview/what-is-iexec.md b/src/get-started/overview/what-is-iexec.md
index a88710e..2d99ec6 100644
--- a/src/get-started/overview/what-is-iexec.md
+++ b/src/get-started/overview/what-is-iexec.md
@@ -2,13 +2,13 @@
 title: What is iExec?
 description:
   Learn about iExec, the decentralized computing platform that enables
-  privacy-preserving applications
+  privacy-preserving apps
 ---
 
 # What is iExec?
 
 iExec is a **decentralized confidential computing toolkit** that helps
-developers build privacy-preserving applications.
+developers build privacy-preserving apps.
 
 ## SpeedRun The Protocol
 
@@ -21,9 +21,9 @@ access it.
 
 ### Step 2: Secure Computing (Workers)
 
-Code runs inside **secure enclaves** (TEEs) on iExec workers. The worker can
-access your data to process it, but only within the privacy-safe TEE
-environment - your data never leaves the secure bubble.
+Code runs inside **secure enclaves** (Trusted Execution Environments - TEEs) on
+iExec workers. The worker can access your data to process it, but only within
+the privacy-safe TEE environment - your data never leaves the secure bubble.
 
 ### Step 3: Run iApp
 
@@ -42,7 +42,7 @@ lose control.
 Protected Data + iApp + Worker = Task → Encrypted Result
 ```
 
-## What Each Piece Does
+## What each piece does
 
 ### **Protected Data**
 
@@ -66,7 +66,7 @@ The execution instruction that unifies the entire flow: "Run this iApp on this
 Protected Data using a TEE Worker, then return the encrypted result to me." The
 protocol takes care of worker allocation and secure coordination.
 
-## Real Example Walkthrough
+## Real example walkthrough
 
 **AI Model Training (Private)**
 
@@ -82,7 +82,7 @@ protocol takes care of worker allocation and secure coordination.
 2. **Execute**: App submits Task → "Send email via Web3Mail iApp"
 3. **Result**: Email sent, addresses stay private, sender/receiver authenticated
 
-## Start Building
+## Start building
 
 Now that you get the protocol, pick your devtools:
 
@@ -93,5 +93,5 @@ Now that you get the protocol, pick your devtools:
   your first dataset
 - **Build iApp**: Create confidential compute with
   [iApp Generator](/references/iapp-generator)
-- **Hands-On**: Follow our [Hello World](/get-started/helloWorld) to see all
+- **Hands-On**: Follow the [Hello World](/get-started/helloWorld) to see all
   devtools working together
diff --git a/src/get-started/overview/workerpool.md b/src/get-started/overview/workerpool.md
index 2669982..d975d58 100644
--- a/src/get-started/overview/workerpool.md
+++ b/src/get-started/overview/workerpool.md
@@ -1,7 +1,7 @@
 ---
 title: Workerpool
 description:
-  Learn about workerpool in iExec - the computing resources that execute iApp
+  Learn about Workerpool in iExec - the computing resources that execute iApp
 ---
 
 # Workerpool
@@ -11,12 +11,12 @@ A **Workerpool** is a group of computing machines (workers) managed by a
 secure environments on the iExec network.
 
 <div class="bg-gradient-to-r from-blue-400/10 to-blue-400/5 rounded-[6px] p-6 border-l-4 border-blue-700 mb-6">
-  <p class="m-0!">Think of a workerpool as a <span class="text-blue-700 font-semibold">computing cluster</span> where your iApp runs. Each workerpool consists of multiple workers (machines) coordinated by a manager who ensures tasks are executed efficiently and securely.</p>
+  <p class="m-0!">Think of a Workerpool as a <span class="text-blue-700 font-semibold">computing cluster</span> where your iApp runs. Each Workerpool consists of multiple workers (machines) coordinated by a manager who ensures tasks are executed efficiently and securely.</p>
 </div>
 
-## Key Concepts
+## Key concepts
 
-### Workerpool Manager
+### Workerpool manager
 
 <div class="mb-4"></div>
 
@@ -37,7 +37,7 @@ secure environments on the iExec network.
     <div class="flex items-center gap-3">
       <span>•</span>
       <div>
-        <strong>Network Interface:</strong> Connects the workerpool to the iExec marketplace
+        <strong>Network Interface:</strong> Connects the Workerpool to the iExec marketplace
       </div>
     </div>
   </div>
@@ -97,7 +97,7 @@ secure environments on the iExec network.
   </div>
 </div>
 
-## How Workerpool Work
+## How Workerpool work
 
 <div class="bg-[var(--vp-c-bg-soft)] rounded-[6px] p-6 mb-6">
   <div class="flex flex-col gap-4">
@@ -110,7 +110,7 @@ secure environments on the iExec network.
     <div class="flex items-center gap-3">
       <span class="text-xl font-bold text-blue-700">2.</span>
       <div>
-        <strong>Workerpool Selection:</strong> PoCo system matches request with available workerpool
+        <strong>Workerpool Selection:</strong> PoCo system matches request with available Workerpool
       </div>
     </div>
     <div class="flex items-center gap-3">
@@ -134,19 +134,19 @@ secure environments on the iExec network.
   </div>
 </div>
 
-## Getting Started
+## Getting started
 
 <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!">Want to <span class="text-green-700 font-semibold">use workerpool</span>? Start building iApp and the protocol will handle workerpool selection automatically.</p>
+  <p class="m-0!">Want to <span class="text-green-700 font-semibold">use Workerpool</span>? Start building iApp and the protocol will handle Workerpool selection automatically.</p>
 </div>
 
-## Next Steps
+## Next steps
 
 <div class="bg-[var(--vp-c-bg-soft)] rounded-[6px] p-6 mb-6">
   <div class="flex flex-col gap-4">
     <div class="flex items-start gap-3">
       <div>
-        <strong>Start Using:</strong> <a href="/get-started/helloWorld" class="text-blue-700 hover:text-blue-600">Build your first iApp</a> and see a workerpool in action
+        <strong>Start Using:</strong> <a href="/get-started/helloWorld" class="text-blue-700 hover:text-blue-600">Build your first iApp</a> and see a Workerpool in action
       </div>
     </div>
     <div class="flex items-start gap-3">
diff --git a/src/get-started/tooling-and-explorers/bridge.md b/src/get-started/tooling-and-explorers/bridge.md
index 3479ff5..f5e6afa 100644
--- a/src/get-started/tooling-and-explorers/bridge.md
+++ b/src/get-started/tooling-and-explorers/bridge.md
@@ -123,13 +123,13 @@ The RLC multichain bridge implementation has been thoroughly audited by
 audit report is accessible at
 [halborn.com/audits](https://www.halborn.com/audits/iexec/rlc-multichain-bridge-979ae0).
 
-### Open Source
+### Open source
 
 The complete source code for the RLC multichain bridge system is publicly
 available and open source on GitHub:
 [RLC Bridge Repository](https://github.com/iExecBlockchainComputing/rlc-multichain)
 
-### Security Features
+### Security features
 
 - **LayerZero Protocol**: Battle-tested cross-chain messaging protocol
 - **Smart Contract Audits**: Professional security audits by Halborn
diff --git a/src/get-started/tooling-and-explorers/iexec-explorer.md b/src/get-started/tooling-and-explorers/iexec-explorer.md
index 63da614..e540b56 100644
--- a/src/get-started/tooling-and-explorers/iexec-explorer.md
+++ b/src/get-started/tooling-and-explorers/iexec-explorer.md
@@ -141,8 +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 TEE capabilities (TDX, 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
index 562aa13..c77d90f 100644
--- a/src/get-started/welcome.md
+++ b/src/get-started/welcome.md
@@ -21,10 +21,10 @@ 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. We believe 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 we Make it Happen
+## 🛠️ How iExec works
 
 iExec provides Turnkey Privacy tools that make confidential computing simple and
 actionable:
diff --git a/src/guides/build-iapp/advanced/access-confidential-assets.md b/src/guides/build-iapp/advanced/access-confidential-assets.md
index 1bb5458..e713ecf 100644
--- a/src/guides/build-iapp/advanced/access-confidential-assets.md
+++ b/src/guides/build-iapp/advanced/access-confidential-assets.md
@@ -2,8 +2,7 @@
 title: Access Confidential Assets from Your iApp
 description:
   Learn how to access confidential assets including secrets, protected data, and
-  requester secrets from your iExec application using the Secret Management
-  Service
+  requester secrets from your iExec app using the Secret Management Service
 ---
 
 # Access confidential assets from your iApp
@@ -11,7 +10,7 @@ description:
 ::: warning
 
 Before going any further, make sure you managed to
-[Build your first application with Scone framework](build-your-first-sgx-iapp.md).
+[Build your first iApp with Scone framework](build-your-first-sgx-iapp.md).
 
 :::
 
@@ -26,25 +25,24 @@ indeed whitelisted for it.
 
 The SMS currently supports 3 types of secrets:
 
-1. [Application developer secret](/guides/build-iapp/build-&-test#application-developer-secret):
-   This secret is directly accessible from the application as an environment
-   variable. It is owned by the developer of the application. It can be any kind
-   of data (API key, private key, token, ..) as long as it respects the size
-   limit (max. 4096 kB).
+1. [App developer secret](/guides/build-iapp/build-&-test#application-developer-secret):
+   This secret is directly accessible from the app as an environment variable.
+   It is owned by the developer of the app. It can be any kind of data (API key,
+   private key, token, ..) as long as it respects the size limit (max. 4096 kB).
 2. [Requester secrets](/guides/build-iapp/inputs#access-requester-secrets):
-   These secrets are directly accessible from the application as environment
-   variables, as long as the requester has decided to share them with it. These
-   secrets can be any kind of data as long as they respect the size limit (max.
-   4096 kB). Before buying a task, a requester secret is pushed into the SMS and
-   is not linked to any application. When a requester buys a task, the requester
-   can declare which secrets can be accessed by the application. Doing so, a
-   single requester secret can be shared with multiple applications.
+   These secrets are directly accessible from the app as environment variables,
+   as long as the requester has decided to share them with it. These secrets can
+   be any kind of data as long as they respect the size limit (max. 4096 kB).
+   Before buying a task, a requester secret is pushed into the SMS and is not
+   linked to any app. When a requester buys a task, the requester can declare
+   which secrets can be accessed by the app. Doing so, a single requester secret
+   can be shared with multiple apps.
 3. [Protected Data secret](/guides/manage-data/manage-access): A protected data
-   secret is not directly accessible from the application but its decrypted
-   content is. If a Protected Data is requested and authorized to be used in it,
-   its content will be automatically decrypted in the application enclave.
+   secret is not directly accessible from the app but its decrypted content is.
+   If a Protected Data is requested and authorized to be used in it, its content
+   will be automatically decrypted in the app enclave.
 
-Here is a general overview of how confidential assets are used on iExec:
+Here is a general overview of how iExec uses confidential assets:
 
 ```mermaid
 graph TD
@@ -53,7 +51,7 @@ graph TD
     ProtectedDataOwn[ProtectedData owner] -->|1.c. Push secret| SMS
     Req --> |2 . Buy task| Chain
     Chain[Blockchain] --> |3 . Notify task to compute| Worker[Worker/Workerpool]
-    Worker --> |4 . Launch TEE application| iApp[TEE application]
+    Worker --> |4 . Launch TEE app| iApp[TEE app]
     iApp --> |5.a. Get secrets for task| SMS
     SMS --> |5.b. Check authorization for secrets| Chain
 ```
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
index 1847a16..c7b3cc4 100644
--- a/src/guides/build-iapp/advanced/build-your-first-sgx-iapp.md
+++ b/src/guides/build-iapp/advanced/build-your-first-sgx-iapp.md
@@ -1,14 +1,14 @@
 ---
 title: Build Your First Application with Scone Framework
 description:
-  Learn how to build and run Confidential Computing applications with the Scone
-  TEE framework for secure, privacy-preserving computation
+  Learn how to build and run Confidential Computing apps with the Scone TEE
+  framework for secure, privacy-preserving computation
 ---
 
-# Build your first application with Scone framework
+# Build your first app with Scone framework
 
 In this tutorial, you will learn how to build and run a Confidential Computing
-application with the Scone TEE framework.
+app with the Scone TEE framework.
 
 ::: tip Prerequisites:
 
@@ -32,10 +32,13 @@ Once your account is activated, you need to
 docker login registry.scontain.com
 ```
 
-## Prepare your application
+## Prepare your app
 
-To create a new directory tree, execute the following commands in
-`~/iexec-projects/`.
+Before going further, your `<docker-hub-user>/hello-world:1.0.0` image built
+previously is required.
+
+For this tutorial, create a new directory tree. Execute the following commands
+in `~/iexec-projects/`:
 
 ```bash
 cd ~/iexec-projects
@@ -244,8 +247,8 @@ docker run \
 
 ## Build the TEE docker image
 
-Before wrapping your iExec confidential application with Scone, you need to
-generate a custom signing key. This key is used for the sconification process.
+Before wrapping your iExec confidential app with Scone, you need to generate a
+custom signing key. The sconification process uses this key.
 
 Generate your enclave signing key with:
 
@@ -256,7 +259,7 @@ openssl genrsa -3 -out enclave-key.pem 3072
 This will create an `enclave-key.pem` file in your current directory. You will
 use this file in the sconify Docker command to sign your TEE image.
 
-We will use the following script to wrap the sconification process, copy the
+Use the following script to wrap the sconification process, copy the
 `sconify.sh` script in the current directory:
 
 ::: code-group
@@ -319,7 +322,7 @@ docker run -it --rm \
 
 :::
 
-Run the `sconify.sh` script to build the Scone TEE application:
+Run the `sconify.sh` script to build the Scone TEE app:
 
 ```bash
 ./sconify.sh
@@ -332,15 +335,19 @@ docker login
 docker push <docker-hub-user>/tee-scone-hello-world:1.0.0
 ```
 
-Congratulations, you just built your Scone TEE application.
+Congratulations, you just built your Scone TEE app.
+
+## Test your iApp on iExec
+
+At this stage, your app is ready to be tested on iExec. The process is similar
+to testing any type of app on the platform, with these minor exceptions:
 
-## Deploy the iApp
+### Deploy the TEE iApp on iExec
 
-TEE applications require some additional information to be filled in during
-deployment.
+TEE apps require some additional information to be filled in during deployment.
 
 ```bash
-# prepare the TEE application template
+# prepare the TEE app template
 iexec app init --tee
 ```
 
@@ -351,7 +358,7 @@ Edit `iexec.json` and fill in the standard keys and the `mrenclave` object:
   ...
   "app": {
     "owner": "<your-wallet-address>", // starts with 0x
-    "name": "tee-scone-hello-world", // application name
+    "name": "tee-scone-hello-world", // app name
     "type": "DOCKER",
     "multiaddr": "docker.io/<docker-hub-user>/tee-scone-hello-world:1.0.0", // app image
     "checksum": "<checksum>", // starts with 0x, update it with your own image digest
@@ -547,10 +554,10 @@ infrastructure.
 
 ## Next step?
 
-In this tutorial, you learned how to leverage your application with the power of
-Trusted Execution Environments using iExec. But according to your use case, you
-may need to use some confidential data to get the full potential of the
-**Confidential Computing** paradigm. Check out next chapters to see how:
+In this tutorial, you learned how to leverage your app with the power of Trusted
+Execution Environments using iExec. But according to your use case, you may need
+to use some confidential data to get the full potential of the **Confidential
+Computing** paradigm. Check out next chapters to see how:
 
 - [Access confidential assets from your iApp](access-confidential-assets.md)
 - [Protect the result](/guides/build-iapp/advanced/protect-the-result.md)
diff --git a/src/guides/build-iapp/advanced/protect-the-result.md b/src/guides/build-iapp/advanced/protect-the-result.md
index 4042945..bc232ab 100644
--- a/src/guides/build-iapp/advanced/protect-the-result.md
+++ b/src/guides/build-iapp/advanced/protect-the-result.md
@@ -7,12 +7,12 @@ description:
 
 # Protect the result
 
-In previous tutorials, we saw how to build
+Previous tutorials showed how to build
 [Confidential Computing applications](/protocol/tee/intel-sgx) that run securely
 inside enclaves and combine them with confidential assets to get the most out of
-confidential computing advantages. In this chapter, we will push things further
-to protect the workflow in an end to end mode. That means the next step would be
-encrypting results.
+confidential computing advantages. This chapter pushes things further to protect
+the workflow in an end to end mode. That means the next step would be encrypting
+results.
 
 ::: warning
 
diff --git a/src/guides/build-iapp/advanced/quick-start.md b/src/guides/build-iapp/advanced/quick-start.md
index 6198a61..3d502c4 100644
--- a/src/guides/build-iapp/advanced/quick-start.md
+++ b/src/guides/build-iapp/advanced/quick-start.md
@@ -7,14 +7,14 @@ description:
 
 # Quick Start
 
-> In this tutorial we will show you how you can create decentralized application
-> over the iExec infrastructure.
+> This tutorial shows how to create decentralized app over the iExec
+> infrastructure.
 
 iExec enables decentralized docker app deployment and monetization on the
 blockchain.
 
-In this guide, we will use the iExec SDK command-line interface to deploy an
-iExec app on a test blockchain.
+This guide uses the iExec SDK command-line interface to deploy an iExec app on a
+test blockchain.
 
 ## Install the iExec SDK
 
diff --git a/src/guides/build-iapp/inputs.md b/src/guides/build-iapp/inputs.md
index 958fe8e..2843d1b 100644
--- a/src/guides/build-iapp/inputs.md
+++ b/src/guides/build-iapp/inputs.md
@@ -15,7 +15,7 @@ applications.
 This guide covers all input types available to your iApp and how to access them
 within the TEE environment.
 
-## Two Perspectives on Inputs
+## Two perspectives on inputs
 
 **Inputs work differently depending on your role:**
 
@@ -33,7 +33,7 @@ You can also execute iApps outside of DataProtector using other methods. See the
 
 This guide shows both perspectives for each input type.
 
-## Input Types Overview
+## Input types overview
 
 Inside the TEE, your iApp can work with four distinct categories of inputs:
 
@@ -107,7 +107,7 @@ try {
 
 :::
 
-### How Users Provide Protected Data
+### How users provide protected data
 
 Users specify the protected data address when executing your iApp:
 
@@ -177,7 +177,7 @@ if (args.length >= 2) {
 
 :::
 
-### How Users Provide Args
+### How users provide args
 
 Users pass args through the DataProtector `processProtectedData()` call:
 
@@ -195,7 +195,7 @@ const response = await dataProtectorCore.processProtectedData({
 });
 ```
 
-### Example Use Cases
+### Example use cases
 
 - Model configuration: `"model=sentiment-bert temperature=0.7"`
 - Processing options: `"format=json output_size=small"`
@@ -270,7 +270,7 @@ const response = await dataProtectorCore.processProtectedData({
 });
 ```
 
-### Example Use Cases
+### Example use cases
 
 - ML model files: `"https://example.com/sentiment-model.pkl"`
 - Reference datasets: `"https://data.gov/reference-corpus.csv"`
diff --git a/src/guides/build-iapp/manage-access.md b/src/guides/build-iapp/manage-access.md
index a970720..2d29375 100644
--- a/src/guides/build-iapp/manage-access.md
+++ b/src/guides/build-iapp/manage-access.md
@@ -10,7 +10,7 @@ iApp is deployed with iApp Generator, you need to publish app orders to make it
 accessible to users and define your governance rules.
 
 Think of orders as **usage proposals** - they define pricing, access
-restrictions, and execution conditions for your application.
+restrictions, and execution conditions for your app.
 
 ## What is an Order?
 
@@ -184,9 +184,9 @@ iexec order publish --app
 
 Your iApp is now accessible according to the conditions you defined!
 
-## Managing Orders
+## Managing orders
 
-### View Published Orders
+### View published orders
 
 Check active orders for your app:
 
@@ -222,7 +222,7 @@ iexec order cancel --app <orderHash>
 }
 ```
 
-## App Order Parameters
+## App order parameters
 
 Here's the detailed description of each parameter:
 
@@ -269,7 +269,7 @@ Here's the detailed description of each parameter:
 | `0x0000000000000000000000000000000000000000000000000000000000000000` | Standard execution   |
 | `0x0000000000000000000000000000000000000000000000000000000000000003` | TEE required (Scone) |
 
-### Access Restrictions
+### Access restrictions
 
 All restrictions use `0x0000000000000000000000000000000000000000` to indicate
 "no restriction".
@@ -302,7 +302,7 @@ Next steps:
 - **Adjust pricing**: Create new orders based on demand
 - **Manage revenue**: Check your earnings with `iexec account show`
 
-### Technical Deep Dive
+### Technical deep dive
 
 - **[iExec SDK Documentation](https://github.com/iExecBlockchainComputing/iexec-sdk)** -
   Complete CLI reference
diff --git a/src/guides/manage-data/handle-schemas-dataset-types.md b/src/guides/manage-data/handle-schemas-dataset-types.md
index 1024c8f..5daeb9e 100644
--- a/src/guides/manage-data/handle-schemas-dataset-types.md
+++ b/src/guides/manage-data/handle-schemas-dataset-types.md
@@ -16,7 +16,7 @@ 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.
 
-## How Schemas Work
+## How schemas work
 
 When you protect data with DataProtector, the SDK automatically analyzes your
 JSON object and generates a schema. **No manual schema definition needed** -
@@ -64,7 +64,7 @@ understand and validate.
 
 :::
 
-## Supported Data Types
+## Supported data types
 
 The schema automatically detects these types:
 
@@ -84,7 +84,7 @@ MIME types manually.
 
 :::
 
-## Why Schemas Matter
+## Why schemas matter
 
 - **Clarity**: Makes your data easier to understand and reuse
 - **Safety**: Ensures iExec apps don’t process the wrong data
@@ -129,7 +129,7 @@ const listProtectedData = await dataProtectorCore.getProtectedData({
 });
 ```
 
-## Real Examples
+## Real examples
 
 ### Simple User Profile
 
@@ -240,7 +240,7 @@ const fileData = await dataProtectorCore.protectData({
 }
 ```
 
-## Using Schemas in iApp
+## Using schemas in iApp
 
 Once you have protected data with a schema, you'll want to process it inside an
 iApp.
@@ -256,7 +256,7 @@ don't match, you'll get runtime errors when processing the data.
 [Inputs guide](/guides/build-iapp/inputs) to learn how to access schema fields
 inside your iApp using the deserializer.
 
-## Next Steps
+## Next steps
 
 **You now understand how schemas work with protected data.** Here's what to
 explore next:
diff --git a/src/guides/manage-data/manage-access.md b/src/guides/manage-data/manage-access.md
index 920e9bd..be0852d 100644
--- a/src/guides/manage-data/manage-access.md
+++ b/src/guides/manage-data/manage-access.md
@@ -79,7 +79,7 @@ for detailed formatting instructions.
 
 :::
 
-## Grant Access
+## Grant access
 
 By default, your protected data is private. To let others use it, you need to
 grant access to both:
diff --git a/src/guides/manage-data/monetize-protected-data.md b/src/guides/manage-data/monetize-protected-data.md
index 3674b32..5444287 100644
--- a/src/guides/manage-data/monetize-protected-data.md
+++ b/src/guides/manage-data/monetize-protected-data.md
@@ -227,7 +227,7 @@ const purchase = await dataProtectorSharing.buyProtectedData({
 - One-time valuable insights
 - When you want to exit data ownership
 
-## Which Approach to Choose?
+## Which approach to choose?
 
 | **Signed Orders (Core)**     | **Time-Based Access (Sharing)** |
 | ---------------------------- | ------------------------------- |
@@ -241,7 +241,7 @@ and usage-based billing.
 **Choose Time-Based Access when**: You want automated distribution, unlimited
 usage periods, and flexible pricing models.
 
-## Next Steps
+## Next steps
 
 **Ready to start monetizing your data?** Here are your next steps:
 
diff --git a/src/guides/use-iapp/getting-started.md b/src/guides/use-iapp/getting-started.md
index f15444e..5b3e213 100644
--- a/src/guides/use-iapp/getting-started.md
+++ b/src/guides/use-iapp/getting-started.md
@@ -51,7 +51,7 @@ Using iApp involves these main steps:
 3. **Execute** - Run the iApp
 4. **Get Results** - Retrieve your computation results
 
-### Understanding Orders
+### Understanding orders
 
 iApp are executed through a marketplace system where different actors publish
 orders:
diff --git a/src/guides/use-iapp/how-to-pay-executions.md b/src/guides/use-iapp/how-to-pay-executions.md
index 6ab24d1..d43219d 100644
--- a/src/guides/use-iapp/how-to-pay-executions.md
+++ b/src/guides/use-iapp/how-to-pay-executions.md
@@ -192,7 +192,7 @@ be used in combination with `useVoucher: true`.
 
 ## Understanding Pricing
 
-### Cost Components
+### Cost components
 
 iApp execution costs consist of several components:
 
@@ -201,7 +201,7 @@ iApp execution costs consist of several components:
 3. **Workerpool Fee**: Paid to the computation provider
 4. **Gas Fees**: Blockchain transaction costs
 
-### Setting Maximum Prices
+### Setting maximum prices
 
 You can control costs by setting maximum prices for each component:
 
diff --git a/src/guides/use-iapp/integrate-web3-messaging.md b/src/guides/use-iapp/integrate-web3-messaging.md
index 0881ac8..13d6606 100644
--- a/src/guides/use-iapp/integrate-web3-messaging.md
+++ b/src/guides/use-iapp/integrate-web3-messaging.md
@@ -124,5 +124,5 @@ Each message sent through Web3Mail or Web3Telegram requires payment in RLC
 tokens.
 
 For detailed information about payment methods, pricing, and voucher usage, see
-our comprehensive guide:
+the comprehensive guide:
 [How to pay for executions](/guides/use-iapp/how-to-pay-executions)
diff --git a/src/guides/use-iapp/introduction.md b/src/guides/use-iapp/introduction.md
index c2e6e67..ec58534 100644
--- a/src/guides/use-iapp/introduction.md
+++ b/src/guides/use-iapp/introduction.md
@@ -10,7 +10,7 @@ description:
 In the iExec network, multiple actors work together in a coordinated process to
 ensure secure, decentralized computation. Here's how the ecosystem operates:
 
-### Key Actors in the Network
+### Key actors in the network
 
 - **👤 Requesters**: Users who need computation performed on protected data
 - **🏭 Workerpool Managers**: Operators who manage groups of workers and
@@ -20,7 +20,7 @@ ensure secure, decentralized computation. Here's how the ecosystem operates:
   iExec marketplace
 - **🔐 Data Providers**: Users who own and protect the data being processed
 
-### Network Assets
+### Network assets
 
 - **📱 iApp**: Applications that process the data securely
 - **💾 Data**: Protected information that needs to be processed
@@ -28,22 +28,22 @@ ensure secure, decentralized computation. Here's how the ecosystem operates:
 - **💰 PoCo**: Proof of Contribution system that matches all actors through
   marketplace
 
-### Network Coordination
+### Network coordination
 
 The iExec network coordinates all actors through the PoCo (Proof of
 Contribution) system, which automatically matches requesters with the
 appropriate applications, data, and computational resources based on
 availability, requirements, and pricing.
 
-### Deal Execution Flow
+### Deal execution flow
 
 When a deal is triggered, the following sequence occurs:
 
 1. **Request Creation**: Requester submits a computation request with parameters
 2. **Resource Matching**: PoCo system matches the request with available
    applications, data, and computational resources
-3. **Deal Creation**: When compatible resources are found, a deal is created
-   containing multiple tasks
+3. **Deal Creation**: When the system finds compatible resources, it creates a
+   deal containing multiple tasks
 4. **Task Distribution**: Selected workerpool manager distributes tasks to their
    workers
 5. **Secure Execution**: Workers download the iApp and execute it in TEE
@@ -55,11 +55,11 @@ When a deal is triggered, the following sequence occurs:
    network
 9. **Payment Settlement**: RLC tokens are distributed to all participants
 
-### Network Architecture Diagram
+### Network architecture diagram
 
 ![iExec Network Actors](/assets/use-iapp/iexec-actors-diagram.svg)
 
-### Detailed Interaction Flow
+### Detailed interaction flow
 
 1. **Request Submission**: Requester creates a request specifying the iApp,
    Protected Data, etc.
diff --git a/src/protocol/oracle.md b/src/protocol/oracle.md
index f3179ea..1435805 100644
--- a/src/protocol/oracle.md
+++ b/src/protocol/oracle.md
@@ -7,7 +7,7 @@ description: A flexible and secure Oracle Solution
 
 > A flexible and secure Oracle Solution
 
-## Why do we need Oracles?
+## Why are Oracles needed?
 
 The Ethereum blockchain provides a global trustless computer: given some input
 and the smart contract code, the blockchain guarantees execution according to
@@ -31,12 +31,12 @@ 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.
+iExec has 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\)
 
diff --git a/src/protocol/proof-of-contribution.md b/src/protocol/proof-of-contribution.md
index 5af1ae7..d0d0ba2 100644
--- a/src/protocol/proof-of-contribution.md
+++ b/src/protocol/proof-of-contribution.md
@@ -166,7 +166,7 @@ The scheduler computes the signature at step 2.
 
 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.
+the contributions close. The system then enters a 2h reveal phase.
 
 **7. Reveal:**
 
@@ -185,7 +185,7 @@ 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
+Among the objectives of PoCo, the protocol ensures a worker that contributes
 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
diff --git a/src/protocol/tee/intel-sgx.md b/src/protocol/tee/intel-sgx.md
index 7c1d66c..01521b0 100644
--- a/src/protocol/tee/intel-sgx.md
+++ b/src/protocol/tee/intel-sgx.md
@@ -9,7 +9,7 @@ description:
 
 **Intel® Software Guard Extensions (Intel® SGX)** is the first-generation TEE
 technology that enables **Trusted Computing** and **Confidential Computing**. On
-the iExec platform, SGX is the **production-ready, widely-supported TEE
+the iExec platform, SGX is the **production-ready, widely supported TEE
 technology** that powers secure, privacy-preserving applications in the
 decentralized cloud.
 
@@ -21,28 +21,28 @@ can access. Neither the operating system nor any other software can see what's
 happening inside this protected area. Your code and data are completely private
 and secure.
 
-## SGX: The "Application-Level" Security
+## SGX: The "app-level" security
 
 **Intel SGX** is like having a **small, specialized safe** inside your office
 for specific valuable items. It protects individual applications or parts of
 applications.
 
-### Key Characteristics
+### Key characteristics
 
-- **Scope**: Protects specific parts of your application
+- **Scope**: Protects specific parts of your app
 - **Memory**: Limited secure memory (like a small safe)
-- **Code Changes**: Requires modifications to your application
+- **Code Changes**: Requires modifications to your app
 - **Use Case**: Perfect for focused, lightweight applications
 
 **Analogy**: SGX is like installing a small, specialized safe inside your office
 for specific valuable items.
 
-### Visual Representation
+### Visual representation
 
 ```mermaid
 graph TB
     OS[Operating System<br/>Can see everything]
-    App[Regular Application<br/>Visible & Vulnerable]
+    App[Regular App<br/>Visible & Vulnerable]
     Enclave[🔒 SGX Enclave<br/>Protected]
     Data[Sensitive Code & Data<br/>Encrypted]
     OS --> App
@@ -52,9 +52,9 @@ graph TB
     style Data fill:#ffffff,stroke:#00ff00,stroke-width:2px,color:#000000
 ```
 
-## SGX Technology Details
+## SGX technology details
 
-### How SGX Works
+### How SGX works
 
 1. **Enclave Creation**: SGX creates a secure memory region (enclave) that only
    the CPU can access
@@ -64,15 +64,15 @@ graph TB
 4. **Integrity Protection**: The enclave can prove it's running the correct,
    unmodified code
 
-### SGX Limitations
+### SGX limitations
 
 With native Intel® SGX technology, the OS is not a part of the Trusted
 Computing Base (TCB), hence system calls and kernel services are not available
 from an Intel® SGX enclave. This can be limiting as the application will not be
-able to use File System and sockets directly from the code running inside the
+able to use file system and sockets directly from the code running inside the
 enclave.
 
-### iExec's SGX Infrastructure
+### iExec's SGX infrastructure
 
 iExec provides a complete SGX ecosystem that includes:
 
@@ -90,25 +90,25 @@ To build Confidential Computing (TEE) applications with SGX, iExec uses the
 high-level **Scone framework** instead of requiring developers to manipulate the
 Intel® SGX SDK directly.
 
-#### Scone Framework Benefits
+#### Scone framework benefits
 
 At a high-level, Scone protects the confidentiality and integrity of the data
-and the code without needing to modify or recompile the application. The
+and the code without needing to modify or recompile the app. The
 [Scone](https://scontain.com/) framework resolves the limitations of native SGX
-and reduces the burden of porting the application to Intel® SGX.
+and reduces the burden of porting the app to Intel® SGX.
 
-#### How Scone Works
+#### How Scone works
 
 More precisely, Scone provides a C standard library interface to container
 processes. System calls are executed outside of the enclave, but they are
-shielded by transparently encrypting/decrypting application data. Files stored
-outside of the enclave are therefore encrypted, and network communication is
-protected by Transport Layer Security (TLS).
+shielded by transparently encrypting/decrypting app data. Files stored outside
+of the enclave are therefore encrypted, and network communication is protected
+by Transport Layer Security (TLS).
 
 For a deeper understanding, you can have a look to the official
 [Scone documentation](https://sconedocs.github.io/).
 
-### iExec SGX Workflow
+### iExec SGX workflow
 
 ```mermaid
 graph TD
@@ -131,7 +131,7 @@ graph TD
     style Execute fill:#ffffff,stroke:#0000ff,stroke-width:2px,color:#000000
 ```
 
-## What's Next?
+## What's next?
 
 **Learn about the next generation**:
 
@@ -143,6 +143,6 @@ graph TD
 **Ready to build with SGX?** Check out the practical guides:
 
 - **[Deploy & Run](/guides/build-iapp/deploy-&-run)** - Create your first SGX
-  application
+  app
 - **[Advanced SGX Development](/guides/build-iapp/advanced/build-your-first-sgx-iapp)** -
   Deep dive into SGX development
diff --git a/src/protocol/tee/intel-tdx.md b/src/protocol/tee/intel-tdx.md
index eafd3cf..8b39abf 100644
--- a/src/protocol/tee/intel-tdx.md
+++ b/src/protocol/tee/intel-tdx.md
@@ -19,7 +19,7 @@ memory-intensive workloads and legacy application migration.
 technology that provides VM-level protection, allowing entire virtual machines
 to run in secure, isolated environments.
 
-### Key TDX Benefits
+### Key TDX benefits
 
 1. **🔄 Lift-and-Shift Compatibility**: Run existing applications with minimal
    changes
@@ -35,7 +35,7 @@ to run in secure, isolated environments.
 your existing operations without major renovations. It protects entire virtual
 machines.
 
-### Key Characteristics
+### Key characteristics
 
 - **Scope**: Protects entire virtual machines
 - **Memory**: Large secure memory space (like a large vault)
@@ -45,7 +45,7 @@ machines.
 **Analogy**: TDX is like moving your entire office into a secure building where
 everything is protected.
 
-### Visual Representation
+### Visual representation
 
 ```mermaid
 graph TB
@@ -62,7 +62,7 @@ graph TB
 
 ## TDX Technology Details
 
-### How TDX Works
+### How TDX works
 
 1. **Trust Domain Creation**: TDX creates secure virtual machines called "trust
    domains"
diff --git a/src/protocol/tee/sgx-vs-tdx.md b/src/protocol/tee/sgx-vs-tdx.md
index 3b8ddfe..6852640 100644
--- a/src/protocol/tee/sgx-vs-tdx.md
+++ b/src/protocol/tee/sgx-vs-tdx.md
@@ -11,7 +11,7 @@ problem differently.** On the iExec platform, SGX is the **production-ready,
 widely-supported technology**, while TDX is the **experimental, next-generation
 technology** for advanced use cases.
 
-## Quick Overview
+## Quick overview
 
 | Aspect                  | Intel SGX                       | Intel TDX                 |
 | ----------------------- | ------------------------------- | ------------------------- |
@@ -24,7 +24,7 @@ technology** for advanced use cases.
 | **iExec Use Cases**     | Lightweight applications        | Complex workloads         |
 | **Platform Support**    | Full iExec ecosystem            | Experimental workerpools  |
 
-## Key Differences
+## Key differences
 
 ### 🎯 **Protection Scope**
 
@@ -53,7 +53,7 @@ technology** for advanced use cases.
 
 ## When to Use Each Technology
 
-### Use SGX When
+### Use SGX when
 
 - ✅ Building production applications
 - ✅ Need proven, stable technology
@@ -61,7 +61,7 @@ technology** for advanced use cases.
 - ✅ Require maximum worker availability
 - ✅ Need focused security for specific application parts
 
-### Use TDX When
+### Use TDX when
 
 - 🔬 Experimenting with next-generation technology
 - 💾 Working with memory-intensive applications
diff --git a/src/references/dataProtector/advanced/apps-whitelist.md b/src/references/dataProtector/advanced/apps-whitelist.md
index 8eb4266..63fda76 100644
--- a/src/references/dataProtector/advanced/apps-whitelist.md
+++ b/src/references/dataProtector/advanced/apps-whitelist.md
@@ -6,14 +6,14 @@ description:
   Environment (TEE) iApp and whitelist usage for secure data delivery.
 ---
 
-# Apps Whitelist <ChainNotSupportedBadge />
+# Apps whitelist <ChainNotSupportedBadge />
 
 In order to consume a protected data, an iExec TEE iApp needs to be provided.
 
 ::: tip
 
 **TEE** stands for Trusted Execution Environment. Find more details
-[here](/protocol/tee/introduction)
+[in the TEE introduction guide](/protocol/tee/introduction)
 
 :::
 
@@ -21,7 +21,7 @@ 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](/references/dataProtector/dataProtectorSharing/collection/addToCollection#addonlyappwhitelist)).
+   [in the addToCollection documentation](/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.
 
@@ -31,7 +31,7 @@ The story goes as follow:
    &nbsp;`app` parameter). This chosen application must be in the whitelist
    defined by the collection owner.
 
-## Protected Data Delivery iApp
+## Protected data delivery iApp
 
 Built for the needs of
 [Content Creator use case](https://demo.iex.ec/content-creator/), this iExec TEE
diff --git a/src/references/dataProtector/dataProtectorCore/getGrantedAccess.md b/src/references/dataProtector/dataProtectorCore/getGrantedAccess.md
index 08679c5..418a74a 100644
--- a/src/references/dataProtector/dataProtectorCore/getGrantedAccess.md
+++ b/src/references/dataProtector/dataProtectorCore/getGrantedAccess.md
@@ -191,7 +191,7 @@ const listGrantedAccess = await dataProtectorCore.getGrantedAccess({
 });
 ```
 
-## Return value
+## Return Value
 
 ```ts twoslash
 import { type GrantedAccessResponse } from '@iexec/dataprotector';
diff --git a/src/references/dataProtector/dataProtectorSharing/consume/consumeProtectedData.md b/src/references/dataProtector/dataProtectorSharing/consume/consumeProtectedData.md
index 98292e2..dc61707 100644
--- a/src/references/dataProtector/dataProtectorSharing/consume/consumeProtectedData.md
+++ b/src/references/dataProtector/dataProtectorSharing/consume/consumeProtectedData.md
@@ -3,7 +3,8 @@ title: consumeProtectedData
 description:
   Consume protected data in iExec by visualizing or downloading it. This method
   involves generating RSA keys, interacting with iExec's Secret Management
-  Service, and securely retrieving encrypted data from IPFS.
+  Service, and securely retrieving encrypted data from InterPlanetary File
+  System (IPFS).
 ---
 
 # consumeProtectedData <ChainNotSupportedBadge />
@@ -81,8 +82,9 @@ const consumeProtectedDataResult =
 
 **Type:** `AddressOrENS`
 
-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.
+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 {
@@ -212,7 +214,7 @@ public key, you can reuse it in further calls.
 
 Alternatively, you can generate a RSA keypair on your own.
 
-If a public key is provided, its corresponding private key needs also to be
+If you provide a public key, you must also provide its corresponding private key
 provided.
 
 ```ts twoslash
@@ -241,7 +243,7 @@ private key, you can reuse it in further calls.
 
 Alternatively, you can generate a RSA keypair on your own.
 
-If a private key is provided, its corresponding public key needs also to be
+If you provide a private key, you must also provide its corresponding public key
 provided.
 
 ```ts twoslash
diff --git a/src/references/dataProtector/migrate-from-v1.md b/src/references/dataProtector/migrate-from-v1.md
index 3a1844a..90640e5 100644
--- a/src/references/dataProtector/migrate-from-v1.md
+++ b/src/references/dataProtector/migrate-from-v1.md
@@ -126,7 +126,7 @@ access revocation processes more interactive and manageable.
 
 :::
 
-## Protected Data Schema
+## Protected data schema
 
 The serialization of the data protected by `protectData()` has been changed to
 support a wider range of numbers, and extend the support for processing
diff --git a/src/references/glossary.md b/src/references/glossary.md
index dac449a..78210e7 100644
--- a/src/references/glossary.md
+++ b/src/references/glossary.md
@@ -7,12 +7,12 @@ description: iExec terms glossary
 
 ## A
 
-### Application
+### App
 
-A computer program designed to automate processes. An application is generally
-under the control of different communities such as product managers, project
-owners, or data center administrators. An application can also be decentralized
-thanks to the blockchain: see [DApp](#decentralized-application-dapp).
+A computer program designed to automate processes. An app is generally under the
+control of different communities such as product managers, project owners, or
+data center administrators. An app can also be decentralized thanks to the
+blockchain: see [DApp](#decentralized-application-dapp).
 
 ### Attestation
 
@@ -62,21 +62,20 @@ for more information
 
 ## D
 
-### Decentralized Application (DApp)
+### Decentralized App (DApp)
 
-An application 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 application
-where the backend code is running in fully controlled environments.
+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.
 
-See [Application](#application) for more information.
+See [App](#app) for more information.
 
 ### DApp Provider
 
-Writes, configures, and deploys applications on the iExec platform. Those
-applications can be DApps or legacy (traditional) applications. Providers can
-make their applications available for free or ask for a fixed fee for each use
-of their application.
+Writes, configures, and deploys apps on the iExec platform. Those apps can be
+DApps or legacy (traditional) apps. Providers can make their apps available for
+free or ask for a fixed fee for each use of their app.
 
 ### Dataset
 
@@ -101,7 +100,7 @@ marketplace and recorded in the PoCo smart contract.
 ### Enclave
 
 In confidential computing jargon, an "enclave" is the special memory zone
-protected by the CPU. For simplicity's sake, we can refer to private regions of
+protected by the CPU. For simplicity's sake, you can refer to private regions of
 memory defined by Intel® SGX application as "enclaves".
 
 **Key Points**:
@@ -170,7 +169,7 @@ where sensitive code and data can run safely.
 
 **Characteristics**:
 
-- **Scope**: Application-level protection
+- **Scope**: App-level protection
 - **Memory**: Limited secure memory (like a small safe)
 - **Code Changes**: Requires significant modifications
 - **Best For**: Focused, lightweight applications
@@ -216,8 +215,8 @@ A decentralized method that enables to generate a new token without the
 involvement of a central authority. It can either be a non-fungible token or a
 crypto coin.
 
-Please note that minting an NFT (non-fungible token) is a different procedure.
-To mint an NFT, users usually sign up with a cryptocurrecny wallet on an NFT
+Please note that minting a Non-Fungible Token (NFT) is a different procedure. To
+mint an NFT, users usually sign up with a cryptocurrecny wallet on an NFT
 marketplace (or other platform). Then that create an NFT by uploading a file and
 paying for the creation. Once the transaction is verified, a new NFT is minted.
 This process to add NFTs to a blockchain allows creators to sell their photos,
@@ -251,8 +250,8 @@ See [Deal](#deal) and [PoCo](#poco-proof-of-contribution) for more information.
 A term of affection used to designate the iExec community. Oilers are said to be
 holding "digital oil". This term could also be in reference to the iExec
 whitepaper that states: " iExec introduces a new paradigm in cloud computing: it
-will allow the trading of computing resources as commodities; in the same way we
-may observe with resources such as oil, gold or rice."
+will allow the trading of computing resources as commodities; in the same way
+markets may observe with resources such as oil, gold or rice."
 
 ### Oracle
 
@@ -358,7 +357,7 @@ contracts could do".
 
 ### SMS (Secret Management Service)
 
-An encrypted database where users' secrets are stored.
+An encrypted database that stores users' secrets.
 
 ### sRLC
 
@@ -430,8 +429,8 @@ special security measures that keep its contents completely private and secure.
 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; 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)
+plans to grow and succeed. iExec's whitepaper is available at
+[iEx.ec/whitepaper](https://www.iex.ec/whitepaper)
 
 ### Workers
 
diff --git a/src/references/iapp-generator.md b/src/references/iapp-generator.md
index bfabf38..28f393d 100644
--- a/src/references/iapp-generator.md
+++ b/src/references/iapp-generator.md
@@ -9,7 +9,7 @@ description:
 # 🤖 iApp Generator
 
 **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
+that builds apps running inside TEEs. You write code, iExec handles the
 confidential computing setup.
 
 ## What is iApp Generator?
@@ -64,7 +64,7 @@ Ready for production? Dive into specialized topics:
 Your code runs in Intel SGX/TDX enclaves. Even the worker running your app can't
 see what's happening inside.
 
-### You build, we handle the TEE complexity
+### You build, iExec handles the TEE complexity
 
 Write normal application code. iApp Generator handles secure deployment, worker
 coordination, and result encryption.
diff --git a/src/references/iapp-generator/building-your-iexec-app.md b/src/references/iapp-generator/building-your-iexec-app.md
index b51b069..815c503 100644
--- a/src/references/iapp-generator/building-your-iexec-app.md
+++ b/src/references/iapp-generator/building-your-iexec-app.md
@@ -2,19 +2,19 @@
 title: Build Your iApp
 description:
   Learn how to initialize, configure, and build your iExec application using the
-  iApp Generator CLI with step-by-step guidance.
+  iApp Generator command-line tool with step-by-step guidance.
 ---
 
 # 🧑‍🏭 Build your iApp
 
 ## 🧰 Initialize your iApp
 
-The iApp (iExec Application) Generator CLI simplifies the setup of your iApp by
-guiding you through a step-by-step initialization process. This ensures your
-iApp is correctly configured and compatible with iExec's confidential computing
-environment.
+The iApp (iExec App) Generator command-line tool simplifies the setup of your
+iApp by guiding you through a step-by-step initialization process. This ensures
+your iApp is correctly configured and compatible with iExec's confidential
+computing environment.
 
-### 🏗 Define your Project
+### 🏗 Define your project
 
 <CLIDemo
   initialCommand="iapp init"
diff --git a/src/references/iapp-generator/deserializer.md b/src/references/iapp-generator/deserializer.md
index 2b280c5..4c4b4c6 100644
--- a/src/references/iapp-generator/deserializer.md
+++ b/src/references/iapp-generator/deserializer.md
@@ -13,7 +13,7 @@ protected data that your wallet and iApp are authorized to use. To achieve this,
 you must deserialize the content of the protected data with the expected data
 schema.
 
-To simplify this process, you can use our lightweight utility package,
+To simplify this process, you can use the 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 use the
 information securely.
@@ -21,8 +21,9 @@ information securely.
 ## Overview
 
 This deserializer is built on the
-[Borsh technical specification](https://borsh.io/). We developed this JavaScript
-library to simplify deserialization in your iApp built with JavaScript.
+[Borsh technical specification](https://borsh.io/). iExec developed this
+JavaScript library to simplify deserialization in your iApp built with
+JavaScript.
 
 ::: warning
 
@@ -31,8 +32,8 @@ 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.
+file, the system stores binary values as is while it handles boolean, numbers,
+and strings 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/methods/sendEmail.md b/src/references/web3mail/methods/sendEmail.md
index 2aed89b..76543d4 100644
--- a/src/references/web3mail/methods/sendEmail.md
+++ b/src/references/web3mail/methods/sendEmail.md
@@ -320,7 +320,8 @@ explorer</a> .
 
 ### Validation Errors
 
-We use [yup](https://github.com/jquense/yup) to validate input parameters.
+The system uses [yup](https://github.com/jquense/yup) to validate input
+parameters.
 
 In case one is not valid, you'll get **a yup ValidationError**.
 
@@ -362,8 +363,8 @@ If not, you'll get a `WorkflowError` in the form of:
 
 ### iExec Protocol Errors
 
-In case the iExec stack is to blame, we'll make it clear and you'll get a
-specific `WorkflowError`:
+In case the iExec stack is to blame, the system will make it clear and you'll
+get a specific `WorkflowError`:
 
 ```json5
 {
diff --git a/src/references/web3telegram/getting-started.md b/src/references/web3telegram/getting-started.md
index 36fedb0..75f15d6 100644
--- a/src/references/web3telegram/getting-started.md
+++ b/src/references/web3telegram/getting-started.md
@@ -5,7 +5,7 @@ description:
   Telegram messages. Install the SDK and integrate it with your Web3 project.
 ---
 
-# Getting Started
+# Getting started
 
 [![GitHub package.json version (branch)](https://img.shields.io/github/package-json/v/iExecBlockchainComputing/web3telegram-sdk?color=green)](https://github.com/iExecBlockchainComputing/web3telegram-sdk)