refactor: remove TokenSymbol component and replace with RLC in documentation

Author: Le-Caignec

src/components/TokenSymbol.vue

@@ -41,17 +41,17 @@ iexec order init --workerpool
 Edit the `workerpoolorder` part in `iexec.json` to set the conditions to use
 your workerpool:
 
-| key                 | description                                                                           |
-| ------------------- | ------------------------------------------------------------------------------------- |
-| `workerpool`        | workerpool address                                                                    |
-| `workerpoolprice`   | price to charge the requester for each execution of the app (in nano <TokenSymbol />) |
-| `volume`            | number of authorized uses, each use decreases this number                             |
-| `tag`               | restrict usage to a specific runtime such as **Scone** or **Gramine** TEE frameworks  |
-| `category`          | Order category, will define the deal `workClockTimeRef` and its deadlines             |
-| `trust`             | Trust level of the execution, impacts the number of replicates                        |
-| `apprestrict`       | restrict the workerpool usage to a specific app (1)                                   |
-| `datasetrestrict`   | restrict the workerpool usage to a specific dataset (1)                               |
-| `requesterrestrict` | restrict the workerpool usage to a specific requester (1)                             |
+| key                 | description                                                                          |
+| ------------------- | ------------------------------------------------------------------------------------ |
+| `workerpool`        | workerpool address                                                                   |
+| `workerpoolprice`   | price to charge the requester for each execution of the app (in nano RLC)            |
+| `volume`            | number of authorized uses, each use decreases this number                            |
+| `tag`               | restrict usage to a specific runtime such as **Scone** or **Gramine** TEE frameworks |
+| `category`          | Order category, will define the deal `workClockTimeRef` and its deadlines            |
+| `trust`             | Trust level of the execution, impacts the number of replicates                       |
+| `apprestrict`       | restrict the workerpool usage to a specific app (1)                                  |
+| `datasetrestrict`   | restrict the workerpool usage to a specific dataset (1)                              |
+| `requesterrestrict` | restrict the workerpool usage to a specific requester (1)                            |
 
 1. the restriction is disabled by default with
    0x0000000000000000000000000000000000000000.
@@ -106,7 +106,3 @@ cancel command.
 ```bash
 iexec order cancel --workerpool <orderHash>
 ```
-
-<script setup>
-import TokenSymbol from '@/components/TokenSymbol.vue'
-</script>

src/get-started/protocol/worker/manage-access.md

@@ -14,13 +14,12 @@ The iExec Worker participates in a workerpool by computing tasks purchased by
 requesters on the iExec marketplace. The iExec Worker must connect to the iExec
 Core Scheduler of the workerpool to actively participate in the computation.
 
-A worker will be rewarded with <TokenSymbol /> for every properly computed
-tasks.
+A worker will be rewarded with RLC for every properly computed tasks.
 
 Please note that:
 
-- your wallet must be loaded with <TokenSymbol />. Some <TokenSymbol /> must be
-  deposited to your iExec account in order to stake for incoming tasks.
+- your wallet must be loaded with RLC. Some RLC must be deposited to your iExec
+  account in order to stake for incoming tasks.
 - your computer needs at least 2 CPUs.
 
 ## Start a worker
@@ -34,18 +33,14 @@ configuration documentation of the
 For security reason, it is **highly recommended** to launch your worker in a
 virtual machine.
 
-After loading some <TokenSymbol /> and depositing them to your iExec account,
-you can start your worker.
+After loading some RLC and depositing them to your iExec account, you can start
+your worker.
 
 When the worker initialization process is complete, the worker will start and
 you will get: **Your worker is all set**. Your worker will now be able to
-compute tasks from the iExec network to earn <TokenSymbol />.
+compute tasks from the iExec network to earn RLC.
 
 ## Wallet restriction
 
 An exclusive wallet must be associated to your worker. You need N wallets if you
 want N workers.
-
-<script setup>
-import TokenSymbol from '@/components/TokenSymbol.vue'
-</script>

src/get-started/protocol/worker/quick-start.md

@@ -40,7 +40,7 @@ Here's the simplified process:
 2. **You sign the order** with your wallet
 3. **You publish the order** on the iExec marketplace
 4. **Users can discover** and execute your iApp according to your conditions
-5. **You automatically receive** payment in <TokenSymbol /> for each execution
+5. **You automatically receive** payment in RLC for each execution
 
 ```
 Deployed iApp + Signed App Order = Application accessible on iExec
@@ -231,12 +231,12 @@ Here's the detailed description of each parameter:
 **Common values:**
 
 - `"0"` - Free
-- `"1000000000"` - 1 <TokenSymbol /> per execution
-- `"500000000"` - 0.5 <TokenSymbol /> per execution
+- `"1000000000"` - 1 RLC per execution
+- `"500000000"` - 0.5 RLC per execution
 
 ::: tip
 
-1 <TokenSymbol /> = 1,000,000,000 nano <TokenSymbol /> (10^9)
+1 RLC = 1,000,000,000 nano RLC (10^9)
 
 :::
 
@@ -301,7 +301,3 @@ Next steps:
   Complete CLI reference
 - **[Official Orders Documentation](https://protocol.docs.iex.ec/for-developers/advanced/manage-your-apporders)** -
   Protocol-level order management
-
-<script setup>
-import TokenSymbol from '@/components/TokenSymbol.vue'
-</script>

src/guides/build-iapp/manage-access.md

@@ -169,7 +169,7 @@ yourself!
 Set to `0` for free access, or specify a price to monetize your data
 automatically.
 
-**Example**: `pricePerAccess: 1_000_000_000` = 1 <TokenSymbol /> per access
+**Example**: `pricePerAccess: 1_000_000_000` = 1 RLC per access
 
 → **Want to learn more monetization capabilities?** See our detailed
 [Monetize Protected Data guide](/guides/manage-data/monetize-protected-data)
@@ -211,5 +211,4 @@ steps:
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
 import OptionalBadge from '@/components/OptionalBadge.vue'
-import TokenSymbol from '@/components/TokenSymbol.vue'
 </script>

src/guides/manage-data/manage-access.md

@@ -14,7 +14,7 @@ and cost management strategies.
 
 iExec supports multiple payment methods for executing iApp:
 
-1. **RLC Tokens**: Direct payment using <TokenSymbol /> tokens
+1. **RLC Tokens**: Direct payment using RLC tokens
 2. **Vouchers**: Pre-funded vouchers for simplified payment
 3. **Mixed Payment**: Combination of RLC and vouchers
 
@@ -103,8 +103,8 @@ balance is insufficient. This ensures that if the voucher alone doesn't cover
 the execution cost, the remaining balance is automatically deducted from your
 account.
 
-For additional information on using <TokenSymbol /> for fallback payment in
-Web3Mail, refer to the **Using <TokenSymbol /> with Web3Mail** section.
+For additional information on using RLC for fallback payment in Web3Mail, refer
+to the **Using RLC with Web3Mail** section.
 
 ### Step 4: Use Voucher
 
@@ -161,10 +161,10 @@ const result = await dataProtectorCore.processProtectedData({
 
 ::: tip
 
-If your voucher doesn't have enough <TokenSymbol /> to cover the deal, the SDK
-will automatically get the required amount to your iExec account. Ensure that
-your voucher is authorized to access your iExec account and that your account
-has sufficient funds for this transfer to proceed.
+If your voucher doesn't have enough RLC to cover the deal, the SDK will
+automatically get the required amount to your iExec account. Ensure that your
+voucher is authorized to access your iExec account and that your account has
+sufficient funds for this transfer to proceed.
 
 :::
 
@@ -239,7 +239,6 @@ Now that you understand payment methods:
 
 <script setup>
 import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
-import TokenSymbol from '@/components/TokenSymbol.vue'
 import ImageViewer from '@/components/ImageViewer.vue';
 
 // Assets

src/guides/use-iapp/how-to-pay-executions.md

@@ -53,8 +53,7 @@ When a deal is triggered, the following sequence occurs:
 7. **Result Generation**: Computation results are generated
 8. **Result Delivery**: Results are returned to the requester through the
    network
-9. **Payment Settlement**: <TokenSymbol /> tokens are distributed to all
-   participants
+9. **Payment Settlement**: RLC tokens are distributed to all participants
 
 ### Network Architecture Diagram
 
@@ -71,8 +70,8 @@ When a deal is triggered, the following sequence occurs:
 5. **Data Access**: iApp requests access to protected data through secure
    channels
 6. **Computation**: iApp processes data within the TEE, maintaining privacy
-7. **Payment Distribution**: <TokenSymbol /> tokens are distributed to all
-   participants based on completed tasks
+7. **Payment Distribution**: RLC tokens are distributed to all participants
+   based on completed tasks
 
 This decentralized architecture ensures that no single entity has control over
 the entire process, while the use of TEEs guarantees that sensitive data remains
@@ -83,7 +82,3 @@ protected throughout the computation.
 Ready to start using iApp? Check out our
 [Getting Started Guide](/guides/use-iapp/getting-started) to learn how to find,
 execute, and interact with iApp on the iExec network.
-
-<script setup>
-import TokenSymbol from '@/components/TokenSymbol.vue'
-</script>

src/guides/use-iapp/introduction.md

@@ -165,7 +165,7 @@ const grantedAccess = await dataProtectorCore.grantAccess({
 ::: tip
 
 `pricePerAccess` is expressed in nano RLC (nRLC). nRLC is the smallest
-subdivision of the <TokenSymbol /> token, 1 <TokenSymbol /> equals to 10^9 nRLC.
+subdivision of the RLC token, 1 RLC equals to 10^9 nRLC.
 
 When provided, `pricePerAccess` must be a non-negative integer value.
 
@@ -254,5 +254,4 @@ The result of this method confirms the new access grant. It consists of a JSON
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
 import OptionalBadge from '@/components/OptionalBadge.vue'
-import TokenSymbol from '@/components/TokenSymbol.vue'
 </script>

src/references/dataProtector/dataProtectorCore/grantAccess.md

@@ -154,10 +154,10 @@ const processProtectedDataResponse =
 
 ::: tip
 
-If your voucher doesn't have enough <TokenSymbol /> to cover the deal, the SDK
-will automatically get the required amount to your iExec account. Ensure that
-your voucher is authorized to access your iExec account and that your account
-has sufficient funds for this transfer to proceed.
+If your voucher doesn't have enough RLC to cover the deal, the SDK will
+automatically get the required amount to your iExec account. Ensure that your
+voucher is authorized to access your iExec account and that your account has
+sufficient funds for this transfer to proceed.
 
 :::
 
@@ -501,5 +501,4 @@ processed during the task.
 import RequiredBadge from '@/components/RequiredBadge.vue'
 import OptionalBadge from '@/components/OptionalBadge.vue'
 import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
-import TokenSymbol from '@/components/TokenSymbol.vue'
 </script>

src/references/dataProtector/dataProtectorCore/processProtectedData.md

@@ -17,8 +17,8 @@ Types in DataProtector.
 
 ### datasetprice: <span class="text-yellow">`string`</span>
 
-- Price (in n<TokenSymbol />) to charge the user specified in
-  `requesterrestrict` for each use of this `protectedData`
+- Price (in nRLC) to charge the user specified in `requesterrestrict` for each
+  use of this `protectedData`
 
 ### volume: <span class="text-yellow">`string`</span>
 
@@ -123,7 +123,3 @@ _Hash example:_ `0xc9c2d58fc01fe54149b7daf49a0026d4ab1fdd3d10fb7c76350790fff03fe
 
 You can read more about he iExec Explorer
 [here](https://protocol.docs.iex.ec/for-developers/toolbox/iexec-explorer).
-
-<script setup>
-import TokenSymbol from '@/components/TokenSymbol.vue'
-</script>