diff --git a/src/pages/guide/node/rpc.mdx b/src/pages/guide/node/rpc.mdx
index 23c628f2..741b4f73 100644
--- a/src/pages/guide/node/rpc.mdx
+++ b/src/pages/guide/node/rpc.mdx
@@ -21,10 +21,6 @@ tempo node \
   --http.api eth,net,web3,txpool,trace
 ```
 
-<Callout type="info">
-For mainnet, you have to use the credentials in `--follow` that are issued to you by the Tempo team.
-</Callout>
-
 An RPC node running in follow mode is a **full node**. It fetches blocks from a trusted RPC endpoint, executes every transaction locally through the EVM, validates each block after execution, and stores complete block data with full state. The only trust assumption is block ordering: your node trusts the RPC endpoint to provide the correct sequence of blocks. All execution and validation happens locally on your machine.
 
 By default, RPC nodes run in archive mode, meaning they do not prune historical state.
diff --git a/vocs.config.ts b/vocs.config.ts
index d6e574f2..94840ad5 100644
--- a/vocs.config.ts
+++ b/vocs.config.ts
@@ -15,8 +15,7 @@ export default defineConfig({
   banner: {
     dismissable: false,
     backgroundColor: '#5B4CDB',
-    content:
-      'Tempo Mainnet is live. [Read our announcement.](https://tempo.xyz/blog/mainnet) →',
+    content: 'Tempo Mainnet is live. [Read our announcement.](https://tempo.xyz/blog/mainnet) →',
     height: '40px',
     textColor: 'white',
   },