update

Author: ProfessorKendrick

articles/partner-solutions/new-relic/manage.md

@@ -28,7 +28,7 @@ The *Essentials* details include:
 - Pricing plan
 - Billing term
 
-Select the links next to corresponding details to manage your resource.
+To manage your resource, select the links next to corresponding details.
 
 Below the essentials, you can navigate to other details about your resource by selecting a tab.
 
@@ -66,22 +66,22 @@ The column **Logs to New Relic** indicates whether the resource is sending logs
 
 ## Monitor multiple subscriptions
 
-You can now monitor all your subscriptions through a single New Relic resource using **Monitored Subscriptions**. You don't have to set up a New Relic resource in every subscription that you intend to monitor. Instead, monitor multiple subscriptions by linking them to a single New Relic resource tied to a New Relic organization. This provides a single pane view for all resources across multiple subscriptions.
+You can now monitor all your subscriptions through a single New Relic resource using **Monitored Subscriptions**. You don't have to set up a New Relic resource in every subscription that you intend to monitor. Instead, monitor multiple subscriptions by linking them to a single New Relic resource tied to a New Relic organization to view all resources across multiple subscriptions from a single pane.
 
 To monitor multiple subscriptions:
 
 1. Select **New Relic account config** > **Monitored Subscriptions** from the *Service menu*. 
 
 1. Select **Add subscriptions**. 
 
-    Subscriptions you have _Owner_ role assigned to and New Relic resource(s) created in those subscriptions which are linked to the same New Relic organization as the current resource display in the Add subscriptions panel.
+    A list of subscriptions displays in the working pane.
 
     > [!TIP]
-    > If the subscription you want to monitor has a resource already linked to the same New Relic org, we recommended that you delete the New Relic resources to avoid shipping duplicate data, and incurring double the charges.
+    > If the subscription you want to monitor has a resource already linked to the same New Relic organization, we recommend deleting one to avoid shipping duplicate data, which results in duplicate charges.
 
 1. Select the subscriptions you want to monitor through the New Relic resource and select the **Add** button.
 
-    If the list doesn’t update automatically, select **Refresh**.  When the subscription is successfully added, you see the status is updated to **Active**. If a subscription fails to get added, **Monitoring Status** shows as **Failed**.
+    If the list doesn’t update automatically, select **Refresh**. When the subscription is successfully added, you see the status is updated to **Active**. If a subscription fails to get added, **Monitoring Status** shows as **Failed**.
 
 The set of tag rules for metrics and logs defined for the New Relic resource apply to all subscriptions that are added for monitoring. Setting separate tag rules for different subscriptions isn't supported. Diagnostics settings are automatically added to resources in the added subscriptions that match the tag rules defined for the New Relic resource.
 
@@ -91,7 +91,7 @@ The tag rules and logs that you defined for the New Relic resource apply to all
 
 ## Connected New Relic resources
 
-To view and manage all New Relic Resources you've created, select **New Relic account config** > **Connected New Relic Resources** from the *Service menu*. 
+To view and manage all your New Relic Resources, select **New Relic account config** > **Connected New Relic Resources** from the *Service menu*. 
 
 > [!NOTE]
 > - Your Azure role must be set to *Owner* or a *Contributor* for the subscription to manage these resources.
@@ -131,7 +131,7 @@ To monitor Virtual Machine Scale Sets using the New Relic Agent:
     A list of all Virtual Machine Scale Sets in the subscription displays in the working pane.
 
 > [!NOTE]
-> In manual upgrade policy, preexisting VM instances don't receive the extension automatically. The agent status shows as **Partially Installed**. Upgrade the VM instances by manually installing the extension on them from the VM extensions Resource menu, or go to specific Virtual Machine Scale Sets and select **Instances** from the Resource menu.
+> In manual upgrade policy, preexisting instances don't receive the extension automatically. The agent status shows as **Partially Installed**. Upgrade instances by manually [installing a New Relic agent](#install-a-new-relic-agent) for each preexisting virtual machine.
 
 > [!NOTE]
 > The agent installation dashboard supports the automatic and rolling upgrade policy for Flex orchestration mode in the next release when similar support is available from Virtual Machine Scale Sets Flex resources.
@@ -152,8 +152,8 @@ For each app service, the following information appears:
 > [!IMPORTANT]
 >
 > - App Service extensions only supported for app services that are running on Windows operating systems.
-> - App Services that use Linux operating systems are not displayed.
-> - You can only manage Web App App Services. Function Apps are not supported at this time. 
+> - App Services that use Linux operating systems aren't displayed.
+> - You can only manage Web App Services. Function Apps aren't supported at this time. 
 
 ### Install a New Relic agent
 
@@ -170,7 +170,7 @@ The application settings for the selected Virtual Machine, Virtual Machine Scale
 [!INCLUDE [delete-resource](../includes/delete-resource.md)]
 
 > [!NOTE]
-> If you have other New Relic resources linked to the New Relic account, billing for those other resources continues through the Azure Marketplace.
+> If you have other New Relic resources linked to the New Relic account, billing for those other resources continues through Azure Marketplace.
 
 ## Next steps
 

articles/partner-solutions/new-relic/overview.md

@@ -13,16 +13,16 @@ Microsoft and New Relic developed this service and manage it together.
 
 You can find Neon Serverless Postgres (Preview) in the [Azure portal](https://portal.azure.com/#view/HubsExtension/BrowseResource/resourceType/NewRelic.Observability%2Fmonitors) or get it on [Azure Marketplace](https://azuremarketplace.microsoft.com/marketplace/apps/newrelicinc1635200720692.newrelic_liftr_payg?tab=Overview).
 
-New Relic is a full-stack observability platform that enables a single source of truth for application performance, infrastructure monitoring, log management, error tracking, real-user monitoring, and more. Combined with the Azure platform, use Azure Native New Relic Service to help monitor, troubleshoot, and optimize Azure services and applications.
+New Relic is a full-stack observability platform that enables a single source of truth for application performance, infrastructure monitoring, log management, error tracking, and real-user monitoring. Combined with the Azure platform, use Azure Native New Relic Service to help monitor, troubleshoot, and optimize Azure services and applications.
 
 Azure Native New Relic Service in Marketplace enables you to create and manage New Relic accounts by using the Azure portal with a fully integrated experience. Integration with Azure enables you to use New Relic as a monitoring solution for your Azure workloads through a streamlined workflow, starting from procurement and moving all the way to configuration and management.
 
 You can create and manage the New Relic resources by using the Azure portal through a resource provider named `NewRelic.Observability`. New Relic owns and runs the software as a service (SaaS) application, including the New Relic organizations and accounts that are created through this experience.
 
 > [!IMPORTANT]
-> For New Relic accounts you create by using Azure Native New Relic Service, customer data is stored and processed in the region where the service was deployed. Currently, Azure Native New Relic Service does not support Sovereign Cloud.
+> For New Relic accounts you create by using Azure Native New Relic Service, customer data is stored and processed in the region where the service was deployed. Currently, Azure Native New Relic Service doesn't support Sovereign Cloud.
 >
-> For accounts that you create directly by using the New Relic portal and use for linking, New Relic determines where the customer data is stored and processed. Depending on the configuration at the time of setup, this might be on or outside Azure.
+> For accounts that you create directly by using the New Relic portal and use for linking, New Relic determines where the customer data is stored and processed. Depending on the configuration at the time of setup, this data might be on or outside Azure.
 
 ## Capabilities
 
@@ -46,7 +46,7 @@ When you use the integrated New Relic experience in the Azure portal by using Az
 - **Azure Marketplace SaaS resource**: When you set up a new account and organization on New Relic by using Azure Native New Relic Service, the SaaS resource is created automatically, based on the plan that you select from the Azure New Relic offer in Azure Marketplace. This resource is used for billing.
 
 > [!NOTE]
-> The Azure Marketplace SaaS resource is set up only if you created the New Relic organization by using Azure Native New Relic Service. If you created your New Relic organization directly from the New Relic portal, the Azure Marketplace SaaS resource doesn't exist, and New Relic manages your billing.
+> Azure Marketplace SaaS resource is set up only if you created the New Relic organization by using Azure Native New Relic Service. If you created your New Relic organization directly from the New Relic portal, Azure Marketplace SaaS resource doesn't exist, and New Relic manages your billing.
 
 ### Logs
 

articles/partner-solutions/new-relic/troubleshoot.md

@@ -44,7 +44,7 @@ New Relic manages the APIs for creating and managing resources, and for the stor
 
 ## Diagnostic settings are active even after disabling the New Relic resource or applying necessary tag rules
 
-If logs are being emitted and diagnostic settings remain active on monitored resources even after the New Relic resource is disabled or tag rules have been modified to exclude certain resources, it's likely that there's a delete lock applied to the resource(s) or the resource group containing the resource. This lock prevents the cleanup of the diagnostic settings, and hence, logs continue to be forwarded for those resources. To resolve this, remove the delete lock from the resource or the resource group. If the lock is removed after the New Relic resource is deleted, the diagnostic settings have to be cleaned up manually to stop log forwarding.
+If logs are being emitted and diagnostic settings remain active on monitored resources even after the New Relic resource is disabled or tag rules were modified to exclude certain resources, it's likely that there's a delete lock applied to the resources or the resource group containing the resource. This lock prevents the cleanup of the diagnostic settings, and hence, logs continue to be forwarded for those resources. To resolve the issue, remove the delete lock from the resource or the resource group. If the lock is removed after the New Relic resource is deleted, the diagnostic settings have to be cleaned up manually to stop log forwarding.
 
 [!INCLUDE [diagnostic-settings](../includes/diagnostic-settings.md)]