Merge pull request #7547 from newrelic/Changes-to-user-tutorial

fix(accounts): clarifying when create accounts

src/content/docs/accounts/accounts-billing/account-structure/new-relic-account-structure.mdx

@@ -6,7 +6,7 @@ metaDescription: An explanation of New Relic organization and account structure.
 redirects:
   - /docs/new-relic-account-structure
   - /docs/accounts/accounts-billing/new-relic-one-pricing-users/account-user-structure
-  - /docs/accounts/accounts-billing/new-relic-one-pricing-users/new-relic-account-structure
+  - /docs/accounts/accounts-billing/new-relic-one-pricing-users/new-relic-account-structure 
 ---
 
 Depending on your [user model](/docs/accounts/original-accounts-billing/original-users-roles/overview-user-models), you have different options for adding and managing accounts and assigning users to them. We have two user models:
@@ -22,17 +22,17 @@ At New Relic, an "organization" represents a New Relic customer. The organizatio
 
 When a New Relic organization is created, it contains a single account. A Standard edition organization can only have a single account, but Pro and Enterprise edition organizations can add more accounts. 
 
-In general, you should aim for having as few accounts as possible. There's nothing preventing even large companies from having a single account, or a small number of accounts. The fewer accounts you have, the easier it is to see how all your monitored entities relate to each other using our platform. But there can be several reasons to add accounts, such as creating separate accounts for production and non-production environments, or if you want to establish firmer boundaries between different sets of data for any reason. If you're in doubt about why to create accounts, talk to your account representative.
+Why an organization creates new accounts depends on their goals and structure. There's nothing preventing even quite large companies from having a single account, or a handful of accounts. The fewer accounts you have, the easier it is to see how all your monitored entities relate to each other using our platform. But there can be several reasons to add accounts, such as creating separate accounts for production and non-production environments, or if you want to establish firmer boundaries between different sets of data for any reason. If you're in doubt about why to create accounts, talk to your account representative.
 
 Each account in an organization has its own [account ID](/docs/accounts/accounts-billing/account-setup/account-id), and that ID is used for some account-specific tasks, like making API calls.
 
 To add and rename accounts, you can [use our NerdGraph API](/docs/apis/nerdgraph/examples/manage-accounts-nerdgraph) (UI features coming soon).
 
 ### How users access accounts [#account-access]
 
-In your organization, your New Relic users are granted access to specific accounts that are relevant to their duties and responsibilities. To manage users’ access to accounts, you create [access grants](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts#understand-concepts), which assign a group of users to a specific role on a specific account. For example, you might assign a group the ability to manage billing on some accounts using the [**Billing manager** role](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts#standard-roles), and assign some users as non-admin full platform users on some accounts, and assign some users as basic users on some accounts. Our user management system allows you to create the user access you need, whether that’s a relatively simple setup with just a few roles across a few accounts, or a complex one with many roles across many accounts. [Learn more about user management.](/docs/accounts/accounts-billing/new-relic-one-user-management/)
+In your organization, your New Relic users are granted access to specific accounts that are relevant to their duties and responsibilities. To manage users' access to accounts, you create [access grants](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts#understand-concepts), which assign a group of users to a specific role on a specific account. For example, you might assign a group the ability to manage billing on some accounts using the [**Billing manager** role](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts#standard-roles), and assign some users as non-admin full platform users on some accounts, and assign some users as basic users on some accounts. Our user management system allows you to create the user access you need, whether that's a relatively simple setup with just a few roles across a few accounts, or a complex one with many roles across many accounts. [Learn more about user management.](/docs/accounts/accounts-billing/new-relic-one-user-management/)
 
-Note that some features, like dashboards and workloads, can display data from across different accounts in an organization. This means that if a user isn’t granted access to all relevant accounts, they may experience missing data.
+Note that some features, like dashboards and workloads, can display data from across different accounts in an organization. This means that if a user isn't granted access to all relevant accounts, they may experience missing data.
 
 To learn more about access issues, see [Factors affecting access](/docs/accounts/accounts-billing/account-structure/factors-affecting-access-features-data/).
 

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

@@ -55,7 +55,7 @@ Some user management requirements and restrictions:
 />
 
 <figcaption>
-  In the **Organization and access** UI, you can create access grants, custom groups, custom roles, and configure an authentication domain.
+  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:
@@ -72,7 +72,7 @@ Here are some example user management procedures:
     id="edit-user-type"
     title="Edit user type (basic, core, full platform)"
   >
-    Before changing your users’ user type, we recommend you understand:
+    Before changing your users' user type, we recommend you understand:
 
     * [How to decide a user's user type](/docs/accounts/accounts-billing/new-relic-one-user-management/user-type#choose-user-type)
     * [How billable users are calculated](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/user-count-billing)
@@ -147,6 +147,10 @@ Here are some example user management procedures:
   </Collapser>
 </CollapserGroup>
 
+## Use our API [#api]
+
+To use our API to manage accounts and users, see our [NerdGraph tutorials](/docs/apis/nerdgraph/get-started/introduction-new-relic-nerdgraph/#tutorials).   
+
 ## Track changes [#track-changes]
 
 To see an audit log of changes to your account, including user management actions, you can query the [`NrAuditEvent`](/docs/insights/insights-data-sources/default-data/nrauditevent-event-data-query-examples).