refactor: streamline DataProtector types documentation with enhanced clarity and structure

Author: akugone

src/manage-data/dataProtector/types.md

@@ -2,129 +2,97 @@
 
 Types in DataProtector.
 
-## GrantedAccess
+## 🔑 GrantedAccess
 
-### dataset
+### dataset: <span class="text-yellow">`string`</span>
 
-`string`
+- Address of the `protectedData` containing user data
 
-Address of the `protectedData` containing user data
+### datasetprice: <span class="text-yellow">`string`</span>
 
-### datasetprice
+- Price (iun nRLC) to charge the user specified in `requesterrestrict` for each
+  use of this `protectedData`
 
-`string`
+### volume: <span class="text-yellow">`string`</span>
 
-Price (iun nRLC) to charge the user specified in `requesterrestrict` for each
-use of this `protectedData`
+- Number of authorized uses of this `protectedData`; each use decrements this
+  counter
 
-### volume
+### tag: <span class="text-yellow">`string`</span>
 
-`string`
+- Defines whether a `protectedData` is usable in a TEE environment; `0x00` is
+  TEE while `0x03` is non-TEE
 
-Number of authorized uses of this `protectedData`; each use decrements this
-counter
+### apprestrict: <span class="text-yellow">`string`</span>
 
-### tag
+- Address of the authorized application; a value of 0x0 indicates any
+  application may access this data
 
-`string`
+### requesterrestrict: <span class="text-yellow">`string`</span>
 
-Defines whether a `protectedData` is usable in a TEE environment; `0x00` is TEE
-while `0x03` is non-TEE
+- Address of the requester authorized to use this `protectedData` in workloads;
+  a value of 0x0 indicates any requester may use this data
 
-### apprestrict
+### workerpoolrestrict: <span class="text-yellow">`string`</span>
 
-`string`
+- Address of the decentralized infrastructure (worker pool) authorized to
+  execute the application; a value of 0x0 indicates any worker pool may access
+  this data
 
-Address of the authorized application; a value of 0x0 indicates any application
-may access this data
+### salt: <span class="text-yellow">`string`</span>
 
-### requesterrestrict
+- Random value to make an order unique and reusable as nonce in a blockchain
+  transaction
 
-`string`
+### sign: <span class="text-yellow">`string`</span>
 
-Address of the requester authorized to use this `protectedData` in workloads; a
-value of 0x0 indicates any requester may use this data
+- Order signature of all the `grantedAccess` fields
 
-### workerpoolrestrict
+## 🔐 ProtectedData
 
-`string`
+### name: <span class="text-yellow">`string`</span>
 
-Address of the decentralized infrastructure (worker pool) authorized to execute
-the application; a value of 0x0 indicates any worker pool may access this data
+- Name specified when the protected data was created. This piece of information
+  is public and visible on-chain.
 
-### salt
+### address: <span class="text-yellow">`Address`</span>
 
-`string`
+- Ethereum address of the protected data.
 
-Random value to make an order unique and reusable as nonce in a blockchain
-transaction
+### owner: <span class="text-yellow">`Address`</span>
 
-### sign
+- Ethereum address of the protected data owner.
 
-`string`
+### schema: <span class="text-yellow">`DataSchema`</span>
 
-Order signature of all the `grantedAccess` fields
+- Data schema for the protected data as defined when the protected data was
+  created (see [protectedData](./dataProtectorCore/protectData.md)). `schema`
+  provides a structured representation of the protected data format and
+  attributes. This field plays a crucial role in understanding and interpreting
+  the underlying structure of the sensitive information.
 
-## ProtectedData
+### creationTimestamp: <span class="text-yellow">`number`</span>
 
-### name
+- Timestamp specifying when the protected data 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.
 
-`string`
+### multiaddr: <span class="text-yellow">`string` | `undefined`</span>
 
-Name specified when the protected data was created. This piece of information is
-public and visible on-chain.
+- The multiaddr field is the IPFS path of your encrypted data.
 
-### address
+## ❌ RevokedAccess
 
-`Address`
+### access: <span class="text-yellow">[`GrantedAccess`](./types.md#grantedaccess)</span>
 
-Ethereum address of the protected data.
+- The granted access that was revoked.
 
-### owner
+### txHash: <span class="text-yellow">`string`</span>
 
-`Address`
-
-Ethereum address of the protected data owner.
-
-### schema
-
-`DataSchema`
-
-Data schema for the protected data as defined when the protected data was
-created (see [protectedData](./dataProtectorCore/protectData.md)). `schema`
-provides a structured representation of the protected data format and
-attributes. This field plays a crucial role in understanding and interpreting
-the underlying structure of the sensitive information.
-
-### creationTimestamp
-
-`number`
-
-Timestamp specifying when the protected data 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
-
-`string` | `undefined`
-
-The multiaddr field is the IPFS path of your encrypted data.
-
-## RevokedAccess
-
-### access
-
-[`GrantedAccess`](./types.md#grantedaccess)
-
-The granted access that was revoked.
-
-### txHash
-
-`string`
-
-The ID of the transaction that happened on iExec's side chain. You may view
-details on the transaction using the [iExec explorer](https://explorer.iex.ec).
+- The ID of the transaction that happened on iExec's side chain. You may view
+  details on the transaction using the
+  [iExec explorer](https://explorer.iex.ec).
 
 <!-- prettier-ignore-start -->
 _Hash example:_ `0xc9c2d58fc01fe54149b7daf49a0026d4ab1fdd3d10fb7c76350790fff03fe24d`
@@ -133,14 +101,13 @@ _Hash example:_ `0xc9c2d58fc01fe54149b7daf49a0026d4ab1fdd3d10fb7c76350790fff03fe
 You can read more about he iExec Explorer
 [here](https://protocol.docs.iex.ec/for-developers/toolbox/iexec-explorer).
 
-## SuccessWithTransactionHash
-
-### txHash
+## ✅ SuccessWithTransactionHash
 
-`string`
+### txHash: <span class="text-yellow">`string`</span>
 
-The hash of the transaction that happened on iExec's side chain. You may view
-details on the transaction using the [iExec explorer](https://explorer.iex.ec).
+- The hash of the transaction that happened on iExec's side chain. You may view
+  details on the transaction using the
+  [iExec explorer](https://explorer.iex.ec).
 
 <!-- prettier-ignore-start -->
 _Hash example:_ `0xc9c2d58fc01fe54149b7daf49a0026d4ab1fdd3d10fb7c76350790fff03fe24d`