fix format

Author: aimen-djari

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

@@ -203,15 +203,20 @@ const taskId = await iexec.order.matchOrders({
 
 ## 🔐 Encrypt Results (Advanced)
 
-::: info DataProtector handles encryption automatically
-If you're using DataProtector, result encryption is handled automatically. This section is only needed for manual encryption when not using DataProtector.
-:::
+::: info DataProtector handles encryption automatically If you're using
+DataProtector, result encryption is handled automatically. This section is only
+needed for manual encryption when not using DataProtector. :::
 
-Secure your outputs with end‑to‑end encryption so only you (the beneficiary) can read them. Results leave the enclave and may traverse untrusted storage and networks; encryption ensures nobody else (operators, storage providers, intermediaries) can access the content.
+Secure your outputs with end‑to‑end encryption so only you (the beneficiary) can
+read them. Results leave the enclave and may traverse untrusted storage and
+networks; encryption ensures nobody else (operators, storage providers,
+intermediaries) can access the content.
 
 ### 1) Generate your encryption key pair
 
-The beneficiary key pair is the root of trust for result confidentiality. The public key will be used inside the TEE to encrypt results for the beneficiary; the private key stays with the beneficiary to decrypt them locally.
+The beneficiary key pair is the root of trust for result confidentiality. The
+public key will be used inside the TEE to encrypt results for the beneficiary;
+the private key stays with the beneficiary to decrypt them locally.
 
 Run from your iExec project directory:
 
@@ -228,11 +233,14 @@ This creates two files in `.secrets/beneficiary/`:
    └─ <0x-your-wallet-address>_key.pub   # PUBLIC KEY
 ```
 
-Back up the private key securely. You will only need it locally to decrypt results.
+Back up the private key securely. You will only need it locally to decrypt
+results.
 
 ### 2) Push your public key to the SMS
 
-The Secret Management Service securely delivers your public key, at runtime, to the enclave running your iApp. Without this, the iApp cannot encrypt outputs for you.
+The Secret Management Service securely delivers your public key, at runtime, to
+the enclave running your iApp. Without this, the iApp cannot encrypt outputs for
+you.
 
 Make the public key available to TEEs at runtime:
 
@@ -248,7 +256,9 @@ iexec result check-encryption-key --tee-framework scone
 
 ### 3) Run the iApp with encrypted results
 
-The --encrypt-result flag instructs the platform to perform envelope encryption inside the enclave using your public key, so the archive that leaves the TEE is unreadable to others.
+The --encrypt-result flag instructs the platform to perform envelope encryption
+inside the enclave using your public key, so the archive that leaves the TEE is
+unreadable to others.
 
 Trigger a task and request encrypted outputs:
 
@@ -268,9 +278,11 @@ iexec task show <0x-task-id> --download
 
 Inside the archive, `iexec_out/result.zip.aes` is encrypted.
 
-Note: Results are encrypted for the task beneficiary. Ensure the beneficiary address is yours to be able to decrypt the archive.
+Note: Results are encrypted for the task beneficiary. Ensure the beneficiary
+address is yours to be able to decrypt the archive.
 
-If you extract the archive and try to read the encrypted file, you'll see unreadable content:
+If you extract the archive and try to read the encrypted file, you'll see
+unreadable content:
 
 ```bash
 mkdir /tmp/trash && \
@@ -285,11 +297,13 @@ The output will look like:
 Յ]9WTL*tdzO`!e&snoL3K6L9%
 ```
 
-This confirms the results are properly encrypted and unreadable without the private key.
+This confirms the results are properly encrypted and unreadable without the
+private key.
 
 ### 4) Decrypt results locally
 
-Results are encrypted end‑to‑end; only your private key can decrypt them. This step restores the plaintext so you can use the output files.
+Results are encrypted end‑to‑end; only your private key can decrypt them. This
+step restores the plaintext so you can use the output files.
 
 Use your private key generated in step 1:
 
@@ -315,5 +329,7 @@ Your results are now decrypted and ready to use.
 ### Notes and tips
 
 - Keep the private key offline and backed up.
-- You can rotate keys by re-running generation and push steps; old tasks remain decryptable with the old private key.
-- iApp code does not need changes to enable result encryption; it is enforced by the TEE using the public key from SMS.
+- You can rotate keys by re-running generation and push steps; old tasks remain
+  decryptable with the old private key.
+- iApp code does not need changes to enable result encryption; it is enforced by
+  the TEE using the public key from SMS.