Minor rewording

Author: pwseg

src/engage/faqs.md

@@ -142,6 +142,6 @@ Multiple audience events can trigger for a user if any of the following conditio
 3) The user has [multiple identifiers of the same type](/docs/engage/using-engage-data/#multiple-identifiers-of-the-same-type). Segment sends one event per identifier for each audience or computed trait event.
 4) The `include anonymous users` option is selected for an audience. Segment sends an event for every `anonymousId` on the user profile.
 
-## Why am I not seeing the standard source events on the Engage source, even though it has been connected through "Unify -> Unify Settings -> Profile Sources" page?
+## Why am I not seeing standard source events on the Engage source, even though it has been connected through "Unify -> Unify Settings -> Profile Sources" page?
 
-Based on Engage behavior, standard source events such as page,track and identify calls are not directly visible on the Engage source. The Engage source is specifically designed to track and manage events related to audiences and computed traits within the Engage space. This includes events generated by changes in audience membership or computed trait calculations, or when a user profile has been created in the Engage space. These are distinct from the typical page calls, track calls, or identify calls (user interaction events) that you would observe in a standard Segment source.
+Based on Engage behavior, standard source events such as Page, Track and Identify calls aren't visible on the Engage source. The Engage source tracks and manages events related to audiences and computed traits within the Engage space. This includes events generated by changes in audience membership or computed trait calculations or when a user profile has been created in the Engage space. These are distinct from the typical Page calls, Track calls, or Identify calls (user interaction events) that you would observe in a standard Segment source.