code updates

Author: gfletcher-cll

src/content/ccip/concepts/rate-limit-management/emergency-actions.mdx

@@ -33,8 +33,10 @@ This configuration allows only a negligible transfer before the bucket is deplet
 
 Conceptually, a lane can be locked down by calling `setChainRateLimiterConfig` with the following values:
 
-- outboundConfig: `[true, "1", "1"]`
-- inboundConfig: `[true, "1", "1"]`
+```solidity
+outboundConfig = [true, 1, 1];
+inboundConfig  = [true, 1, 1];
+```
 
 Both inbound and outbound limits should be set to ensure transfers are blocked in both directions.
 

src/content/ccip/concepts/rate-limit-management/inspect-current-rate-limits.mdx

@@ -34,8 +34,16 @@ Chain selectors are represented as `uint64` values. You can find the correct sel
 
 Most token pool contracts expose public getter functions similar to:
 
-- `getCurrentInboundRateLimiterState`
-- `getCurrentOutboundRateLimiterState`
+```solidity
+function getCurrentInboundRateLimiterState(
+  uint64 remoteChainSelector
+) external view returns (TokenBucket memory);
+
+function getCurrentOutboundRateLimiterState(
+  uint64 remoteChainSelector
+) external view returns (TokenBucket memory);
+
+```
 
 These functions take a remote chain selector as input and return the current **TokenBucket** state for that lane.
 
@@ -48,13 +56,24 @@ You can call these functions using:
 
 A typical rate limiter state includes the following fields:
 
-- **tokens**: the current number of tokens available in the bucket
-- **lastUpdated**: the timestamp of the last refill
-- **isEnabled**: whether the rate limit is active
-- **capacity**: the maximum bucket size
-- **rate**: the refill rate in tokens per second
-
-All numeric values are expressed in the token’s **smallest unit**, not in whole tokens.
+```solidity
+struct TokenBucket {
+  uint128 tokens;
+  uint32 lastUpdated;
+  bool isEnabled;
+  uint128 capacity;
+  uint128 rate;
+}
+```
+
+Where:
+
+- tokens (uint128): the current number of tokens available in the bucket
+- lastUpdated (uint32): the timestamp of the last refill
+- isEnabled (bool): whether the rate limit is active
+- capacity (uint128): the maximum bucket size
+- rate (uint128): the refill rate in tokens per second
+- All numeric values are expressed in the token’s **smallest unit**, not in whole tokens.
 
 ## Inbound vs outbound inspection
 

src/content/ccip/concepts/rate-limit-management/update-rate-limits.mdx

@@ -18,17 +18,24 @@ This function updates both the inbound and outbound rate limit configuration for
 
 The `setChainRateLimiterConfig` function takes three parameters:
 
-1. **remoteChainSelector (uint64)**
-   Identifies the remote chain for the lane being configured.
-
-2. **outboundConfig (tuple)**
-   Configuration for transfers leaving the current chain.
-
-3. **inboundConfig (tuple)**
-   Configuration for transfers entering the current chain.
+```solidity
+function setChainRateLimiterConfig(
+  uint64 remoteChainSelector,
+  RateLimiter.Config outboundConfig,
+  RateLimiter.Config inboundConfig
+) external;
+```
 
 Each configuration tuple contains:
 
+```solidity
+struct Config {
+  bool isEnabled;
+  uint128 capacity;
+  uint128 rate;
+}
+```
+
 - **isEnabled**: whether the rate limit is active
 - **capacity**: maximum bucket size (in base units)
 - **rate**: refill rate in tokens per second (in base units)