Apply suggestions from code review

src/content/docs/errors-inbox/group-request-errors.mdx

@@ -99,7 +99,7 @@ Resolved errors include a banner containing details on the user who resolved the
 
 ### Profiles [#error-profiles]
 
-When looking at a specific error, the profiles section provides visual details about significant differences in the frequency of different values for HTTP error events. For each attribute, the error profile includes:
+When you look at a specific error,, the profiles section provides visual details about significant differences in the frequency of different values for HTTP error events. For each attribute, the error profile includes:
 * A heatmap showing how the error's attribute is distributed for values that deviate the most
 * A label comparing the error attribute's distribution to that of other errors
 
@@ -118,7 +118,7 @@ When looking at a specific error, the profiles section provides visual details a
 
 ### Triage [#triage-errors]
 
-When looking at a specific error, the triage section associates the specific error occurrence you are viewing with its [system-created error group](/docs/errors-inbox/errors-inbox/#groups). These system-created error groups are identified by a unique fingerprint. It is this unique fingerprint that allows you to triage error groups by status updates or assignments.
+When you look at a specific error, the triage section associates the specific error occurrence you are viewing with its [system-created error group](/docs/errors-inbox/errors-inbox/#groups). These system-created error groups are identified by a unique fingerprint. It is this unique fingerprint that allows you to triage error groups by status updates or assignments.
 
 For more info on how error groups are created, see [How error groups work](/docs/errors-inbox/errors-inbox/#how-groups-work), and to learn more about status and assignments, see [Error tracking](/docs/errors-inbox/errors-inbox/#assign).
 
@@ -135,7 +135,7 @@ For more info on how error groups are created, see [How error groups work](/docs
 
 ### Distributed trace [#distributed-trace]
 
-When looking at a specific error, the distributed trace section tracks and observes your requests as they flow through your application, traversing various services to reach completion. By visualizing the entire request path across different services, you can rapidly identify failures or performance bottlenecks.
+When you look at a specific error, the distributed trace section tracks and observes your requests as they flow through your application, traversing various services to reach completion. By visualizing the entire request path across different services, you can rapidly identify failures or performance bottlenecks.
 
 To learn more about how distributed tracing works, see [Track requests across your microservices](/docs/distributed-tracing/concepts/introduction-distributed-tracing/).
 
@@ -169,7 +169,7 @@ We capture the response body for requests whenever available, displaying it on t
 
 ### Event trail [#event-trail]
 
-The event trail provides a chronological log of all events leading up to the request error, which helps with root cause analysis. These can be events New Relic monitors by default, or custom events. The event trail is sorted chronologically, beginning with the oldest event, which is typically the app launch, but you can modify the following:
+When you look at a specific error, the event trail provides a chronological log of all events leading up to the request error, which helps with root cause analysis. These can be events New Relic monitors by default, or custom events. The event trail is sorted chronologically, beginning with the oldest event, which is typically the app launch, but you can modify the following:
 
 * Sort: Toggle between ascending and descending order
 * Event filtering: Filter by event type, like `app launch`, `request`, `request error`,  or `user actions`.
@@ -199,7 +199,7 @@ To fully leverage our crash analysis tools, make sure to:
 
 ### Attributes [#attributes]
 
-Each request error sample includes a comprehensive set of attributes that provide detailed information about the request, response, and the specific parameters that triggered the error. These attributes offer valuable insights into the error's context and help in understanding the root cause.
+When you look at a specific error, each request error sample includes a comprehensive set of attributes that provide detailed information about the request, response, and the specific parameters that triggered the error. These attributes offer valuable insights into the error's context and help in understanding the root cause.
 
 <img
     title="Request errors attributes"