slight copy tweak, simple typo fixes to performance-monitoring.mdx (#13049)

* slight copy tweak, simple typo fixes to performance-monitoring.mdx

* make pageloads 2 words

Co-authored-by: Alex Krawiec <[email protected]>

* add period

Co-authored-by: Alex Krawiec <[email protected]>

---------

Co-authored-by: Alex Krawiec <[email protected]>

Author: pry0rity

docs/product/sentry-basics/performance-monitoring.mdx

@@ -22,7 +22,7 @@ Sentry has multiple tools for monitoring performance which are useful for differ
 
 After turning on Distributed Tracing, you'll automatically see a set of [Insights](/product/insights/) pages that give you a high-level view of performance data for each layer of your stack. This is extremely useful for quickly seeing any major performance outliers that need optimization, or tracking potential regressions across time, environments, releases, etc.
 
-- [**Frontend Insights**](/product/insights/frontend) givews you an easy but powerful way to\ drill into common frontend performance issues with things like Core Web Vitals, as well as transaction performance with things like duration, and error rate.
+- [**Frontend Insights**](/product/insights/frontend) gives you an easy but powerful way to drill into common frontend performance issues with things like Core Web Vitals, as well as transaction performance with things like duration, and error rate.
 - [**Backend Insights**](/product/insights/backend/) show your backend transaction performance, across things like database queries, external API calls, caches, queues, crons, and more.
 - [**Mobile Insights**](/product/insights/mobile/) track vital performance metrics for your mobile apps, including your cold & warm app start times, TTID & TTFD, and time to load or render key screens throughout your app. 
 - [**AI Insights**](/product/insights/ai/) give you a view of your LLM performance. This is currently in beta and only available for certain integrations.
@@ -39,7 +39,7 @@ Alongside typical [error issues](/product/issues/issue-details/error-issues/), S
 - N+1 Query & API call issues that indicate unnecessary round-trips to your backend
 - Consecutive DB Queries or HTTP Requests that could be batched for better performance
 - Database queries or File I/O running on the main thread, which can block the UI thread and cause performance issues
-- And many more documented [here](/product/issues/performance-issues/). 
+- And many more documented [here](/product/issues/performance-issues/)
 
 
 <Arcade src="https://demo.arcade.software/t8kZ9OeigLNrH3fLynIu?embed&embed_mobile=tab&embed_desktop=inline&show_copy_link=true" /> <br />
@@ -71,7 +71,9 @@ For basic frontend or backend performance monitoring, just turn on Tracing in yo
 
 ## How Performance Monitoring works under the hood
 
-Instead of instrumenting pageloads with specific metrics at set points, ie. `onLoad`, `onUnload`, `onError`, etc., Sentry automatically traces every network request, file I/O, and other operation in your application. This lets you see the performance impact of every request, and any errors that occur during that request. 
+Instead of instrumenting page loads with specific metrics at certain set intervals, like `onLoad`, `onUnload`, `onError`, etc., Sentry makes an effort to automatically instrument the libraries you rely on, providing detailed telemetry for Web Vitals, file I/O, network requests, and more. This lets you see the performance impact of every request, and any errors that occur during that request. 
+
+This differs substantially from other performance monitoring tools that only capture *predefined* metrics with much less granularity. All your holistic metrics in Sentry are backed up by the raw tracing data, so you can drill into any specific request or operation to get a detailed view of its performance.
 
 These performance metrics are sent by the Sentry SDK as part of each [Span](/concepts/key-terms/tracing/#whats-a-span), which is the smallest unit of work in a [Trace](/concepts/key-terms/tracing/). Traces are assembled in Sentry's backend, and then extrapolated to populate all the tools we have for monitoring performance.