DOC-114 add references

Author: markzegarelli

src/personas/audiences/account-audiences.md

@@ -13,11 +13,11 @@ You can use account-level audiences to accomplish the following use cases:
 - Identify a set of trial accounts which would benefit from a paid plan based on their use, and flag those in your CRM application
 - Create an email list of all users in accounts showing high adoption of a specific feature to aid in recruiting for user research
 
-| Use case                                                                                                                              | Required features                                                                                                                                    | Detailed description                                                                                                                                                |
-| ------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Create a list of accounts based on account-level traits, and/or the traits and behaviors of individual users associated with accounts | 1. Account-level audiences                                                                                                                           | [Account-level audience conditions](#account-level-audience-conditions)                                                                                             |
-| Create a list of accounts based on the collective behavior of all users associated with accounts                                      | 1. Account-level computed trait or SQL trait. <br /> 2. Account-level audience (using computed trait as a condition)                                        | [Using account-level computed and SQL traits as account-level audience conditions](#use-account-level-computed-and-sql-traits-as-account-level-audience-conditions) |
-| Create a list of users based on a combination of user-level traits and events, and account-level traits                               | 1. Account-level audience (using account-level trait as a condition) 2. User-level audience (using account-level audience membership as a condition) | [Using account-level traits in user-level audiences](#use-account-level-traits-in-user-level-audiences)                                                             |
+| Use case                                                                                                                              | Required features                                                                                                                                           | Detailed description                                                                                                                                                |
+| ------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Create a list of accounts based on account-level traits, and/or the traits and behaviors of individual users associated with accounts | 1. Account-level audiences                                                                                                                                  | [Account-level audience conditions](#account-level-audience-conditions)                                                                                             |
+| Create a list of accounts based on the collective behavior of all users associated with accounts                                      | 1. Account-level computed trait or SQL trait <br /> 2. Account-level audience (using computed trait as a condition)                                         | [Using account-level computed and SQL traits as account-level audience conditions](#use-account-level-computed-and-sql-traits-as-account-level-audience-conditions) |
+| Create a list of users based on a combination of user-level traits and events, and account-level traits                               | 1. Account-level audience (using account-level trait as a condition) <br /> 2. User-level audience (using account-level audience membership as a condition) | [Using account-level traits in user-level audiences](#use-account-level-traits-in-user-level-audiences)                                                             |
 
 ## Enable account-level audiences
 

src/personas/audiences/index.md

@@ -45,6 +45,8 @@ Dynamic Property references give you more flexibility over funnel audiences. Ins
 
 If you are a B2B business, you might want to build an audience of accounts. You can use both account-level traits that you've sent through the [group](/docs/connections/spec/group) call, or user-level traits and events. For example, you might want to re-engage a list of at-risk accounts defined as companies which are on a business tier plan and where none of the users in that account have logged in recently. When incorporating user-level events or traits, you can specify `None of the users`, `Any users`, or `All users`.
 
+See [Account-level Audiences](/docs/personas/audiences/account-audiences) for more information.
+
 ![](images/1542075123519.png)
 
 ## Connecting your Audience to a Destination
@@ -55,7 +57,8 @@ Once you have previewed your audience, you can choose to connect a destination,
 
 When you create an audience, Segment starts syncing your audience to the destinations you selected. Audiences are either sent to destinations as a boolean user-property or a user-list, depending on what the destination supports. Read more about [which destinations are supported](/docs/personas/using-personas-data/#compatible-personas-destinations) in the Personas documentation.
 
-For account-level audiences, you have the option to send either a [group](/docs/connections/spec/group) call and/or [identify](/docs/connections/spec/identify) call. Group calls will send one event per account, whereas identify calls will send an identify call for each user in the account. This means that even if a user hasn't performed an event, we will still set the account-level computed trait on that user. Because most marketing tools are still based at the user level, it is often important to map this account-level trait onto each user within an account.
+For account-level audiences, you can send either a [group](/docs/connections/spec/group) call and/or [identify](/docs/connections/spec/identify) call. Group calls will send one event per account, whereas identify calls will send an identify call for each user in the account. This means that even if a user hasn't performed an event, we will still set the account-level computed trait on that user. Because most marketing tools are still based at the user level, it is often important to map this account-level trait onto each user within an account. See [Account-level Audiences](/docs/personas/audiences/account-audiences) for more information.
+
 
 ## Realtime Compute vs. Batch
 
@@ -85,7 +88,7 @@ To create a new audience:
 
 
 > warning ""
-> [Facebook Custom Audiences](/docs/connections/destinations/catalog/personas-facebook-custom-audiences/), [Marketo Lists](/docs/connections/destinations/catalog/marketo-static-lists/), and [Adwords Remarketing Lists](/docs/connections/destinations/catalog/adwords-remarketing-lists) have rate limits on how quickly we can update an audience. We sync at the highest frequency allowed by the tool, which is between 1 hour and 6 hours.
+> [Facebook Custom Audiences](/docs/connections/destinations/catalog/personas-facebook-custom-audiences/), [Marketo Lists](/docs/connections/destinations/catalog/marketo-static-lists/), and [Adwords Remarking Lists](/docs/connections/destinations/catalog/adwords-remarketing-lists) have rate limits on how quickly we can update an audience. We sync at the highest frequency allowed by the tool, which is between 1 hour and 6 hours.
 
 ## Accessing your Audiences using the Profiles API
 

src/personas/computed-traits.md

@@ -152,7 +152,8 @@ Personas sends user-level computed Traits to destinations using the [Identify ca
 
 ![](images/1525837601768.png)
 
-For account-level computed traits, you have the option to send either a [group](/docs/connections/spec/group/) call and/or [identify](/docs/connections/spec/identify/) call. Group calls will send one event per account, whereas identify calls will send an identify call for each user in the account. This means that even if a user hasn't performed an event, we will still set the account-level computed trait on that user. Because most marketing tools are still based at the user level, it is often important to map this account-level trait onto each user within an account.
+For account-level computed traits, you have the option to send either a [group](/docs/connections/spec/group/) call and/or [identify](/docs/connections/spec/identify/) call. Group calls will send one event per account, whereas identify calls will send an identify call for each user in the account. This means that even if a user hasn't performed an event, we will still set the account-level computed trait on that user. Because most marketing tools are still based at the user level, it is often important to map this account-level trait onto each user within an account. See [Account-level Audiences](/docs/personas/audiences/account-audiences) for more information.
+
 
 ## Accessing your Computed Traits using the Profiles API