docs: minor fixes to group management docs (#2592)

website/docs/d/group.html.markdown

@@ -8,11 +8,11 @@ description: |-
 
 # Data Source: newrelic\_group
 
-The `newrelic_group` data source allows users to search for a group by its name and retrieve the ID of the matching group and other associated attributes.
+The `newrelic_group` data source helps search for a group by its name and retrieve the ID of the matching group and other associated attributes.
 
 ## Example Usage
 
-The below example illustrates fetching a group's ID (and IDs of users who belong to the group, if any) using the required arguments.
+The below example illustrates fetching the ID of a group (and IDs of users who belong to the group, if any) using the required arguments.
 
 ```hcl
 data "newrelic_authentication_domain" "foo" {
@@ -36,7 +36,7 @@ The following arguments are supported:
 
 ## Attributes Reference
 
-In addition to the attributes listed above, the following attribute is also exported by this resource:
+In addition to the attributes listed above, the following attributes are also exported by this data source:
 
 * `id` - The ID of the fetched matching group.
 * `user_ids` - IDs of users who belong to the group. In the absence of any users in the group, the value of this attribute would be an empty list.

website/docs/d/user.html.markdown

@@ -8,11 +8,11 @@ description: |-
 
 # Data Source: newrelic\_user
 
-The `newrelic_user` data source may be used to search for a user by their name and/or email ID, and accordingly, fetch the ID of the matching user.
+The `newrelic_user` data source helps search for a user by their name and/or email ID, and accordingly, fetch the ID of the matching user.
 
 ## Example Usage
 
-The below example illustrates fetching a user's ID (and other arguments) using the ID of the authentication domain the user belongs to, as well as a name and/or email ID, which can be used as criteria to search for a user who matches these specified parameters.
+The below example illustrates fetching a the ID of a user (and other arguments) using the ID of the authentication domain the user belongs to, as well as a name and/or email ID, which can be used as criteria to search for a user who matches these specified parameters.
 ```hcl
 data "newrelic_authentication_domain" "foo" {
   name = "Test Authentication Domain"
@@ -39,13 +39,13 @@ The following arguments are supported:
 
 It should be noted that either `name` or `email_id` must be specified in order to retrieve a matching user.
 
--> **NOTE** If the specified `name` matches, or is contained in the names of multiple users in the account, the data source will return the first match from the list of all matching users retrieved from the API. However, when using the `email_id` argument as the search criterion, only the user with the specified email ID will be returned, as each user has a unique email ID and multiple users cannot have the same email ID.
+-> **NOTE** If the `name` specified in the configuration matches the names of multiple users in the account, the data source will return the first match from the list of all matching users retrieved from the API. However, when using the `email_id` argument as the search criterion, only the user with the specified email ID will be returned, as each user has a unique email ID and multiple users cannot have the same email ID.
 
 -> **NOTE** The ID of an authentication domain can be retrieved using its name, via the data source `newrelic_authentication_domain`, as shown in the example above. Head over to the documentation of this data source for more details and examples.
 
 ## Attributes Reference
 
-In addition to the attributes listed above, the following attribute is also exported by this resource:
+In addition to the attributes listed above, the following attribute is also exported by this data source:
 
 * `id` - The ID of the matching user fetched.
 

website/docs/guides/upcoming_synthetics_muted_status_eol_guide.html.markdown

@@ -12,7 +12,7 @@ Use this guide to find details on the upcoming end-of-life of the `MUTED` status
 ### About Synthetic Monitors' 'MUTED' Status and the EOL
 Synthetic Monitors have a `status` field that defines the activity of the monitor, and can currently be either of `ENABLED`, `DISABLED`, or `MUTED`. When a monitor is MUTED, it still functions as usual (runs tests), but is muted; i.e., it does not send out notifications in cases of failure.
 
-Since it has been announced that New Relic Synthetics will discontinue support for the `MUTED` status of monitors, slated to hit its end-of-life in February 2024 (see [this community post](https://forum.newrelic.com/s/hubtopic/aAX8W0000015BHc/endoflife-product-updates-july-2023-september-2023)), the `MUTED` value of `status` has been marked **deprecated** in the New Relic Terraform Provider, in late October 2023. The provider will also _soon_ **discontinue support** for the value `MUTED` pertaining to the `status` argument of resources operating on Synthetic Monitors, with a release of the Terraform Provider in February 2023.
+Since it has been announced that New Relic Synthetics will discontinue support for the `MUTED` status of monitors, slated to hit its end-of-life in February 2024 (see [this community post](https://forum.newrelic.com/s/hubtopic/aAX8W0000015BHc/endoflife-product-updates-july-2023-september-2023)), the `MUTED` value of `status` has been marked **deprecated** in the New Relic Terraform Provider, in late October 2023. The provider will also _soon_ **discontinue support** for the value `MUTED` pertaining to the `status` argument of resources operating on Synthetic Monitors, with a release of the Terraform Provider in February/March 2024.
 
 This would affect all resources in the provider used to manage Synthetic Monitors (_only if_ your configuration comprises these resources with a `status = "MUTED"` argument), i.e.
 * [`newrelic_synthetics_monitor`](https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/resources/synthetics_monitor)