Skip to content

Commit 7263e46

Browse files
cjbellmattmikolay
andauthored
Apply suggestions from code review
Co-authored-by: Matthew Mikolay <mmikolay@knock.app>
1 parent 4f3c517 commit 7263e46

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

content/version-control/branches.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ section: Version control
1818

1919
## What are branches in Knock?
2020

21-
Branches in Knock are a way to isolate changes to your Knock resources. It's like a sandbox for your changes, allowing you to make changes to your resources without affecting the main branch, or other branches in your account.
21+
Branches in Knock are a way to isolate changes to your Knock resources. They're like sandboxes for your changes, allowing you to make changes to your resources without affecting the main branch, or other branches in your account.
2222

2323
Knock branches are conceptually similar to Git branches, and are designed to be used in a similar way as part of your development workflow with Knock. You can create a branch, make changes to your resources, and merge those changes into the main branch when you're ready. Your Knock branches can mirror your Git branches, so that you can coordinate feature changes between your application and Knock.
2424

@@ -155,10 +155,10 @@ There are a few limitations to branches in Knock:
155155
sandbox for your changes.
156156
</Accordion>
157157
<Accordion title="What channel settings are used for a branch?">
158-
Branches will always use the channel settings and configured for the `development` environment (the `main` branch).
158+
Branches will always use the channel settings configured for the `development` environment (the `main` branch).
159159
</Accordion>
160-
<Accordion title="Can I block change being made directly to my development environment?">
161-
No, you cannot yet block change being made directly to your development
160+
<Accordion title="Can I block changes being made directly to my development environment?">
161+
No, you cannot yet block changes being made directly to your development
162162
environment. However, we're considering this feature and would love to hear
163163
your use case if you'd like to see this feature. Please [get in
164164
touch](mailto:support@knock.app) and we can discuss your use case further.

0 commit comments

Comments
 (0)