docs(stripe): Fix anchor link for integration options

[janpio]

This pull request makes a minor correction to the Stripe integration documentation. It updates the anchor links for "Option 2" and "Option 3" in the sales tracking section to use the correct URL encoding, ensuring that the links work as intended.

Summary by CodeRabbit

• Documentation
  • Updated Stripe integration documentation with improved content organization in the "Tracking sales" section.

[coderabbitai]

📝 Walkthrough

Walkthrough

Documentation content in the Stripe integration guide was reorganized by reordering bullet points under the "Tracking sales" section. Two options were repositioned without any textual or structural modifications.

Changes

Cohort / File(s)	Summary
Documentation Reorganization docs/integrations/stripe.mdx	Reordered bullet points under "Tracking sales" section by swapping the positions of Option 2 and Option 3.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A flutter of pages, a shuffle of text,
Options rearranged, what comes next?
Two and three did swap their places,
With carrot-approved thoughtful traces,
The guide flows better, hopping with ease! 🥕✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: fixing anchor links for integration options in the Stripe documentation, which aligns with the PR objectives of correcting anchor links in the sales tracking section.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

📝 Coding Plan

• Generate coding plan for human review comments

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Tip

You can disable the changed files summary in the walkthrough.

Disable the reviews.changed_files_summary setting to disable the changed files summary in the walkthrough.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/integrations/stripe.mdx`:
- Around line 122-123: Replace the URL-encoded anchor links
"#option-2%3A-using-stripe-checkout-recommended" with the standard slug
"#option-2-using-stripe-checkout-recommended" in the stripe.mdx content so all
references (the two remaining encoded occurrences) match the already-correct
anchor format; search for the exact encoded anchor string and update both
instances to the hyphenated slug.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: badd54b4-74a6-4b7d-8d7b-85cc7919d296

📥 Commits

Reviewing files that changed from the base of the PR and between 504361e and 92b686a.

📒 Files selected for processing (1)

• docs/integrations/stripe.mdx

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Anchor links look correct, but similar links elsewhere still use URL encoding.

The fix correctly uses the standard slug format (#option-2-using-stripe-checkout-recommended) that markdown processors typically generate from headings.

However, there are two other anchor links in this file that still use the URL-encoded %3A format:

• Line 206: #option-2%3A-using-stripe-checkout-recommended
• Line 359: #option-2%3A-using-stripe-checkout-recommended

These should be updated for consistency.

Suggested fixes for consistency

Line 206:

-If you're using Stripe's [Checkout Sessions API](https://docs.stripe.com/api/checkout/sessions/object) for a recurring subscription service, you might want to check out our [Stripe Checkout option](`#option-2`%3A-using-stripe-checkout-recommended) instead.
+If you're using Stripe's [Checkout Sessions API](https://docs.stripe.com/api/checkout/sessions/object) for a recurring subscription service, you might want to check out our [Stripe Checkout option](`#option-2-using-stripe-checkout-recommended`) instead.

Line 359:

-Alternatively, if you don't use Stripe's [checkout session creation flow](`#option-2`%3A-using-stripe-checkout-recommended), you can also pass the user ID and the click event ID (`dub_id`) in the [Stripe customer creation flow](https://docs.stripe.com/api/customers/create).
+Alternatively, if you don't use Stripe's [checkout session creation flow](`#option-2-using-stripe-checkout-recommended`), you can also pass the user ID and the click event ID (`dub_id`) in the [Stripe customer creation flow](https://docs.stripe.com/api/customers/create).

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/integrations/stripe.mdx` around lines 122 - 123, Replace the URL-encoded
anchor links "#option-2%3A-using-stripe-checkout-recommended" with the standard
slug "#option-2-using-stripe-checkout-recommended" in the stripe.mdx content so
all references (the two remaining encoded occurrences) match the already-correct
anchor format; search for the exact encoded anchor string and update both
instances to the hyphenated slug.