clarify that non segment users will need to fork the repo

Thomas Gilbert · Thomas Gilbert · commit 15ff4f6253ff · 2023-05-31T09:28:01.000-04:00
diff --git a/templates/partners/destination-new.md b/templates/partners/destination-new.md
@@ -14,11 +14,11 @@
 >
 > The below template intends to provide a standardized structure. To submit your documentation, complete the following steps:
 >
-> 1. Clone the `segment-docs` repo locally
+> 1. Fork and clone the `segment-docs` repo locally
 > 2. Create a new branch (e.g., partner-name/destination)
 > 3. Create an `index.md` file in the following path `src/connections/destinations/catalog/{destination-slug}/index.md
 > 4. Copy the template below into your `index.md` file, and edit it to be in line with how your integration operates
-> 5. Add, commit, and push your code to the `segment-docs` repo and submit a pull request
+> 5. Add, commit, and push your code, then submit a pull request to the `segment-docs` repo
 >
 > If a section does not apply to your integration, feel free to remove. Please don’t create separate sections unless absolutely necessary. In most cases, creating a H3 (###) sub-heading under an existing section is the best option!
 >
diff --git a/templates/partners/destination-update.md b/templates/partners/destination-update.md
@@ -14,11 +14,11 @@
 >
 > The below template intends to provide a standardized structure. To submit your documentation, complete the following steps:
 >
-> 1. Clone the `segment-docs` repo locally
+> 1. Fork and clone the `segment-docs` repo locally
 > 2. Create a new branch (e.g., partner-name/destination)
 > 3. Create an `index.md` file in the following path `src/connections/destinations/catalog/{destination-slug}/index.md
 > 4. Copy the template below into your `index.md` file, and edit it to be in line with how your integration operates
-> 5. Add, commit, and push your code to the `segment-docs` repo and submit a pull request
+> 5. Add, commit, and push your code, then submit a pull request to the `segment-docs` repo
 >
 > If a section does not apply to your integration, feel free to remove. Please don’t create separate sections unless absolutely necessary. In most cases, creating a H3 (###) sub-heading under an existing section is the best option!
 >
diff --git a/templates/partners/source.md b/templates/partners/source.md
@@ -14,11 +14,11 @@
 >
 > The below template intends to provide a standardized structure. To submit your documentation, complete the following steps:
 >
-> 1. Clone the `segment-docs` repo locally
+> 1. Fork and clone the `segment-docs` repo locally
 > 2. Create a new branch (e.g., partner-name/source)
 > 3. Create an `index.md` file in the following path `src/connections/sources/catalog/cloud-apps/{source-slug}/index.md
 > 4. Copy the template below into your `index.md` file, and edit it to be in line with how your integration operates
-> 5. Add, commit, and push your code to the `segment-docs` repo and submit a pull request
+> 5. Add, commit, and push your code, then submit a pull request to the `segment-docs` repo
 >
 > If a section does not apply to your integration, feel free to remove. Please don’t create separate sections unless absolutely necessary. In most cases, creating a H3 (###) sub-heading under an existing section is the best option!
 >

Original file line number	Diff line number	Diff line change
`@@ -14,11 +14,11 @@`
`14`	`14`	`>`
`15`	`15`	`> The below template intends to provide a standardized structure. To submit your documentation, complete the following steps:`
`16`	`16`	`>`
`17`		-> 1. Clone the `segment-docs` repo locally
	`17`	+> 1. Fork and clone the `segment-docs` repo locally
`18`	`18`	`> 2. Create a new branch (e.g., partner-name/destination)`
`19`	`19`	> 3. Create an `index.md` file in the following path `src/connections/destinations/catalog/{destination-slug}/index.md
`20`	`20`	> 4. Copy the template below into your `index.md` file, and edit it to be in line with how your integration operates
`21`		-> 5. Add, commit, and push your code to the `segment-docs` repo and submit a pull request
	`21`	+> 5. Add, commit, and push your code, then submit a pull request to the `segment-docs` repo
`22`	`22`	`>`
`23`	`23`	`> If a section does not apply to your integration, feel free to remove. Please don’t create separate sections unless absolutely necessary. In most cases, creating a H3 (###) sub-heading under an existing section is the best option!`
`24`	`24`	`>`