Merge pull request #4546 from segmentio/vanand17-patch-9

Update identify.md

Author: pwseg

src/connections/spec/identify.md

@@ -164,6 +164,6 @@ Reserved traits Segment has standardized:
 | `username`    | String   | User's username. This should be unique to each user, like the usernames of Twitter or GitHub.             |
 | `website`     | String   | Website of a user       |
 
-**Note:** You might be used to some destinations recognizing special traits by slightly different names. For example, Mixpanel recognizes a `$created` trait when the user's account was first created, while Intercom recognizes the same trait as `created_at` instead.  Luckily, you don't have to worry about those inconsistencies. Just pass along `createdAt`. **Segment handles all of the destination-specific conversions for you automatically.**  Same goes for the rest of the reserved traits.
+**Note:** You might be used to some destinations recognizing special traits by slightly different names. For example, Mixpanel recognizes a `$created` trait when the user's account was first created, while Intercom recognizes the same trait as `created_at` instead. Segment attempts to handle all the destination-specific conversions for you automatically. If you need help understanding if a specific field will be converted to a destination, take a look at Segment's [open source integration code](https://github.com/segment-integrations?q=&type=all&language=&sort=){:target="_blank"}, view the destination's documentation, or [contact Segment support](https://app.segment.com/workspaces?contact=1).
 
 **You can pass these reserved traits using camelCase or snake_case**, so in JavaScript you can match the rest of your camel-case code by sending `firstName`, while in Ruby you can match your snake-case code by sending `first_name`. That way the API never seems alien to your code base. Keep in mind that not all destinations support these reserved traits, so sending these traits in camelCase and snake_case can result in two sets of traits in other destinations.