chore(protocol-contracts): improve documentation

Author: melanciani

protocol-contracts/confidential-wrapper/docs/README.md

@@ -281,12 +281,19 @@ The unwrap mechanism stores requests in a mapping keyed by ciphertext and the cu
 
 The maximum number of decimals `_maxDecimals()` for the confidential token is currently set to **6 decimals** only. This is due to FHE limitations as confidential balances must be represented by the euint64 encrypted datatype. 
 
-It is possible that future implementations of the wrapper set a higher `_maxDecimals()` value to better suit the needs of the underlying token. For example, WBTC might require 8 decimals since using only 6 would make the smallest unit impractically expensive.
+It is possible that future implementations of the wrapper set a higher `_maxDecimals()` value to better suit the needs of the underlying token. For example, cWBTC might require 8 decimals since using only 6 would make the smallest unit impractically expensive.
 
 At deployment, the confidential wrapper sets its number of decimals as: 
 - the number of decimals of the underlying token if it is less than `_maxDecimals()`
 - `_maxDecimals()` otherwise
 
+**Example with `_maxDecimals()` set to 6**
+| Underlying Decimals | Wrapper Decimals | Example |
+|---------------------|------------------|---------|
+| 18  | 6 | ZAMA/cZAMA
+| 6 | 6 | USDT/cUSDT
+| 2 | 2 | GUSD/cGUSD
+
 Once a confidential wrapper contract is deployed, this number cannot be updated. It can be viewed with the following view function:
 
 ```solidity
@@ -295,7 +302,7 @@ wrapper.decimals();
 
 ### Maximum total supply
 
-The maximum total supply for the confidential token is currently set to 2^64 - 1 due to FHE limitations.
+The maximum total supply for the confidential token is currently set to `type(uint64).max` (`2^64 - 1`) due to FHE limitations.
 
 ---