docs: Refactor iApp guides for improved clarity and structure

- Enhanced the 'Build and Test an iApp' and 'Deploy and Run an iApp' guides by breaking long lines in descriptions for better readability.
- Removed the outdated 'Run an iApp' and 'Run iApp with Inputs' guides to streamline documentation.
- Updated descriptions and sections to improve clarity and consistency across the guides.

Author: Le-Caignec

src/guides/build-iapp/build-&-test.md

@@ -1,7 +1,8 @@
 ---
 title: Build and Test an iApp
 description:
-  Learn how to build, test, and package your iExec application using the iApp Generator CLI tool
+  Learn how to build, test, and package your iExec application using the iApp
+  Generator CLI tool
 ---
 
 # Build and Test an iApp

src/guides/build-iapp/deploy-&-run.md

@@ -1,12 +1,14 @@
 ---
 title: Deploy and Run an iApp
 description:
-  Deploy your iApp to supported networks and learn how to execute it using the iApp Generator CLI
+  Deploy your iApp to supported networks and learn how to execute it using the
+  iApp Generator CLI
 ---
 
 # Deploy and Run an iApp
 
-It's time to run your iApp! After building and testing, you'll need to deploy it to a supported network and then execute it.
+It's time to run your iApp! After building and testing, you'll need to deploy it
+to a supported network and then execute it.
 
 ## Deploy your iApp
 
@@ -40,7 +42,11 @@ specify your app version, and push both standard and TEE-compatible images:
   />
 </template>
 
-Now that your iApp has been deployed on the iExec protocol, you can navigate to the `cache` folder to see your deployments saved. A file named `deployments.json` in the folder corresponding to your target network will be created containing each deployment made on this network. These files will help you easily track each deployment per network.
+Now that your iApp has been deployed on the iExec protocol, you can navigate to
+the `cache` folder to see your deployments saved. A file named
+`deployments.json` in the folder corresponding to your target network will be
+created containing each deployment made on this network. These files will help
+you easily track each deployment per network.
 
 Here is an example:
 
@@ -96,7 +102,12 @@ for developers who have built their own iApp.
   />
 </template>
 
-Now that you have run your iApp on the iExec protocol, you can navigate to the `cache` folder to see your runs saved. A file named `runs.json` in the folder corresponding to your target network will be created containing each run made on this network. These files will help you easily track each run per network. Use the [iExec Explorer](/guides/tooling-and-explorers/iexec-explorer) to retrieve more data about your tasks.
+Now that you have run your iApp on the iExec protocol, you can navigate to the
+`cache` folder to see your runs saved. A file named `runs.json` in the folder
+corresponding to your target network will be created containing each run made on
+this network. These files will help you easily track each run per network. Use
+the [iExec Explorer](/guides/tooling-and-explorers/iexec-explorer) to retrieve
+more data about your tasks.
 
 Here is an example:
 
@@ -116,7 +127,8 @@ Here is an example:
 ## Next Steps
 
 - Learn how to [manage access to your iApp](/guides/build-iapp/manage-access)
-- Discover [debugging techniques](/guides/build-iapp/debugging) for troubleshooting
+- Discover [debugging techniques](/guides/build-iapp/debugging) for
+  troubleshooting
 
 <script setup>
 import CLIDemo from '@/components/CLIDemo.vue';

src/guides/use-iapp/run-iapp-with-ProtectedData.md

@@ -0,0 +1,128 @@
+---
+title: Run iApp with ProtectedData
+description:
+  Learn how to run iApp with encrypted protected data, arguments, and input files using the DataProtector toolkit for secure data processing
+---
+
+# 📥 Run iApp with a ProtectedData
+
+When an iApp requires additional data or parameters to function, you can provide
+various types of inputs to customize its behavior and enable processing. This
+guide covers all the different ways to run an iApp with inputs using the
+DataProtector turnkey toolkit.
+
+## Possible Inputs
+
+iExec supports several types of inputs for iApp executions:
+
+1. **Protected Data**: Encrypted data processed within the TEE
+2. **Arguments**: Command-line arguments passed to the application
+3. **Input Files**: URLs to public files that the app can download
+4. **Secrets**: Sensitive data like API keys stored securely
+
+## Adding Protected Data
+
+When working with protected data that contains multiple files, you can specify
+which file to process.
+
+```ts twoslash
+import { IExecDataProtectorCore, getWeb3Provider } from '@iexec/dataprotector';
+
+const web3Provider = getWeb3Provider('PRIVATE_KEY');
+const dataProtectorCore = new IExecDataProtectorCore(web3Provider);
+// ---cut---
+// Process protected data with specific path
+const result = await dataProtectorCore.processProtectedData({
+  protectedData: '0x123abc...',
+  app: '0x456def...',
+  path: 'data/input.csv',
+});
+```
+
+The `processProtectedData` function will automatically download and decrypt the
+results for you. Nevertheless, if you want to retrieve results from a completed
+task, you can do so as follows:
+
+```ts twoslash
+import { IExecDataProtectorCore, getWeb3Provider } from '@iexec/dataprotector';
+
+const web3Provider = getWeb3Provider('PRIVATE_KEY');
+const dataProtectorCore = new IExecDataProtectorCore(web3Provider);
+const taskId = '0x7ac398...';
+
+// ---cut---
+// Retrieve the result
+const taskResult = await dataProtectorCore.getResultFromCompletedTask({
+  taskId: taskId,
+});
+```
+
+## Adding Command-Line Arguments
+
+Command-line arguments are passed as a string to the iApp and are visible on the
+blockchain.
+
+```ts twoslash
+import { IExecDataProtectorCore, getWeb3Provider } from '@iexec/dataprotector';
+
+const web3Provider = getWeb3Provider('PRIVATE_KEY');
+const dataProtectorCore = new IExecDataProtectorCore(web3Provider);
+// ---cut---
+// Process protected data with arguments
+const result = await dataProtectorCore.processProtectedData({
+  protectedData: '0x123abc...',
+  app: '0x456def...',
+  args: '--input-path data/input.csv --output-format json --verbose',
+});
+```
+
+## Adding Input Files
+
+Input files are URLs to public files that the iApp can download during
+execution.
+
+```ts twoslash
+import { IExecDataProtectorCore, getWeb3Provider } from '@iexec/dataprotector';
+
+const web3Provider = getWeb3Provider('PRIVATE_KEY');
+const dataProtectorCore = new IExecDataProtectorCore(web3Provider);
+// ---cut---
+// Process protected data with input files
+const result = await dataProtectorCore.processProtectedData({
+  protectedData: '0x123abc...',
+  app: '0x456def...',
+  inputFiles: [
+    'https://raw.githubusercontent.com/user/repo/main/config.json',
+    'https://example.com/public-data.csv',
+  ],
+});
+```
+
+## Adding Secrets
+
+Secrets are sensitive data like API keys, passwords, or tokens that are stored
+securely and made available to the iApp as environment variables.
+
+```ts twoslash
+import { IExecDataProtectorCore, getWeb3Provider } from '@iexec/dataprotector';
+
+const web3Provider = getWeb3Provider('PRIVATE_KEY');
+const dataProtectorCore = new IExecDataProtectorCore(web3Provider);
+// ---cut---
+// Process protected data with secrets
+const result = await dataProtectorCore.processProtectedData({
+  protectedData: '0x123abc...',
+  app: '0x456def...',
+  secrets: {
+    1: 'openai-api-key',
+    2: 'database-password',
+  },
+});
+```
+
+## Next Steps
+
+Now that you understand how to add inputs to iApp executions:
+
+- Check out our
+  [How to Pay for Executions](/guides/use-iapp/how-to-pay-executions) guide