fixes

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

@@ -29,14 +29,18 @@ Performance overhead depends on the complexity of your application. Applications
   value is higher than Sentry with Replay.
 </sub>
 
+<br />
+
 The benchmarks were run on an Apple M1 MacBook Pro against a remote preview server against a remote API backend with 100 iterations. The scenario can be summarized as loading Sentry, navigating to Discover, adding 4 columns, waiting for results, adding another column, and finally waiting for results a second time. The benchmark tests a rather strenuous recording scenario as the Discover data table is one of our most complex in regards to DOM nodes and mutations. A simpler scenario run consisting of navigation to four different "Settings" pages produced an increase of ~100 ms of total JS blocking time.
 
 <Note>
   There is a known performance issue when recording replays with many DOM
   mutations. This generally occurs when rendering large data grids. We are
   currently working on improving the performance of this situation, but in the
-  mean time it is recommended to [use the blocking
-  feature](https://docs.sentry.io/platforms/javascript/session-replay/privacy/#blocking)
+  mean time it is recommended to{" "}
+  <Link to="https://docs.sentry.io/platforms/javascript/session-replay/privacy/#blocking">
+    use the blocking feature
+  </Link>
   in order to not record these large mutations which can degrade performance for
   your customers.
 </Note>