diff --git a/pages/sdk/onchain-tracking.mdx b/pages/sdk/onchain-tracking.mdx
index 53073523..7ae2217d 100644
--- a/pages/sdk/onchain-tracking.mdx
+++ b/pages/sdk/onchain-tracking.mdx
@@ -118,6 +118,8 @@ The on-chain identifier allows tracking the deployment of Safe accounts, the exe
 
   If you use the [Protocol Kit](../sdk/protocol-kit.mdx) or the [Relay Kit](../sdk/relay-kit.mdx) to execute the Safe transactions, adding the `onchainAnalytics` property to the initialization method will automatically handle this. The Safe transactions will include the identifier.
 
+  {/* <!-- vale off --> */}
+
   <Tabs items={['Protocol Kit', 'Relay Kit']}>
     <Tabs.Tab>
       ```typescript
@@ -156,6 +158,8 @@ The on-chain identifier allows tracking the deployment of Safe accounts, the exe
     </Tabs.Tab>
   </Tabs>
 
+  {/* <!-- vale on --> */}
+
   ### Get the on-chain identifier
 
   To get the current safe on-chain identifier, you can use the `getOnchainIdentifier` method from an initialized instance of the Protocol Kit.
diff --git a/pages/sdk/protocol-kit/guides/execute-transactions.mdx b/pages/sdk/protocol-kit/guides/execute-transactions.mdx
index b5e34c50..5d3a9842 100644
--- a/pages/sdk/protocol-kit/guides/execute-transactions.mdx
+++ b/pages/sdk/protocol-kit/guides/execute-transactions.mdx
@@ -90,10 +90,10 @@ pnpm add @safe-global/api-kit \
 
   ### Create a transaction
 
-  {/* <!-- vale off --> */}
-
   Create a `safeTransactionData` object with the properties of the transaction, add it to an array of transactions you want to execute, and pass it to the `createTransaction` method.
 
+  {/* <!-- vale off --> */}
+
   ```typescript
   const safeTransactionData: MetaTransactionData = {
     to: '0x',
@@ -111,8 +111,6 @@ pnpm add @safe-global/api-kit \
 
   For more details on what to include in a transaction, see the [`createTransaction`](../reference/safe.mdx#createtransaction) method in the reference.
 
-  {/* <!-- vale on --> */}
-
   ### Propose the transaction
 
   Before a transaction can be executed, the signer who creates it needs to send it to the Safe Transaction Service so that it is accessible by the other owners, who can then give their approval and sign the transaction.
diff --git a/pages/sdk/protocol-kit/guides/multichain-safe-deployment.mdx b/pages/sdk/protocol-kit/guides/multichain-safe-deployment.mdx
index 2c65b292..af488de4 100644
--- a/pages/sdk/protocol-kit/guides/multichain-safe-deployment.mdx
+++ b/pages/sdk/protocol-kit/guides/multichain-safe-deployment.mdx
@@ -66,12 +66,12 @@ pnpm add @safe-global/protocol-kit viem
   const safeAccountConfig: SafeAccountConfig = {
     owners: ['0x...', '0x...', '0x...'],
     threshold: 2
-    // More optional properties
+    // ...
   }
 
   const predictedSafe: PredictedSafeProps = {
     safeAccountConfig
-    // More optional properties
+    // ...
   }
   ```
 
@@ -101,10 +101,10 @@ pnpm add @safe-global/protocol-kit viem
   })
   ```
 
-  Optionally, you can [track your Safe deployments and transactions on-chain](../../onchain-tracking.mdx) by using the `onchainAnalytics` property.
-
   {/* <!-- vale on --> */}
 
+  Optionally, you can [track your Safe deployments and transactions on-chain](../../onchain-tracking.mdx) by using the `onchainAnalytics` property.
+
   ### Predict the Safe addresses
 
   You can predict the Safe addresses by calling the [`getAddress`](../../../reference-sdk-protocol-kit/safe-info/getaddress.mdx) method from each Protocol Kit instance and ensure that the result addresses are the same.