Update events-and-properties.mdx (#1703)

Clarified language for a best practice

Co-authored-by: myronkaifung <[email protected]>

pages/docs/data-structure/events-and-properties.mdx

@@ -45,7 +45,7 @@ We recommend striking the right balance when defining your events. Events should
 
 * If your goal is to track different buttons from different user journeys: instead of tracking 1 event `Button Clicked` with `Button Name` property set to **"Play"**, or **"Profile"**, or **"X"**, track them as different events `Song Played` and `Profile Updated` and `Logout` with specific properties for each event to provide richer context.
 
-### Name Events and Properties Consistently
+### Use a Naming Convention for Events and Properties
 
 <Callout type="warning">
    Mixpanel strings are case-sensitive; `sign_up_completed` and `Sign_Up_Completed` are considered two separate events.