Merge branch 'develop' of github.com:newrelic/docs-website into liz/i…

…mg-styling

gatsby-config.js

@@ -209,9 +209,6 @@ module.exports = {
               maxWidth: 850,
             },
           },
-          autoLinkHeaders,
-          // This MUST come after `gatsby-remark-autolink-headers` to ensure the
-          // link created for the icon has the proper id
           'gatsby-remark-custom-heading-ids',
         ],
       },

src/content/docs/accounts/accounts-billing/account-setup/downgradecancel-account.mdx

@@ -74,7 +74,7 @@ Other options for cancelling your organization depend on your pricing edition:
     2. Then click **Organization and access**.
     3. Click **Delete organization**.
 
-    Requirements to be able to delete your own organization:
+       Requirements to be able to delete your own organization:
 
     * Organization has a single account, and single user.
     * Is on both the new [pricing model](/docs/accounts/original-accounts-billing/original-product-based-pricing/overview-changes-pricing-user-model#pricing-plans) and the [New Relic One user model](/docs/accounts/original-accounts-billing/original-users-roles/overview-user-models).

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

@@ -120,29 +120,29 @@ Here are example queries for these two pricing versions:
     * Use only the `NrMTDConsumption` event.
     * The attributes used to query by user type are: `BasicUsersBillable`, `CoreUsersBillable`, and `FullPlatformUsersBillable`.
 
-    Here are some example NRQL queries for determining user count:
+      Here are some example NRQL queries for determining user count:
 
-    **Month-to-date full platform users**
-    This query shows the billable full platform users for the month. In other words, it shows how much you'd be billed for your full platform users for that month if you were billed right now.
+      **Month-to-date full platform users**
+      This query shows the billable full platform users for the month. In other words, it shows how much you'd be billed for your full platform users for that month if you were billed right now.
 
-    ```
-    FROM NrMTDConsumption SELECT latest(FullPlatformUsersBillable) SINCE this month
-    ```
+      ```
+      FROM NrMTDConsumption SELECT latest(FullPlatformUsersBillable) SINCE this month
+      ```
 
-    **Month-to-date core users**
-    This query shows the number of core users you’d be billed for if you were billed right now:
+      **Month-to-date core users**
+      This query shows the number of core users you’d be billed for if you were billed right now:
 
-    ```
-    FROM NrMTDConsumption SELECT latest(CoreUsersBillable) SINCE this month
-    ```
+      ```
+      FROM NrMTDConsumption SELECT latest(CoreUsersBillable) SINCE this month
+      ```
 
-    **Track users during the switch to core users pricing version**
+      **Track users during the switch to core users pricing version**
 
-    If your organization started out with [New Relic One pricing without core users](#user-queries) and opted in to switch to the [core users release](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/core-users-release), the usage UI will track the count of your billable users over that transition. Here's an example of a query that would display the count of full platform users over that transition period:
+      If your organization started out with [New Relic One pricing without core users](#user-queries) and opted in to switch to the [core users release](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/core-users-release), the usage UI will track the count of your billable users over that transition. Here's an example of a query that would display the count of full platform users over that transition period:
 
-    ```
-    FROM NrMTDConsumption SELECT latest(billableConsumption) as 'Full platform users' where metric in ('FullPlatformUsers', 'FullUsers') SINCE 4 month ago limit max TIMESERIES 
-    ```
+      ```
+      FROM NrMTDConsumption SELECT latest(billableConsumption) as 'Full platform users' where metric in ('FullPlatformUsers', 'FullUsers') SINCE 4 month ago limit max TIMESERIES 
+      ```
   </Collapser>
 
   <Collapser
@@ -158,46 +158,46 @@ Here are example queries for these two pricing versions:
     * You can use the `NrMTDConsumption` or `NrConsumption` event.
     * The attributes used to query by user type are: `BasicUsersBillable`, and `FullUsersBillable`.
 
-    **Billable full platform users for the month**
-    This query shows the billable full platform users for the month. In other words, it shows how much you'd be billed for your users for the current month if you were charged at that moment.
+      **Billable full platform users for the month**
+      This query shows the billable full platform users for the month. In other words, it shows how much you'd be billed for your users for the current month if you were charged at that moment.
 
-    ```
-    FROM NrMTDConsumption SELECT latest(FullUsersBillable) 
-      SINCE this month
-    ```
+      ```
+      FROM NrMTDConsumption SELECT latest(FullUsersBillable) 
+        SINCE this month
+      ```
 
-    This query shows how many full platform users were counted by hour. This is useful for seeing how the full platform user count changed over time.
+      This query shows how many full platform users were counted by hour. This is useful for seeing how the full platform user count changed over time.
 
-    ```
-    from NrConsumption SELECT max(FullUsers) 
-      SINCE 10 days ago TIMESERIES 1 hour
-    ```
+      ```
+      from NrConsumption SELECT max(FullUsers) 
+        SINCE 10 days ago TIMESERIES 1 hour
+      ```
 
-    **Projected monthly full platform user count**
-    This query shows a projected count of monthly full platform users. This query would not be good for using in a dashboard; it requires values based on a) the days remaining in the month, b) the start of the month. Here's an example querying the projected end-of-month count with 10 days left in that month:
+      **Projected monthly full platform user count**
+      This query shows a projected count of monthly full platform users. This query would not be good for using in a dashboard; it requires values based on a) the days remaining in the month, b) the start of the month. Here's an example querying the projected end-of-month count with 10 days left in that month:
 
-    ```
-    FROM NrMTDConsumption SELECT predictLinear(FullUsers, 10 days) 
-    SINCE '2020-09-01'
-    ```
+      ```
+      FROM NrMTDConsumption SELECT predictLinear(FullUsers, 10 days) 
+      SINCE '2020-09-01'
+      ```
 
-    **Count of full platform users and basic users**
-    The [usage UI](/docs/accounts/accounts-billing/new-relic-one-pricing-users/pricing-billing#billing-usage-ui) shows the count of full platform users and basic users. The query used is:
+      **Count of full platform users and basic users**
+      The [usage UI](/docs/accounts/accounts-billing/new-relic-one-pricing-users/pricing-billing#billing-usage-ui) shows the count of full platform users and basic users. The query used is:
 
-    ```
-    FROM NrUsage SELECT max(usage) SINCE 10 days ago
-    WHERE productLine='FullStackObservability' 
-    WHERE metric in ('FullUsers', 'BasicUsers') 
-    FACET metric
-    ```
+      ```
+      FROM NrUsage SELECT max(usage) SINCE 10 days ago
+      WHERE productLine='FullStackObservability' 
+      WHERE metric in ('FullUsers', 'BasicUsers') 
+      FACET metric
+      ```
 
-    To see the count of full platform users and basic users over time:
+      To see the count of full platform users and basic users over time:
 
-    ```
-    FROM NrUsage SELECT max(usage) SINCE 10 days ago
-    WHERE productLine='FullStackObservability' 
-    WHERE metric in ('FullUsers', 'BasicUsers') FACET metric TIMESERIES 1 hour
-    ```
+      ```
+      FROM NrUsage SELECT max(usage) SINCE 10 days ago
+      WHERE productLine='FullStackObservability' 
+      WHERE metric in ('FullUsers', 'BasicUsers') FACET metric TIMESERIES 1 hour
+      ```
   </Collapser>
 </CollapserGroup>
 

src/content/docs/accounts/accounts-billing/new-relic-one-user-management/tutorial-add-new-user-groups-roles-new-relic-one-user-model.mdx

@@ -82,16 +82,15 @@ To view existing access grants: from the [account dropdown](/docs/using-new-reli
   alt="New Relic organization and access UI - access grants view"
   src={newRelicOneUserMgmt}
 />
-<figcaption>This is what you might see when you go to the **Organization and access** UI and view groups. The default available groups of **Admin** and **User** have access grants automatically created that grant users in those groups access to the roles associated with those groups and to the initial account those users were added in.</figcaption>
+
+<figcaption>
+  This is what you might see when you go to the **Organization and access** UI and view groups. The default available groups of **Admin** and **User** have access grants automatically created that grant users in those groups access to the roles associated with those groups and to the initial account those users were added in.
+</figcaption>
 
 To create a new access grant that gives a user group access to a role and an account:
 
 1. From the **Organization and access** UI, click **Group access**. If you don't see that UI, it may be because you're logged in with an [original user model](/docs/accounts/original-accounts-billing/original-product-based-pricing/overview-user-models) record, or because you don't have the ability to manage users. For more on such factors, see [Factors affecting access](/docs/accounts/accounts-billing/account-structure/factors-affecting-access-features-data/).
-   <img
-     title="Group access UI"
-     alt="Group access UI"
-     src={groupAccessUi}
-   />
+   <img title="Group access UI" alt="Group access UI" src={groupAccessUi}/>
 2. Choose one of the following:
 
 * **Existing**: If there is already a group you want to add an access grant to, you can use this. For example, if you want to gives users in the default [**Admin** or **User** group](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts#groups) access to new accounts, you might choose this and then select the **Admin Default** or **Admin User** role.

src/content/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts.mdx

@@ -51,7 +51,10 @@ When you initially sign up for New Relic, your organization has some built-in ac
   alt="New Relic organization and access UI - default access grants"
   src={organizationAndAccessUiDefaultGroups}
 />
-<figcaption>A view of the **Organization and access** UI, showing how our default groups (**Admin** and **User**) have access grants that associate the groups with a) specific roles, and b) either a specific account or the entire organization. (Note that this UI is available only for users on the [New Relic One user model](/docs/accounts/original-accounts-billing/original-users-roles/overview-user-models).)</figcaption>
+
+<figcaption>
+  A view of the **Organization and access** UI, showing how our default groups (**Admin** and **User**) have access grants that associate the groups with a) specific roles, and b) either a specific account or the entire organization. (Note that this UI is available only for users on the [New Relic One user model](/docs/accounts/original-accounts-billing/original-users-roles/overview-user-models).)
+</figcaption>
 
 Here's a diagram showing how access grants work and how they relate to the broader organization:
 
@@ -157,13 +160,11 @@ Here's a table with our standard roles. To better understand the account-scoped
       </td>
 
       <td>
-        Provides access to our platform features (for example, APM UI and browser monitoring UI), but lacks permissions to configure those features and lacks organization-level and user management permissions. This role is essentially the **All product admin** role without the ability to configure platform features.  
-
+        Provides access to our platform features (for example, APM UI and browser monitoring UI), but lacks permissions to configure those features and lacks organization-level and user management permissions. This role is essentially the **All product admin** role without the ability to configure platform features.
       </td>
 
       <td>
-        Any. Recommended: core or full platform.  
-
+        Any. Recommended: core or full platform.
       </td>
     </tr>
 
@@ -313,7 +314,10 @@ A role, whether one of our [standard roles](#standard-roles) or a custom role, i
   alt="New Relic user capabilities UI screenshot"
   src={newRelicUserCapabilitiesUi}
 />
-<figcaption>A view of the capabilities associated with the [**All product admin** role](#standard-roles). When creating a custom role, you can select a custom set of capabilities. Note that the capabilities exposed in the UI may change over time: this screenshot was taken January 2022.</figcaption>
+
+<figcaption>
+  A view of the capabilities associated with the [**All product admin** role](#standard-roles). When creating a custom role, you can select a custom set of capabilities. Note that the capabilities exposed in the UI may change over time: this screenshot was taken January 2022.
+</figcaption>
 
 Note that some of the standard roles have hidden capabilities not available for selection when building a custom role. For more detail, see [Standard roles](#standard-roles). Also note that the roles UI shows account-scoped roles but does **not** show organization-scoped roles (**Organization manager** and **Authentication domain manager**).
 

src/content/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-ui-and-tasks.mdx

@@ -53,7 +53,10 @@ Some user management requirements and restrictions:
   alt="New Relic One organization and access UI"
   src={newRelicOneUserMgmt}
 />
-<figcaption>In the **Organization and access** UI, you can create access grants, custom groups, custom roles, and configure an authentication domain.</figcaption>
+
+<figcaption>
+  In the **Organization and access** UI, you can create access grants, custom groups, custom roles, and configure an authentication domain.
+</figcaption>
 
 Here are some example user management procedures:
 
@@ -76,20 +79,20 @@ Here are some example user management procedures:
     * [User downgrade rules](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/user-count-billing#user-downgrade-rules)
     * If you're using [automated user management](/docs/accounts/accounts/automated-user-management/automated-user-provisioning-single-sign), you have [other options for managing user type](/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more/#user-upgrade).
 
-    To change the user type of one or more users:
+      To change the user type of one or more users:
 
     1. From the [**User management** UI](#where), click the checkboxes for the users whose user type you want to edit.
     2. Once you start selecting users, an option will appear for **Edit type**.
 
-    You can also edit the user type and group of a specific user by clicking on that user.
+       You can also edit the user type and group of a specific user by clicking on that user.
 
-    <img
-      title="Edit user type in the UI"
-      alt="New Relic user management UI - edit user type"
-      src={userManagementEditUserType}
-    />
+       <img
+         title="Edit user type in the UI"
+         alt="New Relic user management UI - edit user type"
+         src={userManagementEditUserType}
+       />
 
-    To manage how users upgrade their user type, see the [authentication domain settings](/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more/#user-upgrade).
+       To manage how users upgrade their user type, see the [authentication domain settings](/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more/#user-upgrade).
   </Collapser>
 
   <Collapser

src/content/docs/accounts/accounts/automated-user-management/okta-scimsso-application-configuration.mdx

@@ -113,11 +113,7 @@ To manage your users' user type from Okta:
 4. Next, you'll configure your Okta user profile to have this field. Steps:
    * In the **Profile editor**, go to **Users** and click the **User (default)** profile.
    * Add a new **New Relic user type** attribute to that profile ([see Okta user profile instructions](https://developer.okta.com/docs/concepts/user-profiles/#universal-directory-schemas)). How you set this will depend on your own setup and preferences for defining user type. Note that the expected values for user type are `Basic user`, `Core user`, and `Full user`. Below is an example with information filled in.
-     <img
-       title="Set Okta user profile to have new attribute"
-       alt="Set Okta user profile to have new attribute"
-       src={oktaAddUserTypeToProfile}
-     />
+     <img title="Set Okta user profile to have new attribute" alt="Set Okta user profile to have new attribute" src={oktaAddUserTypeToProfile}/>
 
 5. In the **People** section, define the user type for your users. How you do this will depend on your setup and preferences. For example, you may choose to set this manually by setting each user’s user type, or you may use Okta to manage these in bulk.