diff --git a/src/content/ccip/architecture.mdx b/src/content/ccip/architecture.mdx
index c4640b839ba..5e5fdd8094f 100644
--- a/src/content/ccip/architecture.mdx
+++ b/src/content/ccip/architecture.mdx
@@ -115,15 +115,17 @@ The mechanism for handling tokens varies depending on the characteristics of eac
   
 </Aside>
 
-<Aside type="note" title="Onboarding New Tokens">
-  Supported tokens for each lane are listed on the [CCIP supported network pages](/ccip/supported-networks). Expanding
-  support for additional tokens is an ongoing process to help ensure the highest level of cross-chain security. [Token
-  pool rate limits](/ccip/architecture/#token-pool-rate-limit) are configured per-token for each lane. These rate limits
-  are set together with token issuers where applicable. Rate limits are also selected based on various factors, such as
-  the unique risk characteristics of the token and the intended use cases. The onboarding process for adding new tokens
-  also helps ensure that dApps and users interact with the correct token version, reducing risks within the cross-chain
-  ecosystem.
-</Aside>
+<section id="onboarding-new-tokens">
+  <Aside type="note" title="Onboarding New Tokens">
+    Supported tokens for each lane are listed on the [CCIP supported network pages](/ccip/supported-networks). Expanding
+    support for additional tokens is an ongoing process to help ensure the highest level of cross-chain security. [Token
+    pool rate limits](/ccip/architecture/#token-pool-rate-limit) are configured per-token for each lane. These rate
+    limits are set together with token issuers where applicable. Rate limits are also selected based on various factors,
+    such as the unique risk characteristics of the token and the intended use cases. The onboarding process for adding
+    new tokens also helps ensure that dApps and users interact with the correct token version, reducing risks within the
+    cross-chain ecosystem.
+  </Aside>
+</section>
 
 #### Risk Management Network contract