iExecBlockchainComputing · Le-Caignec · Nov 10, 2025 · Nov 6, 2025 · Nov 6, 2025
diff --git a/src/get-started/develop-with-ai.md b/src/get-started/develop-with-ai.md
@@ -5,13 +5,13 @@
   privacy-first applications with iExec
 ---
 
-# 🤖 Develop with AI
+# Develop with AI
 
 AI tools accelerate building privacy-first applications with iExec using
 AI-powered development tools. This guide covers how to effectively use AI
 assistants while maintaining security best practices.
 
-## 📚 Documentation for LLMs and AI Code Editors
+## Documentation for LLMs and AI Code Editors
 
 You can use MCP (Model Control Protocol) servers like
 [Context7](https://context7.com/iexecblockchaincomputing/documentation) to
@@ -21,7 +21,7 @@
 - Architecture suggestions for privacy-first apps
 - Code explanation and best practices
 
-## 🎨 Vibe Coding Integration
+## Vibe Coding Integration
 
 Vibe coding lets you build applications by describing what you want in plain
 language. An AI assistant (like Cursor or ChatGPT) then generates code based on
@@ -37,7 +37,7 @@
 
 - You review and adjust until it works
 
-## ⚠️ Security Considerations
+## Security Considerations
 
 While vibe coding is powerful, it's important to keep privacy and security in
 mind:

diff --git a/src/get-started/overview/rlc.md b/src/get-started/overview/rlc.md
@@ -18,7 +18,7 @@
 execution requires RLC. The more builders use iExec tools, the more RLC has to
 be bought and used by builder leveraging iExec's technology.
 
-## 🎯 Why RLC Matters
+## Why RLC Matters
 
 **iExec's adoption is linearly correlated to the real-time usage of the RLC
 token** When developers build with iExec tools, RLC gets used. More privacy apps
@@ -39,7 +39,7 @@
 More developers using iExec's privacy tools means more RLC utility in real
 dApps. iExec builds actionable privacy, not just protocols.
 
-## 💰 Transparent Payment Flow
+## Transparent Payment Flow
 
 When you pay for a task execution with RLC, your payment is automatically and
 transparently distributed to all iExec protocol participants:
@@ -66,7 +66,7 @@
 task is completed, you can recover the RLC that wasn't consumed for the task
 payment.
 
-### 📊 Ecosystem Growth Metrics
+### Ecosystem Growth Metrics
 
 ::: info Circulating Supply
 
@@ -93,7 +93,7 @@
 - Confidential computations need RLC for execution
 - Staking mechanisms lock RLC, reducing circulating supply
 
-## 🔄 Getting RLC
+## Getting RLC
 
 You can acquire RLC tokens through several methods:
 
@@ -134,7 +134,7 @@
   />
 </div>
 
-## 🚀 Ready to Get Started?
+## Ready to Get Started?
 
 Ready to dive into the iExec ecosystem? Here are the next steps:
 

diff --git a/src/get-started/tooling-and-explorers/blockchain-explorer.md b/src/get-started/tooling-and-explorers/blockchain-explorer.md
@@ -5,13 +5,13 @@
   Arbitrum mainnet and Bellecour network.
 ---
 
-# 🔍 Blockchain Explorers
+# Blockchain Explorers
 
 Monitor iExec protocol smart contracts on all supported networks through
 verified blockchain explorers. All protocol contracts have been verified and are
 publicly auditable.
 
-## 🌐 Supported Networks
+## Supported Networks
 
 <div class="grid grid-cols-1 gap-8 my-8">
   <UseCaseCard

diff --git a/src/get-started/tooling-and-explorers/bridge.md b/src/get-started/tooling-and-explorers/bridge.md
@@ -24,7 +24,7 @@
 
 :::
 
-## 🗂️ Available Bridges
+## Available Bridges
 
 iExec provides officially supported bridges for seamless token transfer across
 networks:
@@ -55,7 +55,7 @@
   />
 </CardGrid>
 
-## ⚡ Stargate Bridge
+## Stargate Bridge
 
 The **Stargate Bridge** powered by LayerZero enables cross-chain transfers of
 RLC tokens between Ethereum and Arbitrum mainnet in both directions.
@@ -77,7 +77,7 @@
   link-url="https://stargate.finance/bridge"
 />
 
-## 🔄 Bellecour Bridge
+## Bellecour Bridge
 
 The **Bellecour Bridge** enables seamless transfer of RLC tokens between
 Ethereum mainnet and the Bellecour sidechain in both directions. When bridged to
@@ -113,7 +113,7 @@
 
 :::
 
-## 🔒 Security & Audits
+## Security & Audits
 
 The **Stargate Bridge** uses the **LayerZero protocol** under the hood, which
 provides secure cross-chain communication infrastructure. LayerZero is a

diff --git a/src/get-started/tooling-and-explorers/builder-dashboard.md b/src/get-started/tooling-and-explorers/builder-dashboard.md
@@ -5,7 +5,7 @@
   iApp and your manage vouchers
 ---
 
-# 🏗️ Builder Dashboard
+# Builder Dashboard
 
 The **Builder Dashboard** is your comprehensive development hub for iExec
 protocol. Monitor voucher usage, track your remaining compute capacity for TEE
@@ -20,7 +20,7 @@
   caption="Access the Builder Dashboard"
 />
 
-## 🎯 Key Features
+## Key Features
 
 <CardGrid>
   <FeatureCard
@@ -34,7 +34,7 @@
   />
 </CardGrid>
 
-## 📊 Voucher Consumption & Task History
+## Voucher Consumption & Task History
 
 The first screen of the Builder Dashboard provides comprehensive voucher
 monitoring with detailed task execution history and real-time balance tracking.
@@ -81,7 +81,7 @@
   />
 </CardGrid>
 
-## 📱 Confidential iApp Management
+## Confidential iApp Management
 
 The second screen provides comprehensive management and analytics for your
 deployed confidential iApp with detailed statistics and user insights.

diff --git a/src/get-started/tooling-and-explorers/faucet.md b/src/get-started/tooling-and-explorers/faucet.md
@@ -5,7 +5,7 @@
   workerpools, and protected datasets without spending real tokens.
 ---
 
-# 🚰 RLC Faucet
+# RLC Faucet
 
 Get free RLC tokens on **Arbitrum Sepolia testnet** to test your iApps, pay for
 workerpool executions, and access protected datasets without spending real
@@ -34,7 +34,7 @@
   distribution)
 - **One claim per 24 hours** per authenticated account
 
-## 💰 Claim Details
+## Claim Details
 
 <UseCaseCard
   title="🚰 iExec RLC Faucet"

diff --git a/src/get-started/tooling-and-explorers/iexec-explorer.md b/src/get-started/tooling-and-explorers/iexec-explorer.md
@@ -5,7 +5,7 @@
   platform. Monitor deals, tasks, apps, and datasets in real-time.
 ---
 
-# 🔍 iExec Explorer
+# iExec Explorer
 
 The **iExec Explorer** is your real-time window into the iExec confidential
 decentralized computing protocol. Track deals, monitor task execution, and
@@ -25,7 +25,7 @@
 
 :::
 
-## 🎯 What you Can Explore
+## What you Can Explore
 
 <CardGrid>
   <FeatureCard

diff --git a/src/get-started/tooling-and-explorers/subgraph-explorer.md b/src/get-started/tooling-and-explorers/subgraph-explorer.md
@@ -6,7 +6,7 @@
   networks.
 ---
 
-# 🔍 The Graph Explorer
+# The Graph Explorer
 
 The **iExec protocol** uses **The Graph** as a decentralized protocol for
 indexing and querying blockchain data across multiple networks. This powerful
@@ -19,7 +19,7 @@
   link-url="https://thegraph.com/docs/en/subgraphs/quick-start/"
 />
 
-## 🎯 What is the Graph?
+## What is the Graph?
 
 The Graph is a decentralized protocol for indexing and querying blockchain data.
 It enables developers to build and publish open API called **subgraphs** that
@@ -41,7 +41,7 @@
 - **GraphQL Interface**: Powerful query language for flexible data retrieval
 - **Multi-network Support**: Access data across different blockchain networks
 
-## 🗂️ Available Subgraphs
+## Available Subgraphs
 
 iExec has deployed several subgraphs across different networks to provide
 comprehensive data access. Each subgraph indexes specific aspects of the iExec
@@ -117,7 +117,7 @@
 
 </CardGrid>
 
-## 🔍 GraphQL Explorer Interface
+## GraphQL Explorer Interface
 
 The Graph provides an interactive GraphQL explorer that allows you to build and
 test queries directly in your browser. This powerful interface makes it easy to

diff --git a/src/get-started/welcome.md b/src/get-started/welcome.md
@@ -145,7 +145,7 @@
 
 </Container>
 
-## 🚀 Start Building
+## Start Building
 
 Ready to build privacy-first applications? Choose your path:
 

diff --git a/src/guides/build-iapp/advanced/build-your-first-tdx-iapp.md b/src/guides/build-iapp/advanced/build-your-first-tdx-iapp.md
@@ -5,7 +5,7 @@
   technology using both traditional deployment and the iApp Generator
 ---
 
-# 🛡️ Build Intel TDX iApp <ChainNotSupportedBadge/>
+# Build Intel TDX iApp <ChainNotSupportedBadge/>
 
 In this tutorial, you will learn how to build and run a Confidential Computing
 application with Intel TDX technology using both traditional deployment and the
@@ -257,7 +257,7 @@
 
 ## What's Next?
 
-### 🔧 **Continue with TDX Development**
+### **Continue with TDX Development**
 
 **Enhance your TDX application**:
 
@@ -269,7 +269,7 @@
 - **[iApp Access Control and Pricing](/guides/build-iapp/manage-access)** -
   Configure access control for your TDX applications
 
-### 📚 **Learn More About TEE Technologies**
+### **Learn More About TEE Technologies**
 
 **Deepen your understanding**:
 
@@ -280,7 +280,7 @@
 - **[Introduction to TEE Technologies](/protocol/tee/introduction)** -
   Foundation concepts of TEE technologies
 
-### 🚀 **Production Considerations**
+### **Production Considerations**
 
 **For production applications**:
 
@@ -291,7 +291,7 @@
 - **[Deploy & Run](/guides/build-iapp/deploy-&-run)** - Standard iApp deployment
   guide
 
-### 🔗 **Related Resources**
+### **Related Resources**
 
 **Explore the iExec ecosystem**:
 

diff --git a/src/guides/build-iapp/advanced/result-callback.md b/src/guides/build-iapp/advanced/result-callback.md
@@ -18,7 +18,7 @@ Use a callback when your smart contract should:
 - Store a timestamped record (price feed, score, KPI, proof hash)
 - Bridge logic between external systems and on-chain state
 
-## 🧩 High-level flow
+## High-level flow
 
 1. A requester deploys the smart contract that should receive the callback data.
 2. The requester executes an iApp and specifies the callback address.
@@ -154,7 +154,7 @@ const taskId = await iexec.order.matchOrders({
 });
 ```
 
-## 🔄 Other use cases
+## Other use cases
 
 | Use Case             | Description                              |
 | -------------------- | ---------------------------------------- |

diff --git a/src/guides/build-iapp/debugging.md b/src/guides/build-iapp/debugging.md
@@ -4,7 +4,7 @@
   Troubleshoot and optimize your iApp execution in the TEE environment
 ---
 
-# 🐛 Debugging
+# Debugging
 
 **When your iApp doesn't work as expected, debugging in the TEE environment
 requires specific techniques.** This guide helps you identify issues and
@@ -88,18 +88,18 @@
 
 ## Common Issues
 
-### ⏱️ **Task Timeout**
+### **Task Timeout**
 
 - **Cause**: Code takes too long to execute
 - **Solution**: Optimize algorithms, reduce input sizes, use appropriate task
   category
 
-### 💾 **Memory Issues**
+### **Memory Issues**
 
 - **Cause**: Loading large files, memory leaks, TEE constraints
 - **Solution**: Process data in chunks, use streaming, optimize memory usage
 
-### 📁 **Input/Output Problems**
+### **Input/Output Problems**
 
 - **Cause**: Wrong file paths, missing `computed.json`
 - **Solution**: Always create `computed.json`, verify environment variables
@@ -112,15 +112,15 @@
     json.dump(computed, f)
 ```
 
-### ⚠️ **Dataset Type Unmatching**
+### **Dataset Type Unmatching**
 
 - **Cause**: The dataset type specified in the frontend (protectData) does not
   match with the dataset type specified in the iApp
 - **Solution**: Check both dataset types
 
 ## Best Practices
 
-### 🔍 **Input Validation**
+### **Input Validation**
 
 ```python
 import os, sys
@@ -136,7 +136,7 @@
     sys.exit(1)
 ```
 
-### 📝 **Clear Error Messages**
+### **Clear Error Messages**
 
 ```python
 try:
@@ -147,7 +147,7 @@
     sys.exit(1)
 ```
 
-### 🔒 **Safe File Operations**
+### **Safe File Operations**
 
 ```python
 import os, json