edits

Author: rchinn1

src/unify/identity-resolution/identity-resolution-settings.md

@@ -16,13 +16,12 @@ redirect_from:
 
 Before you connect a source to Unify, Segment recommends that you first review the default Identity settings and configure custom rules as needed. Segment applies configuration updates to all *new* data flowing through the space after you save your changes. As a result, if this is your first time setting up your Identity Graph, Segment recommends that you get started with a *Dev* space [here](/docs/unify/identity-resolution/space-setup/).
 
-> note ""
-> **NOTE:** Workspace owners and users with the Identity Admin role can edit the Identity Resolution table.
+> info ""
+> Workspace owners and users with the Identity Admin role can edit the Identity Resolution table.
 
-> note ""
-> **NOTE:** When changing an Engage Space's Identity Resolution Rules, please keep the following in mind as changes will have impacts on existing profiles :
-> Making a space's Identity Resolution Rules less restrictive by changing the [Limit](https://segment.com/docs/unify/identity-resolution/identity-resolution-settings/#limit) shouldn't cause any issues to existing or future profiles. Though making a space's Identity Resolution Rules more restrictive after profiles exist then that could have serious impacts on existing profiles that already exist outside the bounds of the more restrictive rules, such as with decreasing an identifier's Limit or changing the [Priority](https://segment.com/docs/unify/identity-resolution/identity-resolution-settings/#priority) of identifiers.
-> The recommended approach is to get started with a Dev space [here](https://segment.com/docs/unify/identity-resolution/space-setup/), test the rules with the expected data, and then create an identical Production space with those rules. When making any changes to a space's Identity Resolution Rules, make sure your team documents those changes to ensure changes don't cause breaking changes to profiles, and do not to update the Identity Resolution Rules to be more restrictive after profiles already exist outside the bounds of those new limitations. 
+> warning "Changing Identity Resolution rules"
+> Making a space's Identity Resolution rules less restrictive by changing the [limit](/docs/unify/identity-resolution/identity-resolution-settings/#limit) shouldn't cause any issues to existing or future profiles. <br><br> However, making a space's rules more restrictive might have an impact existing profiles that don't adhere to the new rules (for example, decreasing an identifier's limit or changing the [priority](/docs/unify/identity-resolution/identity-resolution-settings/#priority) of identifiers).
+> <br><br>Segment recommends to get started with a Dev space [here](https://segment.com/docs/unify/identity-resolution/space-setup/), test the rules with the expected data, and then create an identical Production space with those rules. Document any changes to a space's Identity Resolution rules, and don't update rules to be more restrictive after profiles already exist outside the bounds of those new rules. 
 
 ## ExternalIDs