feat(billing): Update documentation surrounding on-demand budgets

[dashed]

This pull request updates the current on-demand budget documentation in anticipation of the rollout of the new on-demand budgets feature to all performance plans on the week of April 4, 2022. This pull request should not be merged until this roll out completes.

Changelog:

• I've renamed "On-Demand Spending Cap" to "On-Demand Budget"
• Added blurbs on shared and per-category on-demand budget strategies.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/sentry/sentry-docs/DasEvrLtKHiJdShtFEW2PjZrwExx
✅ Preview: https://sentry-docs-git-alberto-ondemand-budgets.sentry.dev

[imatwawana]

I've made some wording and style edits that should improve clarity, but overall, it's solid.

[imatwawana]

A couple more wording fixes.

[dashed]

@imatwawana Let me know if I missed any suggested feedback you had. Can you check the latest changes again?

[imatwawana]

Looks good!

[dashed]

@imatwawana There are changes to how the new on-demand budget feature will be rolled out. We aim to roll this out to customers on the performance plan, and are also on the early adopters program.

In addition, if they are using the per-category on-demand budget strategy, they'll retain this configuration regardless if they are on the Early Adopters program or not.

I updated this note to reflect that. I'm unsure if the language here is sufficient.

[imatwawana]

When you say they'll retain the configuration, do we mean that they just retain the per-category budget they've already set up? Or could they make changes to their per-category budget?

And if they switch to shared, I assume we mean that they can't go back to per-category?

[dashed]

@imatwawana

When you say they'll retain the configuration, do we mean that they just retain the per-category budget they've already set up? Or could they make changes to their per-category budget?

They'll be able to do both.

So if they:

1. enabled early adopters feature in the past,
2. switched to per-category on-demand budget strategy, and
3. opted out of early adopters afterwards,

they remain on the per-category on-demand budget.

Customers on the performance plans may only be able to opt into per-category on-demand budget only if they're opted into the Early Adopter program.

And if they switch to shared, I assume we mean that they can't go back to per-category?

They'll be unable to switch back to per-category as long as they're opted out of Early Adopters.