Update docs/product/explore/profiling/transaction-vs-continuous-profi…

…ling.mdx

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

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

@@ -21,11 +21,11 @@ The cap on max profile duration isn't the only drawback of transaction-based pro
 
 To address these limitations, we created a different profiling mode, one that doesn't impose constraints on profile durations and can surface parts of your application that might be slowing down your application even if you haven't instrumented them.
 
-## Continuous profiling mode
+## Continuous Profiling Mode
 
-In countinuous profiling mode, the profiler runs continuously (no pun intended) and regularly flushes what we call profile "profile chunks" to the server, this enables us to extend profile durations and continuously profile your application.
+In continuous profiling mode, the profiler runs continuously (no pun intended) and regularly flushes what we call "profile chunks" to the server. This enables us to extend profile durations and continuously profile your application.
 
-Continuous profiling mode is suitable for profiling long running workflows or processes that you want full visibility into, while the transaction based profiling is largely suitable for workflows where you want to limit profiling to only a subset of your application.
+Continuous profiling mode is capable of profiling long-running workflows or processes that you want full visibility into, while transaction-based profiling is intended for workflows where you want to limit profiling to only a subset of your application.
 
 
 ## SDK differences