chore: apply PR suggestions

Author: zeljkoX

content/relayer/1.4.x/guides/zama-fhevm-counter-guide.mdx

@@ -157,7 +157,7 @@ npx ts-node examples/relayers/zama/counter.ts
 The script should:
 
 1. Read the encrypted counter handle from the contract.
-2. Attempt decryption (public first, then user decryption with an OpenZeppelin Relayer-signed EIP-712 payload).
+2. Attempt decryption (public first, then user decryption with an OpenZeppelin Relayer signed EIP-712 payload).
 3. Submit an encrypted `increment()` through the OpenZeppelin Relayer and poll until the transaction is mined or confirmed.
 4. Re-read and decrypt the updated counter value.
 
@@ -172,12 +172,12 @@ npx ts-node examples/relayers/zama/generate-keypair.ts
 Copy the printed `ZAMA_PUBLIC_KEY` and `ZAMA_PRIVATE_KEY` values into your `.env` file.
 
 <Callout>
-The decryption keypair is an application-side secret. Do not pass the private key to the OpenZeppelin Relayer; it is only used by the Zama Relayer SDK to decrypt results returned by the Zama Relayer.
+The decryption keypair is an application side secret. Do not pass the private key to the OpenZeppelin Relayer; it is only used by the Zama Relayer SDK to decrypt results returned by the Zama Relayer.
 </Callout>
 
 ## Walkthrough
 
-The following snippets show the OpenZeppelin Relayer-specific integration points from `counter.ts`. Full code is in the [SDK repository](https://github.com/OpenZeppelin/openzeppelin-relayer-sdk/tree/main/examples/relayers/zama).
+The following snippets show the OpenZeppelin Relayer's specific integration points from `counter.ts`. Full code is in the [SDK repository](https://github.com/OpenZeppelin/openzeppelin-relayer-sdk/tree/main/examples/relayers/zama).
 
 ### 1. Initialize the OpenZeppelin Relayer client and Zama SDK
 
@@ -291,7 +291,7 @@ const result = await instance.publicDecrypt([encryptedHandle]);
 const clear = result.clearValues[encryptedHandle as `0x${string}`];
 ```
 
-### 2. User Decryption (OpenZeppelin Relayer-signed EIP-712)
+### 2. User Decryption (OpenZeppelin Relayer's signed EIP-712)
 
 When decryption requires authorization, the Zama Relayer SDK builds an EIP-712 payload and the **OpenZeppelin Relayer** signs it via `signTypedData`. The resulting signature is passed to `userDecrypt`, which uses it to authorize the Zama Relayer to return the cleartext.
 

content/relayer/guides/zama-fhevm-counter-guide.mdx

@@ -157,7 +157,7 @@ npx ts-node examples/relayers/zama/counter.ts
 The script should:
 
 1. Read the encrypted counter handle from the contract.
-2. Attempt decryption (public first, then user decryption with an OpenZeppelin Relayer-signed EIP-712 payload).
+2. Attempt decryption (public first, then user decryption with an OpenZeppelin Relayer's signed EIP-712 payload).
 3. Submit an encrypted `increment()` through the OpenZeppelin Relayer and poll until the transaction is mined or confirmed.
 4. Re-read and decrypt the updated counter value.
 
@@ -172,12 +172,12 @@ npx ts-node examples/relayers/zama/generate-keypair.ts
 Copy the printed `ZAMA_PUBLIC_KEY` and `ZAMA_PRIVATE_KEY` values into your `.env` file.
 
 <Callout>
-The decryption keypair is an application-side secret. Do not pass the private key to the OpenZeppelin Relayer; it is only used by the Zama Relayer SDK to decrypt results returned by the Zama Relayer.
+The decryption keypair is an application side secret. Do not pass the private key to the OpenZeppelin Relayer; it is only used by the Zama Relayer SDK to decrypt results returned by the Zama Relayer.
 </Callout>
 
 ## Walkthrough
 
-The following snippets show the OpenZeppelin Relayer-specific integration points from `counter.ts`. Full code is in the [SDK repository](https://github.com/OpenZeppelin/openzeppelin-relayer-sdk/tree/main/examples/relayers/zama).
+The following snippets show the OpenZeppelin Relayer's specific integration points from `counter.ts`. Full code is in the [SDK repository](https://github.com/OpenZeppelin/openzeppelin-relayer-sdk/tree/main/examples/relayers/zama).
 
 ### 1. Initialize the OpenZeppelin Relayer client and Zama SDK
 
@@ -291,7 +291,7 @@ const result = await instance.publicDecrypt([encryptedHandle]);
 const clear = result.clearValues[encryptedHandle as `0x${string}`];
 ```
 
-### 2. User Decryption (OpenZeppelin Relayer-signed EIP-712)
+### 2. User Decryption (OpenZeppelin Relayer's signed EIP-712)
 
 When decryption requires authorization, the Zama Relayer SDK builds an EIP-712 payload and the **OpenZeppelin Relayer** signs it via `signTypedData`. The resulting signature is passed to `userDecrypt`, which uses it to authorize the Zama Relayer to return the cleartext.