Move added note to previous section

Author: bobbyatsegment

src/engage/using-engage-data.md

@@ -119,6 +119,9 @@ Engage only sends events to the destination if the computed trait value has chan
 }
 ```
 
+> note ""
+> **Note**: Email as an identifier is set in `traits.email` for identify calls, and `context.traits.email` for track calls. 
+
 ## Additional identifiers
 
 Engage has a flexible identity resolution layer that allows you to build user profiles based on multiple identifiers like `user_id`, `email`, or `mobile advertisingId`. However, different destinations may require different keys, so they can do their own matching and identification. For example, Zendesk requires that you include the `name` property.
@@ -129,9 +132,6 @@ If you send events to a destination that requires specific enrichment Segment do
 > note ""
 > **Note**: Profiles with multiple identifiers (for example, `user_id` and `email`) will trigger one API call per identifier when the audience or computed trait is first synced to a destination.
 
-> note ""
-> **Note**: Email as an identifier is set in `traits.email` for identify calls, and `context.traits.email` for track calls. 
-
 ## Multiple identifiers of the same type
 
 You might also see that profiles that have multiple values for the same `external_id` type, for example a profile might have multiple email addresses. When this happens, Engage sends one event per email for each audience or computed trait event. This ensures that all downstream email-based profiles receive the complete audience or computed trait.