Clarify refresh cadence and other cleanup

Author: rchinn1

src/engage/audiences/computed-traits.md

@@ -171,7 +171,7 @@ To edit a real-time Trait, follow these steps:
 
 Engage then processes your Trait edits. While the edit task runs, the trait remains locked and you can't make further changes. Once Engage has finished incorporating your changes, you'll be able to access your updated Trait.
 
-You can use the Overview page to view trait details and current [compute status](/docs/engage/audiences/#compute-statuses). For real-time traits, click **Refresh Trait** to see the current number of users with the trait.  
+Use the Overview page to view trait details and current [compute status](/docs/engage/audiences/#compute-statuses). For real-time traits, click **Refresh Trait** to see the current number of users with the trait.  
 
 ## Accessing your Computed Traits using the Profiles API
 

src/engage/audiences/index.md

@@ -88,20 +88,20 @@ Because a number of factors (like system load, backfills, or user bases) determi
 
 As a result, **Segment recommends waiting at least 24 hours for an Audience to finish computing** before you resume working with the Audience.
 
-From the Audience Overview page, you can view Audience details including the current compute status and progress bar for real-time and batch Audiences.
+From the Overview page, you can view Audience details including the current compute status and a progress bar for real-time and batch Audiences. Engage updates the progress bar and status for real-time computations approximately every 10 minutes.
 
 > info ""
-> Engage only displays a progress bar when you're creating new Audiences or Traits.
+> Engage only displays the progress bar when you create new Audiences or Traits.
 
 ### Refresh real-time Audiences and Traits
 
-For real-time Audiences and Traits, click **Refresh Audience** or **Refresh Trait** to update user counts, status, and compute progress. Engage refreshes real-time Audiences and Traits approximately every 10 minutes.
+For real-time computations, you can click **Refresh Audience** or **Refresh Trait** to update user counts, status, and compute progress.
 
 ### Compute statuses
 
 Engage displays the following compute statuses for Audiences and Traits.
 
-#### Real-time Audience or Trait
+#### Real-time computations
 
 | Computation status        | Description                           |
 |---------------------------|---------------------------------------|
@@ -112,17 +112,13 @@ Engage displays the following compute statuses for Audiences and Traits.
 | Failed                    | The computation was cancelled or failed to compute. Please contact [Segment support](https://segment.com/help/contact/){:target="_blank"}.      |
 
 
-#### Batch Audience or Trait
-
-> info ""
-> Engage updates batch Audiences and Traits approximately once every hour.
-
+#### Batch computations
 
 | Computation status        | Description                           |
 |---------------------------|---------------------------------------|
 | Preparing                 | Engage is preparing the batch computation. |
 | Computing                 | Engage is computing the batch Audience or Trait.  |
-| Live                      | The batch computation is up-to-date with the most recent data, based on the most recent sync cadence.        |
+| Live                      | The batch computation is up-to-date with the most recent data, based on the most recent sync cadence. Engage updates batch Audiences and Traits approximately once every hour.        |
 | Not Computing             | Engage displays this status when there are no destinations connected and `Compute without connected destinations` isn't selected. |
 | Disabled                  | The batch Audience or Trait is disabled. |
 | Failed                    | The batch computation was cancelled or failed to compute. Please contact [Segment support](https://segment.com/help/contact/){:target="_blank"}.      |
@@ -148,7 +144,7 @@ To create a new Audience:
 
 3. To preview your Audience, select **Select Destinations**, then select **Review & Create**.
 
-   By default, Segment queries all historical data to set the current value of the computed trait and Audience. Backfill computes historical data up to the point of audience creation. After audience creation, Segment computes traits and audiences in real-time. You can uncheck **Include Historical Data** to compute values for the Audience or trait without historical data. With backfill disabled, the trait or Audience only uses the data that arrives after you create it.
+   By default, Segment queries all historical data to set the current value of the computed trait and Audience. Backfill computes historical data up to the point of audience creation. You can uncheck **Include Historical Data** to compute values for the Audience or trait without historical data. With backfill disabled, the trait or Audience only uses the data that arrives after you create it.
 
 Use the Audience Explorer to see users or accounts that enter the Audience. Segment displays the Audience as computing until at least one user or account enters.
 
@@ -167,7 +163,7 @@ To edit a realtime Trait or Audience, follow these steps:
 3. Select the **Builder** tab and make your edits.
 4. Select **Save Audience** to confirm your edits.
 
-Engage then processes your realtime Audience or Trait edits. While the edit task runs, the audience remains locked and you can't make further changes. Once Engage incorporates your changes, you'll be able to access your updated Audience or Trait. You can use the Overview page to view user details, refresh real-time Audiences, and view the current [compute status](#compute-statuses).
+Engage then processes your realtime Audience or Trait edits. While the edit task runs, the audience remains locked and you can't make further changes. Once Engage incorporates your changes, you'll be able to access your updated Audience or Trait. Use the Overview page to view the current [compute status](#compute-statuses) and Audience details, and refresh real-time computations.
 
 > warning ""
 > If your audience includes historical data (Historical Backfill is enabled), editing an audience creates a new backfill task. The backfill task, and therefore the edit task, take longer to process if the audience is connected to a destination with rate limits. Rate-limited destinations dictate how fast Engage can backfill. View a list of [rate-limited destinations](/docs/engage/using-engage-data/#rate-limits-on-engage-event-destinations).