Skip to content

Commit fe72f8c

Browse files
committed
Update with feedback
1 parent 40e656a commit fe72f8c

File tree

5 files changed

+7
-7
lines changed

5 files changed

+7
-7
lines changed

src/partners/index.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Customers discover your Sources and Destinations using the Connections Catalog a
2323
The development process is simple:
2424

2525
1. Understand Segment's [Conceptual Model](/docs/partners/conceptual-model) and [Spec](https://segment.com/docs/connections/spec).
26-
2. Review Segment's security guidance.
26+
2. Follow Segment's security guidance.
2727
3. Request [access to the Segment Developer Center](https://segment.com/partners/developer-center/).
2828
4. Create an App.
2929
5. Build and test your Component(s).
@@ -35,12 +35,12 @@ The development process is simple:
3535

3636
It's important to understand Segment's [Conceptual Model](/docs/partners/conceptual-model) to begin planning your integration. This will help you understand how data will flow from or into your integration.
3737

38-
### 2. Review Segment's security guidance
38+
### 2. Follow Segment's security guidance
3939

4040
Security is a priority for us at Segment for both our customers and our partners. Before you start building on the Developer Center, please review our [Acceptable Use Policy](https://segment.com/legal/acceptable-use-policy/) and ensure you're following the below guidance:
4141

4242
- Follow a secure software-development lifecycle, which enables you to create code that is safe for Segment customers and their end users, and that enables you to maintain and raise the security of that code over time
43-
- If you or your code come into contact with Segment customer or end-user data for any reason, protect it with commercially reasonable methods throughout its data lifecycle: creation, handling, transporting, storing and destruction
43+
- If you or your code come into contact with Segment customer or end-user data for any reason, protect it with commercially reasonable security methods throughout its data lifecycle: creation, handling, transporting, storing and destruction
4444
- If you suspect a security event, incident or breach while working on this project or afterward, contact [Segment Security](mailto:[email protected]?subject=Developer%20Center%20Security) for assistance with your investigation and communications
4545
- Practice modern and common-sense security for any scenario not explicitly stated
4646

src/partners/plugins.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ SDK Plugins are an appropriate component for your App if your source or destinat
1717
Review the steps outlined in the [Developer Center Overview](/docs/partners). This document outlines specific details for Step 4 as it relates to building a plugin.
1818

1919
1. Understand Segment's [Conceptual Model](/docs/partners/conceptual-model) and [Spec](https://segment.com/docs/connections/spec).
20-
2. Review Segment's security guidance.
20+
2. Follow Segment's security guidance.
2121
3. Request [access to the Segment Developer Center](https://segment.com/partners/developer-center/).
2222
4. Create an App.
2323
5. Build and test your Component(s).

src/partners/subscriptions/build-functions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ Subscription Functions allow you to write custom JavaScript code that sends Segm
1010
Review the steps outlined in the [Developer Center Overview](/docs/partners). This document outlines specific details for Step 4 as it relates to building a Subscription Function.
1111

1212
1. Understand Segment's [Conceptual Model](/docs/partners/conceptual-model) and [Spec](https://segment.com/docs/connections/spec).
13-
2. Review Segment's security guidance.
13+
2. Follow Segment's security guidance.
1414
3. Request [access to the Segment Developer Center](https://segment.com/partners/developer-center/).
1515
4. Create an App.
1616
5. Build and test your Component(s).

src/partners/subscriptions/build-webhook.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ Subscription Webhooks allow Segment Partners to ingest Segment Event Data using
1010
Review the steps outlined in the [Developer Center Overview](/docs/partners). This document outlines specific details for Step 4 as it relates to building a Subscription Webhook.
1111

1212
1. Understand Segment's [Conceptual Model](/docs/partners/conceptual-model) and [Spec](https://segment.com/docs/connections/spec).
13-
2. Review Segment's security guidance.
13+
2. Follow Segment's security guidance.
1414
3. Request [access to the Segment Developer Center](https://segment.com/partners/developer-center/).
1515
4. Create an App.
1616
5. Build and test your Component(s).

src/partners/subscriptions/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ A Subscription gives you complete control over how you want to store, transform
1111
Review the steps outlined in the [Developer Center Overview](/docs/partners). This document outlines specific details for Step 4 as it relates to building a subscription.
1212

1313
1. Understand Segment's [Conceptual Model](/docs/partners/conceptual-model) and [Spec](https://segment.com/docs/connections/spec).
14-
2. Review Segment's security guidance.
14+
2. Follow Segment's security guidance.
1515
3. Request [access to the Segment Developer Center](https://segment.com/partners/developer-center/).
1616
4. Create an App.
1717
5. Build and test your Component(s).

0 commit comments

Comments
 (0)