Merge pull request #18601 from animalet/asegura/source-monitoring-cro…

…ss-accounts

Describe AWS monitoring and source accounts for AWS cross account

src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-billing-monitoring-integration.mdx

@@ -49,7 +49,7 @@ Enabling AWS budgets allows New Relic to capture service consumptions as well as
   If you have **not** created a role in AWS, follow the procedure to [connect AWS to New Relic](/docs/infrastructure/infrastructure-integrations/getting-started/connect-aws-integrations-infrastructure#connect) before configuring a budget policy.
 </Callout>
 
-1. From the AWS Management console, select <DNT>**Services > IAM > Roles**</DNT>.
+1. From the AWS Management Console, select <DNT>**Services > IAM > Roles**</DNT>.
 2. Select the role you have configured for New Relic, then select <DNT>**Permissions**</DNT>.
 3. From the selected role's <DNT>**Inline policy**</DNT> tab, select the expand <Icon name="fe-chevron-down"/>
    icon if one already exists, or select the option to add a new inline policy to the role.

src/content/docs/infrastructure/amazon-integrations/connect/aws-multi-account.mdx

@@ -40,7 +40,10 @@ Check the following:
 
 You'll need to have access to the AWS Management Console of both monitoring and source accounts.
 
-1. Go to the AWS management console of the monitoring account and copy the <DNT>**Monitoring accounts sink ARN**</DNT>. Follow these steps:
+* **Source AWS account(s)**: These are individual AWS accounts that generate observability data for the resources that reside in them. Source accounts share their observability data with the monitoring account.
+* **Monitoring AWS account**: This is a central AWS account that can view and interact with observability data generated from source accounts. It collects the telemetry from these accounts and pushes it to New Relic.
+
+1. Go to the AWS Management Console of the monitoring account and follow these steps to copy the <DNT>**Monitoring accounts sink ARN**</DNT>:
 
     - Go to <DNT>**CloudWatch > Settings**</DNT>.
     - Click on <DNT>**Manage monitoring account**</DNT>.
@@ -51,7 +54,7 @@ You'll need to have access to the AWS Management Console of both monitoring and
         Each account can have one sink per region, so if you need to monitor multiple regions, you need to set up a sink for each region.
     </Callout>
 
-2. Go to the AWS management console of the source account and [link the monitoring account](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Unified-Cross-Account-Setup.html) for the <DNT>**Metrics****</DNT> resources:
+2. Go to the AWS Management Console of the source account and [link the monitoring account](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Unified-Cross-Account-Setup.html) for the <DNT>**Metrics**</DNT> resources:
 
     - Go to <DNT>**Cloudwatch > Settings**</DNT>.
     - In the <DNT>**Source account configuration**</DNT> section, click on <DNT>**Configure**</DNT>.
@@ -60,7 +63,7 @@ You'll need to have access to the AWS Management Console of both monitoring and
     - Paste the previously copied sink ARN in <DNT>**Sink ARN**</DNT> field.
     - Click on <DNT>**Link**</DNT> and confirm.
 
-3. Go back to the AWS management console of the monitoring account:
+3. Go back to the AWS Management Console of the monitoring account:
 
     - Go to <DNT>**CloudWatch > Settings**</DNT>.
     - Click on <DNT>**Manage monitoring account**</DNT> and check that the source account is listed.