fix(profiling): add beta note and decrease titles (#7567)

* fix(profiling): add beta note and decrease titles

* style(lint): Auto commit lint changes

---------

Co-authored-by: getsantry[bot] <66042841+getsantry[bot]@users.noreply.github.com>

src/platforms/javascript/common/profiling/index.mdx

@@ -6,6 +6,12 @@ supported:
 description: "Learn what transactions are captured after tracing is enabled."
 ---
 
+<Note>
+
+Browser Profiling is currently in beta. Beta features are still in-progress and may have bugs. We recognize the irony.
+
+</Note>
+
 Because our browser profiling integration is built on top of the profiler exposed by the [JS Self-Profiling API](https://wicg.github.io/js-self-profiling/), it's in beta and will likely only move out once the official spec progresses and gains adoption. As with any beta package, there are risks involved in using it - see platform [status](https://chromestatus.com/feature/5170190448852992)
 
 Please note, that since profiling API is currently only implemented in Chromium based browsers, the profiles collected will inherently be biased towards that demographic. This is something you'll need to consider if you're basing your decisions on the data collected. We hope that as the API gains adoption, other browsers will implement it as well. If you find browser profiling feature helpful and would like to see it gain further adoption, please consider supporting the spec at the official [WICG repository](https://github.com/WICG/js-self-profiling).

src/wizard/javascript/profiling-onboarding/javascript/1.install.md

@@ -5,7 +5,13 @@ support_level: beta
 type: framework
 ---
 
-## Install
+<Note>
+
+Browser Profiling is currently in beta. Beta features are still in-progress and may have bugs. We recognize the irony.
+
+</Note>
+
+#### Install
 
 Because our browser profiling integration is built on top of the profiler exposed by the [JS Self-Profiling API](https://wicg.github.io/js-self-profiling/), it's in beta and will likely only move out once the official spec progresses and gains adoption. As with any beta package, there are risks involved in using it - see platform [status](https://chromestatus.com/feature/5170190448852992)
 

src/wizard/javascript/profiling-onboarding/javascript/2.configure-document-policy.md

@@ -5,7 +5,7 @@ support_level: beta
 type: framework
 ---
 
-## Add Document-Policy: js-profiling header
+#### Add Document-Policy: js-profiling header
 
 In order for the profiler to start, the document response header has to include a `Document-Policy` header key with the `js-profiling` value.
 

src/wizard/javascript/profiling-onboarding/javascript/3.configure.md

@@ -5,7 +5,7 @@ support_level: beta
 type: framework
 ---
 
-## Configure
+#### Configure
 
 Configuration should happen as early as possible in your application's lifecycle. Once this is done, Sentry's JavaScript SDK will capture all unhandled exceptions and transactions.
 

src/wizard/javascript/profiling-onboarding/react/1.install.md

@@ -5,7 +5,13 @@ support_level: beta
 type: framework
 ---
 
-## Install
+<Note>
+
+Browser Profiling is currently in beta. Beta features are still in-progress and may have bugs. We recognize the irony.
+
+</Note>
+
+#### Install
 
 Because our browser profiling integration is built on top of the profiler exposed by the [JS Self-Profiling API](https://wicg.github.io/js-self-profiling/), it's in beta and will likely only move out once the official spec progresses and gains adoption. As with any beta package, there are risks involved in using it - see platform [status](https://chromestatus.com/feature/5170190448852992).
 

src/wizard/javascript/profiling-onboarding/react/2.configure-document-policy.md

@@ -5,7 +5,7 @@ support_level: beta
 type: framework
 ---
 
-## Add Document-Policy: js-profiling header
+#### Add Document-Policy: js-profiling header
 
 In order for the profiler to start, the document response header has to include a `Document-Policy` header key with the `js-profiling` value.
 

src/wizard/javascript/profiling-onboarding/react/3.configure.md

@@ -5,7 +5,7 @@ support_level: beta
 type: framework
 ---
 
-## Configure
+#### Configure
 
 Configuration should happen as early as possible in your application's lifecycle. Once this is done, Sentry's JavaScript SDK will capture all unhandled exceptions and transactions.