diff --git a/docs/governance/overview.mdx b/docs/governance/overview.mdx
index 8556420a..34063165 100644
--- a/docs/governance/overview.mdx
+++ b/docs/governance/overview.mdx
@@ -4,18 +4,18 @@ title: Governance overview
 
 import InlineCopy from '@site/src/components/InlineCopy';
 
-The Etherlink<!--TX--> governance process manages updates to Etherlink<!--TX-->'s kernel and the account that operates the sequencer.
+The Etherlink{/* TX */} governance process manages updates to Etherlink{/* TX */}'s kernel and the account that operates the sequencer.
 
-Tezos bakers can participate in the [Etherlink<!--TX--> governance process](/governance/how-is-etherlink-governed) by submitting proposals to change the kernel and sequencer operator and voting for or against them.
+Tezos bakers can participate in the [Etherlink{/* TX */} governance process](/governance/how-is-etherlink-governed) by submitting proposals to change the kernel and sequencer operator and voting for or against them.
 The voting power of a baker is the amount of tez that it has staked plus the tez that delegators have delegated to it, also called its _staking balance_.
 
 Separate contracts manage the slow kernel updates, the fast kernel updates, and the sequencer operator, so to interact with them, bakers send transactions to those contracts, such as with the Octez client.
-The addresses of the governance contracts are specified in Etherlink<!--TX-->'s kernel.
+The addresses of the governance contracts are specified in Etherlink{/* TX */}'s kernel.
 For information about the Octez client, see [Command Line Interface](https://octez.tezos.com/docs/active/cli-commands.html) in the Octez documentation.
 
 ## Governance web site
 
-For information about Etherlink<!--TX--> governance and to vote on governance proposals, see https://governance.etherlink.com.
+For information about Etherlink{/* TX */} governance and to vote on governance proposals, see https://governance.etherlink.com.
 This site:
 
 - Shows information about each governance process
@@ -25,7 +25,7 @@ This site:
 
 ## Governance contract addresses
 
-You need the address of the correct governance contract (and sometimes the address of the Etherlink<!--TX--> Smart Rollup) to propose changes, vote on changes, and trigger approved changes.
+You need the address of the correct governance contract (and sometimes the address of the Etherlink{/* TX */} Smart Rollup) to propose changes, vote on changes, and trigger approved changes.
 
 <table class="customTableContainer">
 <thead>
@@ -52,7 +52,7 @@ You need the address of the correct governance contract (and sometimes the addre
 <td><InlineCopy code="KT1Ut6kfrTV9tK967tDYgQPMvy9t578iN7iH" href="https://better-call.dev/mainnet/KT1Ut6kfrTV9tK967tDYgQPMvy9t578iN7iH" abbreviate="6,4"></InlineCopy></td>
 </tr>
 <tr>
-<td>Etherlink<!--TX--> Smart Rollup</td>
+<td>Etherlink{/* TX */} Smart Rollup</td>
 <td><InlineCopy code="sr1Ghq66tYK9y3r8CC1Tf8i8m5nxh8nTvZEf" href="https://tzkt.io/sr1Ghq66tYK9y3r8CC1Tf8i8m5nxh8nTvZEf" abbreviate="6,4"></InlineCopy></td>
 </tr>
 </tbody>
diff --git a/docs/michelson/nac-usage.md b/docs/michelson/nac-usage.md
index 0696e841..3409aaa2 100644
--- a/docs/michelson/nac-usage.md
+++ b/docs/michelson/nac-usage.md
@@ -201,7 +201,7 @@ IF_NONE
 
 ## Return value
 
-### `%call_evm` — callback
+### `%call_evm`
 
 `%call_evm` is a state-mutating call with no direct return. To receive the EVM return value, supply a `contract bytes` handle in the `callback` field. After the EVM call succeeds, the kernel emits a `TRANSFER_TOKENS` internal operation that sends the raw ABI-encoded return bytes to the callback contract at zero mutez.
 
@@ -296,7 +296,7 @@ def test():
     )
 ```
 
-### `staticcall_evm` — synchronous
+### `staticcall_evm`
 
 `staticcall_evm` is a read-only view. The return value is delivered synchronously as `option bytes` via the Michelson `VIEW` instruction — no callback contract is needed.