Update src/docs/product/session-replay/performance-overhead.mdx

Co-authored-by: Ryan Albrecht <ryan.albrecht@sentry.io>

src/docs/product/session-replay/performance-overhead.mdx

@@ -12,7 +12,7 @@ Session Replay works by observing and recording changes to your web application'
 
 Performance overhead depends on the complexity of your application. Applications with a large DOM and numerous DOM node mutations will have a higher overhead than a more simpler and mostly static site. The only way to get accurate overhead metrics is to measure it yourself. We have written a blog post, [Measuring Session Replay Overhead](https://sentry.engineering/blog/measuring-session-replay-overhead), that outlines how you can get started measuring overhead of Replay on your applications without deploying to production. We measured the overhead of the Replay SDK on Sentry's web UI using the methodology from the blog. Here are the results (median values are shown):
 
-| metric | Without Sentry | Sentry SDK only | Sentry + Replay SDK |
+| Metric | Without Sentry | Sentry SDK only | Sentry + Replay SDK |
 | -------------------------------- | -------------- | --------------- | ------------------- |
 | Largest Contentful Paint (LCP)\* | 1336.05 ms | 1896.80 ms | 1643.00 ms |
 | Cumulative Layout Shift (CLS) | 0.39 ms | 0.39ms | 0.39 ms |