chore(browser): update freshnessDate, add anchor name

src/content/docs/browser/browser-monitoring/browser-pro-features/session-traces-explore-webpages-life-cycle.mdx

@@ -17,7 +17,7 @@ redirects:
   - /docs/browser/new-relic-browser/additional-standard-features/view-browser-trace-details
   - /docs/browser/new-relic-browser/browser-pro-features/session-traces-exploring-webpages-life-cycle
   - /docs/browser/new-relic-browser/browser-pro-features/session-traces-explore-webpages-life-cycle
-freshnessValidatedDate: never
+freshnessValidatedDate: 2024-05-06
 ---
 
 import browserSessionTraceDetails from 'images/browser_screenshot-full_session-trace-details.webp'
@@ -311,7 +311,7 @@ Session traces help you identify callbacks in your JavaScript code that execute
 
 Session traces highlight any callbacks longer than 33ms. If called in rapid succession (such as inside a `requestAnimationFrame` loop), callbacks longer than 33ms reduce the frame rate below 30 frames per second. This speed seems sluggish to users.
 
-## Plan for paid consumption
+## Plan for paid consumption [#plan-for-paid-consumption]
 
 Starting June 10, 2024, session trace data will contribute to your overall monthly data consumption. This means it will be charged per your existing order. This change reflects the storage upgrade to the New Relic database (NRDB) which enables [customizing your sampling rate](#configure-sampling-rates), extending data retention, and improved performance.
 
@@ -328,9 +328,11 @@ FROM NrConsumption SELECT rate(sum(consumption), 1 month) as monthly_SessionTrac
 />
 
 For a more granular view, this query can be used to view your daily consumption by child account, if applicable:
+
 ```sql
 FROM NrConsumption SELECT sum(consumption) as SessionTraceGBs WHERE usageMetric = 'UnbilledBrowserEventsBytes' FACET consumingAccountId, consumingAccountName SINCE '2024-04-25' TIMESERIES 1 day
 ```
+
 <img
   title="Daily session trace consumption query"
   alt="A screenshot of daily session trace consumption"