Skip to content

Commit cf03863

Browse files
committed
Update headers and change "we" to "Segment"
1 parent 72d02f4 commit cf03863

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

src/partners/sources.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Before you begin, you need access to the Developer Portal. To access the Develop
1212
2. Once approved, you'll receive an invitation to join the Segment Developer Portal.
1313
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"}.
1414

15-
## Build the Source
15+
## Build the source
1616

1717
1. Once in the Developer Portal, navigate to **Integrations** and click **Build integration** > **Build a source**
1818

@@ -36,9 +36,9 @@ If you break the spec, you are breaking the promise of Segment, which is grounds
3636

3737
Within the Spec, there are a few requirements for partner Streams worth pointing out.
3838

39-
### Naming Conventions
39+
### Naming conventions
4040

41-
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. We recommend `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.
41+
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.
4242

4343
Here are the five most common options:
4444

@@ -110,7 +110,7 @@ Segment offers customers the option to lead on data residency by providing [regi
110110
- Oregon (US Default) — `api.segment.io/v1`
111111
- Dublin — `events.eu1.segmentapis.com/`
112112

113-
## Test your Source
113+
## Test your source
114114

115115
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.
116116

0 commit comments

Comments
 (0)