fix(Rewrite): WIP

src/content/docs/browser/browser-monitoring/getting-started/introduction-browser-monitoring.mdx

@@ -27,23 +27,17 @@ Your end-user experience depends on your entire technology stack. You need to qu
 * Is it the result of a problematic internet provider, a problem in your own data center with failing CPU or memory, or something else?
 * How can you monitor and improve your [core web vital (CWV) scores](https://web.dev/vitals/) so you can prioritize where to focus the customer experience with your website?
 
-<Callout variant="tip">
-  This doc gives you detailed information about why our browser monitoring solution matters to your business. But if you want to skip ahead, just [sign up for a New Relic account](https://newrelic.com/signup). Then, after you [install the browser monitoring agent](/docs/browser/browser-monitoring/installation/install-browser-monitoring-agent), you can start [working with your data](/docs/data-apis/get-started/nrdb-horsepower-under-hood).
-</Callout>
-
-## More than Real User Monitoring (RUM) [#life-cycle-monitoring]
-
-Many websites contain dynamic content that is loaded after the initial page has finished loading, and complex JavaScript code increases the need for error reporting. Browser monitoring in New Relic provides a Real User Monitoring (RUM) solution that measures speed and performance as your end users navigate to your site from different web browsers, devices, operating systems, and networks.
+With browser monitoring in New Relic, you can see actionable data about your end users' experience with your app.
 
 <img
   title="Browser monitoring summary"
   alt="Screenshot of the New Relic browser monitoring Summary page"
   src={browserSummaryPage}
 />
 
-<figcaption>
-  With browser monitoring, you see actionable data about your end users' experience with your app.
-</figcaption>
+## More than Real User Monitoring (RUM) [#life-cycle-monitoring]
+
+Many websites contain dynamic content that is loaded after the initial page has finished loading, and complex JavaScript code increases the need for error reporting. Browser monitoring in New Relic provides a Real User Monitoring (RUM) solution that measures speed and performance as your end users navigate to your site from different web browsers, devices, operating systems, and networks.
 
 But browser monitoring in New Relic goes far beyond the initial page load to measure [full page life cycle data](/docs/browser/new-relic-browser/page-load-timing-resources/page-load-timing-process). For example, our browser UI shows you:
 
@@ -56,7 +50,7 @@ But browser monitoring in New Relic goes far beyond the initial page load to mea
 
 These tools (and more!) help your teams optimize your end users' page load experience, eliminate bugs, and troubleshoot faster across your full stack.
 
-## Use core web vitals data [core-web-vitals]
+## Core web vitals [core-web-vitals]
 
 The browser monitoring [**Summary** page](/docs/browser/browser-monitoring/getting-started/browser-summary-page/) includes important core web vitals, including largest contentful paint (LCP), first input delay (FID), and cumulative layout shift (CLS). You can also use the [`PageViewTiming` event](/attribute-dictionary/?event=PageViewTiming) for a more real-time delivery mechanism that does not have a dependency on any other event.
 
@@ -157,10 +151,11 @@ With our platform, you can instrument any type of data you need, such as [metric
 
 Follow these basic steps, and you'll quickly be up and running in New Relic with browser monitoring!
 
-1. Review the [compatibility details and basic requirements](/docs/browser/new-relic-browser/getting-started/compatibility-requirements-new-relic-browser) for browser monitoring.
+1. If you haven't already, [sign up for a New Relic account](https://newrelic.com/signup).
 2. [Install](/docs/browser/new-relic-browser/installation/install-new-relic-browser-agent) the browser agent.
-3. Go to **[one.newrelic.com](https://one.newrelic.com) > Explorer > Browser applications**. Use the [Explorer](/docs/new-relic-one/use-new-relic-one/core-concepts/new-relic-explorer-view-performance-across-apps-services-hosts/) to access all your [entities](/docs/new-relic-one/use-new-relic-one/core-concepts/what-entity-new-relic/), that is, anything we can identify that reports data, from applications and hosts to custom groupings of any elements.
-4. View summary data from your [**Browser summary** page](/docs/browser/new-relic-browser/getting-started/browser-overview-website-performance-glance), then drill down into page load timing details and other UI data.
-5. Configure your [alerts](/docs/alerts/new-relic-alerts/getting-started/new-relic-alerts-concepts-workflow) for key performance data, or use our [applied intelligence](/docs/new-relic-one/use-new-relic-one/new-relic-ai/introduction-new-relic-ai) solutions to reduce alert noise, correlate incidents, and automatically detect anomalies.
-6. [Query](/docs/using-new-relic/data/understand-data/query-new-relic-data) and visualize your [default data](/docs/insights/insights-data-sources/default-attributes/browser-default-attributes-insights) (or customize your own), then analyze what that data says about your business.
-7. Customize and share your own [charts and dashboards](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/).
+3. Go to **[one.newrelic.com](https://one.newrelic.com)** and select your browser app.
+4. View the core web vitals and other summary data from your [**Browser summary** page](/docs/browser/new-relic-browser/getting-started/browser-overview-website-performance-glance), then drill down into page load timing details and other UI data.
+
+<Callout variant="tip">
+  Not sure how to make the most of all the data you get? Review our [best practices guide](/docs/new-relic-solutions/best-practices-guides/full-stack-observability/browser-monitoring-best-practices-guide/) for browser monitoring.
+</Callout>