fix: correction du terme "iApps" en "iApp" dans la documentation pour assurer la cohérence terminologique

Author: 64ix

src/get-started/overview/iapp.md

@@ -23,7 +23,7 @@ protected data inside a TEE.
 
 ## Why iApp Matters?
 
-iApps provide privacy capabilities, allowing you to process sensitive data while
+iApp provide privacy capabilities, allowing you to process sensitive data while
 keeping it private and secure.
 
 Imagine you want to build:
@@ -38,7 +38,7 @@ Imagine you want to build:
 </CardWithoutBorder>
 
 Users have this data, but they won't trust your regular app with it. **With
-Privacy iApps, they will.**
+Privacy iApp, they will.**
 
 **You gain their trust. They gain their privacy. Everyone wins.**
 
@@ -133,7 +133,7 @@ Collaborative research on sensitive datasets across institutions
 
 Let's build an iApp that can process protected data in a secure environment
 using the [iExec iApp generator tool](/references/iapp-generator). This tool
-helps you create, test and deploy iApps with just a few commands.
+helps you create, test and deploy iApp with just a few commands.
 
 </Banner>
 

src/get-started/overview/protected-data.md

@@ -56,7 +56,7 @@ entries with matching types**.
 <CardWithBorder>
 
 1. **Protect:** Encrypt and register your data on the iExec network
-2. **Share:** Authorize specific users and iApps to access your data
+2. **Share:** Authorize specific users and iApp to access your data
 3. **Monitor:** Track usage and maintain control
 4. **Monetize:** Earn from your data while keeping it private
 5. **Compute:** Authorized users can compute on your data with authorized iApp

src/get-started/toolkit.md

@@ -39,7 +39,7 @@ users to pay for access.
 - **Asset visualization** to easily view and explore protected asset types on
   the iExec protocol
 - **Content consumption** capabilities for accessing protected data through
-  confidential iExec applications (iApps)
+  confidential iExec applications (iApp)
 - **Governance management** to control who accesses your data, when, and at what
   price
 

src/guides/build-iapp/advanced/build-your-first-tdx-iapp.md

@@ -62,7 +62,7 @@ application need to be changed in order to run securely in a TEE. Only two files
 need to be changed compared to the usual SGX workflow: `chain.json` and
 `iexec.json`.
 
-iApps using Intel TDX technology follow the same format as non-TEE applications;
+iApp using Intel TDX technology follow the same format as non-TEE applications;
 follow the instructions on
 [Build your first application](/guides/build-iapp/advanced/build-your-first-sgx-iapp)
 to create and Dockerize your iApp.
@@ -223,8 +223,8 @@ await dataProtector.core.processProtectedData({
 
 :::warning Protected Data Requirements
 
-**TDX iApps may require TDX-compatible protected data.** Check compatibility
-before using protected data with TDX iApps.
+**TDX iApp may require TDX-compatible protected data.** Check compatibility
+before using protected data with TDX iApp.
 
 :::
 
@@ -237,7 +237,7 @@ documentation for TDX-specific requirements.
 #### 1. **Local Testing**
 
 ```bash
-# Test locally (same as regular iApps)
+# Test locally (same as regular iApp)
 iapp test --protectedData "mock_name"
 
 # TDX only affects remote deployment/execution

src/guides/build-iapp/inputs.md

@@ -26,7 +26,7 @@ within the TEE environment.
 
 ::: tip
 
-You can also execute iApps outside of DataProtector using other methods. See the
+You can also execute iApp outside of DataProtector using other methods. See the
 [Use an iApp guide](/guides/use-iapp/introduction) for more information.
 
 :::

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

@@ -55,7 +55,7 @@ await iexec.account.deposit(1_000_000_000); // Deposit 1 RLC
 
 Now you are ready to run a task on the iExec Protocol and pay for it. See our
 guide on
-[running iApps with ProtectedData](/guides/use-iapp/run-iapp-with-ProtectedData.md)
+[running iApp with ProtectedData](/guides/use-iapp/run-iapp-with-ProtectedData.md)
 for detailed execution steps.
 
 ## Paying with Vouchers <ChainNotSupportedBadge />