@@ -18,7 +18,7 @@ requires RLC. Every piece of protected data consumed requires RLC. Every app
1818execution requires RLC. The more builders use iExec tools, the more RLC has to
1919be bought and used by builder leveraging iExec's technology.
2020
21- ## 🎯 Why RLC Matters
21+ ## Why RLC Matters
2222
2323** iExec's adoption is linearly correlated to the real-time usage of the RLC
2424token** When developers build with iExec tools, RLC gets used. More privacy apps
@@ -39,7 +39,7 @@ All stakeholders earn RLC when people use their contributions.
3939More developers using iExec's privacy tools means more RLC utility in real
4040dApps. iExec builds actionable privacy, not just protocols.
4141
42- ## 💰 Transparent Payment Flow
42+ ## Transparent Payment Flow
4343
4444When you pay for a task execution with RLC, your payment is automatically and
4545transparently distributed to all iExec protocol participants:
@@ -66,7 +66,7 @@ during the task period. In exchange, you receive **sRLC (staked RLC)**. Once the
6666task is completed, you can recover the RLC that wasn't consumed for the task
6767payment.
6868
69- ### 📊 Ecosystem Growth Metrics
69+ ### Ecosystem Growth Metrics
7070
7171::: info Circulating Supply
7272
@@ -93,7 +93,7 @@ ecosystem requires RLC:
9393- Confidential computations need RLC for execution
9494- Staking mechanisms lock RLC, reducing circulating supply
9595
96- ## 🔄 Getting RLC
96+ ## Getting RLC
9797
9898You can acquire RLC tokens through several methods:
9999
@@ -134,7 +134,7 @@ You can acquire RLC tokens through several methods:
134134 />
135135</div >
136136
137- ## 🚀 Ready to Get Started?
137+ ## Ready to Get Started?
138138
139139Ready to dive into the iExec ecosystem? Here are the next steps:
140140
0 commit comments