fix(pricing): formatting changes

src/content/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing.mdx

@@ -47,17 +47,40 @@ Related docs:
 * For more on how data is ingested, see [Manage data ingest](/docs/data-apis/manage-data/manage-data-coming-new-relic).
 * For how to query usage, see [Query and alert on usage](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts).
 
+## Core users pricing version [#core-users-pricing]
 
-## User billing calculations and user downgrade limits  [#user-count]
-
-The main way to understand your billable user count is to go to the [usage UI](/docs/accounts/accounts-billing/general-account-settings/introduction-account-settings/#pricing). If you need more detail than the UI provides, you can also run usage-related queries. 
-
-How your billable users are calculated, and the rules governing upgrading/downgrading users, depends on which of two versions of New Relic One pricing you’re on: 
+There are two versions of New Relic One pricing: 
 
 * New Relic One pricing, **with** core users
 * New Relic One pricing, **without** core users
 
-If you have the ability to add core users, your organization is on the "New Relic One with core users" version. Click your version below for billing details. 
+On December 15, 2021, we released a version of New Relic One pricing that added a new user type ([core user](/docs/accounts/accounts-billing/new-relic-one-user-management/user-type)) and changed [how billable users are counted](#nr1-pricing-with-core). This is currently the default pricing version for new New Relic sign-ups. 
+
+If your organization has the ability to add core users, you're on this version. Some customers on older versions are able to [opt in to get core users](?).
+
+### Details about opting in to core users [#nr1core-optin]
+
+Some New Relic organizations that existed prior to December 15, 2021 have a self-serve option in the UI for opting in to the core users version of pricing. The UI acceptance form is called the “core user addendum." By accepting this addendum, the New Relic user is stating that they're authorized to accept those terms for their organization. 
+
+The core user addendum is available to organizations that: 
+* ... ? 
+* ... ? 
+
+When your organization opts in, your organization has a seven-day grace period, during which your users’ user type won’t affect your bill. This gives you time to [decide which user type to assign your users](?). After your grace period ends, the normal billing calculations apply. 
+
+If your organization has opted in to add core users, the [two-times-per-year limit on downgrading full platform users](#nr1core-downgrade-rules) will apply from when you opted in until the renewal of your subscription term or, if applicable, the annual anniversary date of your commitment term, whichever is earlier. 
+
+### Change to "full user" name [#full-user-language]
+
+On December 16, 2021, the “full user” user type was renamed to “full platform user." For organizations that were on the New Relic One pricing plan before that date and have not opted in to the [core users version](#nr1-pricing-with-core), “full platform users” are equivalent to “full users” or “monthly provisioned users” in their New Relic agreement. 
+
+One exception to this: For organizations on the [New Relic One without core users version of pricing](#nr1-pricing-without-core), the "full user" term is still used as an attribute when [querying full user counts](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts). 
+
+## User billing calculations  [#user-count]
+
+The main way to understand your billable user count is to go to the [usage UI](/docs/accounts/accounts-billing/general-account-settings/introduction-account-settings/#pricing). If you need more detail than the UI provides, you can also run usage-related queries. 
+
+How your billable users are calculated depends on which of [two versions of New Relic One pricing](#core-users-pricing) you’re on: 
 
 <CollapserGroup>
 
@@ -66,49 +89,26 @@ If you have the ability to add core users, your organization is on the "New Reli
     title="New Relic One with core users"
   >
  <Callout variant="important">
-On December 17, 2021, we released a version of New Relic One pricing that added a new user type ([core user](/docs/accounts/accounts-billing/new-relic-one-user-management/user-type)) and changed how billable users are counted. This is currently the default pricing version for new New Relic sign-ups. If you have the ability to add core users, you're on this version. Some customers on other pricing versions are able to [opt in to get core users](?).
+On December 17, 2021, we released a version of New Relic One pricing that added a new user type ([core user](/docs/accounts/accounts-billing/new-relic-one-user-management/user-type)) and changed how billable users are counted. [Learn more about the core users release.](#core-users-pricing)
 </Callout>
 
-### User calculations [#nr1core-user-calculation]
-
 The [usage UI](/docs/accounts/accounts-billing/general-account-settings/introduction-account-settings/#pricing) displays a count of billable users and is the best place to go to understand your user count. 
- 
+
 To determine an organization's count of billable users in a calendar month, we count the users during that month who had a **billable user type** of either full platform user or core user. A user’s **billable user type** is defined as the highest user type that the user was set at during a calendar month, no matter how briefly. 
 
 For an example of how this works in practice: If a user is set as a full platform user at any point during a month, their billable user type for that month is "full platform user," and won't change, even if they downgrade later that month. This is the case even if that user is changed to a full platform user only briefly.
- 
+
 Our billing logic has several implications for when you should adjust user type:
 * If you want to upgrade a user, you should do that at the beginning of the month.  
 * Similarly, if you want to downgrade a user, you should do that at the end of the month. 
 
 The count of your unique users is determined by email address. If there are multiple user records in an organization that have the same email address, for billing purposes those user records would count as a single user, and that user's billable user type would be their highest user type assigned during that month.
 
 The cost of your billable users depends on an organization’s [pricing edition](https://newrelic.com/pricing) (Standard, Pro, or Enterprise) or on any custom deals you have with New Relic. 
-
-When a New Relic organization first starts being billed, their billable user count is pro-rated based on when during the month they started. If an organization cancels their subscription, prorating is also applied for their last month. 
-
-### Rules for changing user type [#nr1core-downgrade-rules]
-
-How frequently you can downgrade a full platform user depends on your [usage plan](#?): 
-
-* Pay-as-you-go: There are no rules limiting changing user type but remember that [upgrading a user has billing impacts](#nr1core-user-calculation). 
-* Annual pool of funds: 
-  * When upgrading a user, remember that [upgrading has billing impacts](#nr1core-user-calculation). 
-  * Because the annual pool of funds [usage plan](?) involves a longer-term commitment, we limit how frequently full platform users can be downgraded. A user can only go from having a full platform user billable user type to a lower billable user type twice during one contract year (defined as a year starting at an organization’s contract starting point, or at the anniversary of that contract start). Once that limit is exceeded, that user is considered a full platform user for the remaining months in that year. 
-    * Let’s look at an example of how this works for an organization whose year-long contract started March 1st. A full platform user switches to a basic user for the month of May, then goes back to being a full platform user for the month of June, and then becomes a basic user for the month of August. That user has reached the two-times-per-year limit. If that user then becomes a billable full platform user again for a subsequent calendar month in that remaining year, that user counts as full platform user for the remaining months in that contract year, regardless of what their user type is changed to. 
-
-### Details about opting in to core users [#nr1core-optin]
-
-Some New Relic organizations that existed prior to December 15, 2021 have a self-serve option in the UI for opting in to the core users version of pricing. The UI acceptance form is called the “core user addendum." By accepting this addendum, the New Relic user is stating that they're authorized to accept those terms for their organization. 
 
-The core user addendum is available to organizations that: 
-* ... ? 
-* ... ? 
-
-When your organization opts in, your organization has a seven-day grace period, during which your users’ user type won’t affect your bill. This gives you time to [decide which user type to assign your users](?). After your grace period ends, the normal billing calculations apply. 
-
-If your organization has opted in to add core users, the [two-times-per-year limit on downgrading full platform users](#nr1core-downgrade-rules) will apply from when you opted in until the renewal of your subscription term or, if applicable, the annual anniversary date of your commitment term, whichever is earlier. 
+When a New Relic organization first starts being billed, their billable user count is pro-rated based on when during the month they started. If an organization cancels their subscription, prorating is also applied for their last month. 
 
+For rules pertaining to downgrading users, see [Downgrade rules](#user-downgrade-rules).
 
 </Collapser>
 
@@ -120,24 +120,55 @@ If your organization is on the New Relic One pricing model but doesn't have the
 
 * **How billable users are determined.** For a calendar month, an organization is billed based on a calculation of the number of full platform users for that month. 
 * **Prorating in first and last month.** The count of billable users is prorated based on when a New Relic organization starts their subscription, or based on when a user becomes a full platform user (added as a full platform user or converted to one).
-* **Downgrading full platform users.** User type is meant to be a fairly long-term setting based on a user’s expected New Relic duties and responsibilities. For that reason, a full platform user may only be downgraded a maximum of two times in a 12-month period. If a user’s user type has changed more than this allowed number of changes, New Relic can charge that user as a full platform user. 
 * **Users are billable when provisioned.** A user counts as billable the moment they are set to a billable user type in New Relic. This applies regardless of whether that user has ever logged into or used New Relic. 
 * **User count based on email address.** If there are multiple user records in an organization that have the same email address, for billing purposes that would count as a single user.
 * **Caveat for our original user model.** If your organization has users on our [original user model](?): If a user is set as a basic user in one account in the organization and as a billable user in another account, the billable user status takes precedence.
 
-### Change to "full user" user type name [#full-user-language]
+For rules pertaining to downgrading users, see [Downgrade rules](#user-downgrade-rules).
 
-On December 16, 2021, the “full user” user type was renamed to “full platform user." For organizations that were on the New Relic One pricing plan before that date and have not opted in to the [core users version](#nr1-pricing-with-core), “full platform users” are equivalent to “full users” or “monthly provisioned users” in their New Relic agreement. 
+</Collapser>
 
-One exception to this: For organizations on the [New Relic One without core users version of pricing](#nr1-pricing-without-core), the "full user" term is still used as an attribute when [querying full user counts](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts). 
+</CollapserGroup>
+
+## User downgrade rules [#user-downgrade-rules]
+
+The rules governing downgrading users depends on which of the [two versions of New Relic One pricing](#core-users-pricing) you’re on: 
+
+<CollapserGroup>
+
+  <Collapser
+    id="nr1-with-core-downgrade"
+    title="New Relic One with core users - downgrade policies"
+  >
+ <Callout variant="important">
+On December 17, 2021, we released a version of New Relic One pricing that added a new user type ([core user](/docs/accounts/accounts-billing/new-relic-one-user-management/user-type)) and changed how billable users are counted. [Learn more about this core users release.](#core-users-pricing)
+</Callout>
+
+How frequently you can downgrade a full platform user depends on your [usage plan](#?): 
+
+* Pay-as-you-go: There are no rules limiting changing user type but remember that [upgrading a user has billing impacts](#nr1core-user-calculation). 
+* Annual pool of funds: 
+  * When upgrading a user, remember that [upgrading has billing impacts](#nr1core-user-calculation). 
+  * Because the annual pool of funds [usage plan](?) involves a longer-term commitment, we limit how frequently full platform users can be downgraded. A user can only go from having a full platform user billable user type to a lower billable user type twice during one contract year (defined as a year starting at an organization’s contract starting point, or at the anniversary of that contract start). Once that limit is exceeded, that user is considered a full platform user for the remaining months in that year. 
+    * Let’s look at an example of how this works for an organization whose year-long contract started March 1st. A full platform user switches to a basic user for the month of May, then goes back to being a full platform user for the month of June, and then becomes a basic user for the month of August. That user has reached the two-times-per-year limit. If that user then becomes a billable full platform user again for a subsequent calendar month in that remaining year, that user counts as full platform user for the remaining months in that contract year, regardless of what their user type is changed to. 
 
 </Collapser>
 
-</CollapserGroup>
+  <Collapser
+    id="nr1-without-core-downgrade"
+    title="New Relic One without core users - downgrade policies"
+  >
+ <Callout variant="important">
+[Before reading this, ensure you're on the "New Relic One without core users" version.](#core-users-pricing)
+</Callout>
 
-## Restrictions on sharing logins [#login-sharing]
+User type is meant to be a fairly long-term setting based on a user’s expected New Relic duties and responsibilities. For that reason, a full platform user may only be downgraded a maximum of two times in a 12-month period. If a user’s user type has changed more than this allowed number of changes, New Relic can charge that user as a full platform user. 
 
-A New Relic user is prohibited from sharing their login with other people. To allow you to use New Relic on several devices, a user’s login credentials can be associated with a maximum of either three concurrent active sessions or three unique IP addresses at one time. 
+[this seems illogical to me for PAYG, because we can't force them to keep paying us when they're PAYG, right?]
+
+</Collapser>
+
+</CollapserGroup>
 
 ## What can I get for free? [#free]
 
@@ -156,4 +187,6 @@ When you’re on New Relic One pricing, you can have one of two types of usage p
 
 For more detail about how your usage plan can affect your user downgrade rules, see [User count calculations](#user-count). 
 
-
+## Restrictions on sharing logins [#login-sharing]
+[need better place for this]
+A New Relic user is prohibited from sharing their login with other people. To allow you to use New Relic on several devices, a user’s login credentials can be associated with a maximum of either three concurrent active sessions or three unique IP addresses at one time.