diff --git a/docs/product/explore/profiling/transaction-vs-continuous-profiling.mdx b/docs/product/explore/profiling/transaction-vs-continuous-profiling.mdx
index ad39a1bafc2e8..d876f60d7a56c 100644
--- a/docs/product/explore/profiling/transaction-vs-continuous-profiling.mdx
+++ b/docs/product/explore/profiling/transaction-vs-continuous-profiling.mdx
@@ -7,7 +7,7 @@ description: "Learn about the differences between continuous and transaction-bas
 We've released a new profiling mode called **continuous profiling**. Read on to learn about the differences between transaction-based and continuous profiling mode. 
 
 
-## A bit of historical context first
+## Historical Context
 
 Transaction based profiling was the first profiling mode supported at Sentry, it  simply means that any code executed between Sentry.startTransaction and transaction.finish is subject to being profiled. In this mode, all profiles are attached to transactions (and are even sent as part of the same envelope). This has the benefit of automatically profiling parts of the application that are actually instrumented while requiring no extra effort. This approach however has drawback that continuous profiling aims to address, one of the most obvious ones being that profiles cannot exceed 30 second durations.