refactor(docs): update DataProtector and iApp types documentation for clarity and consistency

Author: Le-Caignec

src/references/dataProtector/types.md

@@ -22,8 +22,11 @@ Types in DataProtector.
 
 ### volume: <span class="text-yellow">`string`</span>
 
-- Number of authorized uses of this `protectedData`; each use decrements this
-  counter
+- Total number of authorized accesses for processing a Protected Data when the access was signed and published
+
+### remainingAccess: <span class="text-yellow">`number`</span>
+
+- Number of remaining authorized accesses for processing a protected data; each use decrements this counter
 
 ### tag: <span class="text-yellow">`string`</span>
 
@@ -120,6 +123,3 @@ You can read more about the
 <!-- prettier-ignore-start -->
 _Hash example:_ `0xc9c2d58fc01fe54149b7daf49a0026d4ab1fdd3d10fb7c76350790fff03fe24d`
 <!-- prettier-ignore-end -->
-
-You can read more about the [iExec Explorer]
-(/get-started/tooling-and-explorers/iexec-explorer).

src/references/iapp-generator/sdk/types.md

@@ -1,7 +1,7 @@
 ---
 title: Types
 description:
-  Complete reference for DataProtector types including GrantedAccess,
+  Complete reference for iApp types including GrantedAccess,
   ProtectedData, Collection, and other essential data structures.
 ---
 
@@ -11,33 +11,36 @@ Types in DataProtector.
 
 ## 🔑 GrantedAccess
 
-### dataset: <span class="text-yellow">`string`</span>
+### app: <span class="text-yellow">`string`</span>
 
-- Address of the `protectedData` containing user data
+- Address of the iExec Tee application (IApp)
 
-### datasetprice: <span class="text-yellow">`string`</span>
+### appprice: <span class="text-yellow">`string`</span>
 
 - Price (in nRLC) to charge the user specified in `requesterrestrict` for each
-  use of this `protectedData`
+  use of this `iapp`
 
 ### volume: <span class="text-yellow">`string`</span>
 
-- Number of authorized uses of this `protectedData`; each use decrements this
-  counter
+- Total number of authorized accesses for running an iApp when the access was signed and published
+
+### remainingAccess: <span class="text-yellow">`number`</span>
+
+- Number of remaining authorized accesses for running an iApp; each use decrements this counter
 
 ### tag: <span class="text-yellow">`string`</span>
 
 - Defines whether a `protectedData` is usable in a TEE environment; `0x00` is
   TEE while `0x03` is non-TEE
 
-### apprestrict: <span class="text-yellow">`string`</span>
+### datasetrestrict: <span class="text-yellow">`string`</span>
 
-- Address of the authorized application; a value of 0x0 indicates any
-  application may access this data
+- Address of the authorized protected data; a value of 0x0 indicates any
+  protected data may run with this iapp
 
 ### requesterrestrict: <span class="text-yellow">`string`</span>
 
-- Address of the requester authorized to use this `protectedData` in workloads;
+- Address of the requester authorized to run this `iapp` in workloads;
   a value of 0x0 indicates any requester may use this data
 
 ### workerpoolrestrict: <span class="text-yellow">`string`</span>
@@ -55,31 +58,31 @@ Types in DataProtector.
 
 - Order signature of all the `grantedAccess` fields
 
-## 🔐 ProtectedData
+## 🔐 IApp
 
 ### name: <span class="text-yellow">`string`</span>
 
-- Name specified when the protected data was created. This piece of information
+- Name specified when the iApp was created. This piece of information
   is public and visible on-chain.
 
 ### address: <span class="text-yellow">`Address`</span>
 
-- Ethereum address of the protected data.
+- Ethereum address of the iapp.
 
 ### owner: <span class="text-yellow">`Address`</span>
 
-- Ethereum address of the protected data owner.
+- Ethereum address of the iapp owner.
 
 ### creationTimestamp: <span class="text-yellow">`number`</span>
 
-- Timestamp specifying when the protected data was created, expressed in
+- Timestamp specifying when the iapp was created, expressed in
   milliseconds since the epoch. This timestamp provides precise information
   about the moment of creation and can be used for chronological ordering or
   time-based operations.
 
 ### multiaddr: <span class="text-yellow">`string` | `undefined`</span>
 
-- The multiaddr field is the IPFS path of your encrypted data.
+- The multiaddr field is the IPFS path of iapp published on Dockerhub.
 
 ## ❌ RevokedAccess
 
@@ -111,6 +114,3 @@ You can read more about the
 <!-- prettier-ignore-start -->
 _Hash example:_ `0xc9c2d58fc01fe54149b7daf49a0026d4ab1fdd3d10fb7c76350790fff03fe24d`
 <!-- prettier-ignore-end -->
-
-You can read more about the [iExec Explorer]
-(/get-started/tooling-and-explorers/iexec-explorer).