Remove callout about reserved account-level traits

Author: evanSegment

src/personas/audiences/account-audiences.md

@@ -35,9 +35,6 @@ A single account-level audience can incorporate any combination of the following
 - Account-level audience membership
 - Account-level custom traits (set through a [group](/docs/connections/spec/group) call)
 
-> warning ""
-> [Reserved account-level custom traits](/docs/connections/spec/group/#traits) are not available in audience conditions. You must include them in the traits dictionary a second time using a non-reserved trait name to make them available in the audience builder.
-
 The three types of user-level conditions are:
 - **Any User** (default): Returns all accounts where *at least one user* associated with the account satisfies the specified condition
 - **All users**: Returns all accounts where *all users* associated with the account satisfy the specified condition
@@ -99,4 +96,4 @@ For example, you may wish to create an audience which selects all admin-level us
 - Account-level audiences do not respect the `context.groupId` property on track calls. If users are associated with multiple accounts (through multiple group calls), the entire collection of a user’s events is considered when evaluating user-level event conditions (not just those events which are tagged with a matching `groupId`). This can lead to unexpected results where a user’s events triggered in the context of one account lead to another account incorrectly matching an account-level audience. 
 - The identity breakdown report (displayed in the audience builder for user-level audiences) is not available for account-level audiences.
 
-If you find that these limitations impede your ability to use account-level audiences, contact [[email protected]](mailto:[email protected]) with details about your use-case.
+If you find that these limitations impede your ability to use account-level audiences, contact [[email protected]](mailto:[email protected]) with details about your use-case.