Merge pull request #4768 from segmentio/thomas/sources

new section on event naming conventions

Author: rchinn1

src/partners/sources.md

@@ -12,7 +12,7 @@ Before you begin, you need access to the Developer Portal. To access the Develop
 2. Once approved, you'll receive an invitation to join the Segment Developer Portal.
 3. Log in to Segment, navigate to the User dropdown in the top right of the screen, and click [**Developer Portal**](https://app.segment.com/dev-portal){:target="_blank"}.
 
-## Build the Source
+## Build the source
 
 1. Once in the Developer Portal, navigate to **Integrations** and click **Build integration** > **Build a source**
 
@@ -34,7 +34,26 @@ Building your source will require defining the event data that you send to Segme
 
 If you break the spec, you are breaking the promise of Segment, which is grounds for removal from the catalog. To learn about the semantics of the five supported API calls, and the semantic event names and properties Segment recognizes, read the [Segment Spec](/docs/connections/spec).
 
-Within the Spec, there are a few requirements for partner Streams worth pointing out. 
+Within the Spec, there are a few requirements for partner Streams worth pointing out.
+
+### Naming conventions
+
+When you're creating events and the properties associated with them, you want to be crystal clear about the casing. This might seem nitpicky, but it's imperative in the long run. Segment recommends `Proper Case` for event names, and `snake_case` for properties. If you have platform-specific requirements that necessitate the use of different casing, it is permissible.
+
+Here are the five most common options:
+
+- `all lowercase` — account created
+
+- `snake_case` — account_created
+
+- `Proper Case` — Account Created
+
+- `camelCase` — accountCreated
+
+- `Sentence case` — Account created
+
+You can read more about Segment's recommended naming conventions [here](https://segment.com/academy/collecting-data/naming-conventions-for-clean-data/){:target="_blank"}.
+
 
 ### `userId`
 
@@ -91,7 +110,7 @@ Segment offers customers the option to lead on data residency by providing [regi
 - Oregon (US Default) — `api.segment.io/v1`
 - Dublin — `events.eu1.segmentapis.com/`
 
-## Test your Source
+## Test your source
 
 1. From your source's page in the Developer Portal, navigate to **Settings** > **Add to workspace**. From the dropdown, select the Segment workspace you'll use to test your source, and click **Add to workspace**. The selected workspace will open in a new tab.