Update docs/product/explore/profiling/transaction-vs-continuous-profiling.mdx

Co-authored-by: Liza Mock <[email protected]>

Author: JonasBa

docs/product/explore/profiling/transaction-vs-continuous-profiling.mdx

@@ -82,6 +82,6 @@ The main difference between transaction-based and continuous profiling is when t
 
 Continuous profiling can give you visibility into parts of your application that you haven't instrumented. This is especially useful if your instrumentation is incomplete. However, it may also capture idle time, resulting in data that's potentially less valuable.
 
-On the flip side, if you want to profile a high throughput server with little or no idle time, continuous profiling mode will help you reduce costs, as the profiler will not upload duplicated profiling data from overlapping transactions.
+If you want to profile a high-throughput server with little or no idle time, continuous profiling can help reduce costs, as the profiler will not upload duplicated profiling data from overlapping transactions.
 
-It is important that you understand the trade-offs between the two modes and choose the one that best fits your use case. If you're unsure, we recommend starting with continuous profiling mode, as it will give you a more complete picture of your application's performance.
+It's important that you understand the tradeoffs between the two modes and choose the one that best fits your use case. If you're unsure, we recommend starting with continuous profiling because you'll get a more complete picture of your application's performance.