📝 remove acknowledgement part from the documentation

docs/api/cipher.md

@@ -58,25 +58,7 @@ Resolves a DRSAP handshake packet and validates the sender's public key.
   - `packet`: The DRSAP handshake packet.
   - `from`: The sender's identifier.
 
-- **Returns:** A Promise that resolves to an acknowledgment packet or `undefined` if validation fails.
-
-#### `createDRSAPAcknowledgment(toId: string): string`
-
-Creates a DRSAP acknowledgment packet for acknowledging receipt of a DRSAP handshake.
-
-- **Parameters:**
-
-  - `toId`: The recipient's identifier.
-
-- **Returns:** The DRSAP acknowledgment packet.
-
-#### `resolveDRSAPAcknowledgment(packet: string, from: string): void`
-
-Resolves a DRSAP acknowledgment packet and updates the acknowledgment status in local storage.
-
-- **Parameters:**
-  - `packet`: The DRSAP acknowledgment packet.
-  - `from`: The sender's identifier.
+- **Returns:** A Promise that resolves to an boolean packet or `undefined` if validation fails.
 
 #### `static validatePublicPem(pem: string): boolean`
 

docs/encryption/process.md

@@ -27,16 +27,6 @@ The DRSAP handshake consists of the following components:
 5. **To User ID:** The user ID of the recipient.
 6. **Public Key PEM:** The public key of the sender in PEM format.
 
-### DRSAP Handshake Acknowledgment Content
-
-![ack](../public/images/Acknowledgement.png)
-
-After receiving a handshake, a client sends an acknowledgment packet containing:
-
-1. **Prefix:** `::ACK::` to identify the message as an acknowledgment.
-2. **Separator:** `__` for separating different parts of the acknowledgment.
-3. **To User ID:** The user ID of the sender.
-
 ## DRSAP Encrypted Message Content
 
 ![packet](../public/images/Packet.png)