Skip to content

Commit 856d546

Browse files
Fix markdown issues
1 parent e41612b commit 856d546

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

contents/blog/how-to-find-and-fix-onboarding-drop-off.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -311,7 +311,7 @@ Want statistical proof it worked? [Run an A/B experiment](/product-engineers/how
311311

312312
While step isn't mandatory, [it helps avoid "we think this worked" decisions](/newsletter/what-we've-learned-about-ab-testing).
313313

314-
** If using PostHog...**
314+
**If using PostHog...**
315315

316316
Use [feature flags](/docs/feature-flags) to roll out your fix to a percentage of users first.
317317

@@ -362,7 +362,7 @@ If it didn't, that's okay. Go back to Step 4 with a new hypothesis. Onboarding o
362362
<details>
363363
<summary><strong>What is onboarding drop-off?</strong></summary>
364364

365-
**Onboarding drop-off **is when users start your onboarding flow but leave before completing it. They signed up and showed intent, but never reached the point where they experienced real value from your product (your activation event).
365+
**Onboarding drop-off** is when users start your onboarding flow but leave before completing it. They signed up and showed intent, but never reached the point where they experienced real value from your product (your activation event).
366366

367367
Onboarding drop-off is [not the same as churn](/tutorials/churn-rate) – these users never really started using your product in the first place.
368368
</details>

0 commit comments

Comments
 (0)