Update audit-trail.md

grammar

Author: cmastr

src/segment-app/iam/audit-trail.md

@@ -110,10 +110,10 @@ When you forward audit events to a source, Segment passes those events through i
 An audience/computed trait Run or a Sync may fail on its first attempt, but Engage will retry up to 5 times before considering it a hard failure and display on that audience/compute trait's Overview page. As long as the runs/syncs within the specific Audience's Overview page say they are successful, then these can be safely ignored. 
 
 **How things work internally:**
-Our Engage scheduler fetches audiences/traits from compute service and then handles the logic of generating tasks. These compute/sync tasks get scheduled and executed by another worker. Essentially, these tasks are a list of steps to be executed. Each task has a series of steps which is marked as complete by saving a timestamp for the completion. If the worker be disrupted, it picks up at the latest step which has no completed_at timestamp. In some cases, the step might fail or the entire task (for example, due to timeout or the worker disruption as there are many moving parts) - in either case, these failures will be retried. 
+Segment Engage scheduler fetches audiences/traits from compute service and then handles the logic of generating tasks. These compute/sync tasks get scheduled and executed by another worker. Essentially, these tasks are a list of steps to be executed. Each task has a series of steps that are marked as complete by saving a timestamp for the completion. If the worker is disrupted, it picks up at the latest step, which has no completed_at timestamp. In some cases, the step may fail or the entire task may fail (for example, due to timeout or the worker disruption as there are many moving parts). In either case, these failures will be retried.
 
-These tasks are a part of internal Segment process, and there are systems in place which would retry failed tasks. In most cases, it is usually not necessary to track these failures, as long as there are no actual computation or sync failures. 
+These tasks are a part of internal Segment process, and there are systems in place to retry failed tasks. In most cases, it is not necessary to track these failures, as long as there are no actual computation or sync failures.
 
-The Audit Trail logic, however, is configured in the way that it simply notifies about every task failure, even if it then later succeeds.
+The Audit Trail logic, however, is configured to notify you about every task failure, even if it then later succeeds.
 
-If your team would like to avoid receiving the notifications for transient failures, please **[reach out to support](https://segment.com/help/contact/)**, who upon request can enable a setting that will reduce the number of notifications your workspace receives.
+If you would like to avoid receiving the notifications for transient failures, **[reach out to support](https://segment.com/help/contact/)**, to request enabling a setting to reduce the number of notifications your workspace receives.