Merge pull request #707 from pavel-synek/main

Fix wrong wording (Snowflake vs. Python)

components/branches/index.md

@@ -81,8 +81,7 @@ You can end your branch's lifecycle in two ways:
 - **Deleting** -- if you do not wish to use the changes you've made and want to simply discard them. The data associated with the branch is discarded when the branch is deleted.
 - [**Merging into production**](/tutorial/branches/merge-to-production/) -- all changes in the configurations are brought back to the respective production configurations. All the changes are applied at once (after you approve them) and produce new [versions](/components/#configuration-versions) of the respective configurations. The branch can be either deleted or kept for further reference after merging. 
 
-**Important:** All this happens in a same project, allowing you to collaborate on the modifications with other members 
-of the project.
+***Important:** All of this happens within the same project, enabling collaboration with other project members on the modifications.*
 
 ## Component Considerations
 
@@ -99,3 +98,7 @@ write to the destination, or change the destination accordingly.
 ### OAuth Authorized Components
 
 Components using OAuth does not allow authorizing nor changing the OAuth in development branch. The OAuth authorization tokens are shared with production so changing them might break the production pipeline.
+
+*****
+
+***Important:** Development branches are for development and testing only, so setting up status notifications on Flows is not supported.*

orchestrator/notifications/index.md

@@ -27,7 +27,7 @@ enabling [*Continue on error*](/orchestrator/running/) for the given tasks).
 for 100 minutes but it is still not finished after 120 minutes, a notification will be sent. The *usual* run length is computed as 
 a running average of the last 20 executions of the orchestration.
 
-When an orchestration is triggered manually, only the user who triggered it will receive any notifications. Therefore you
+When an orchestration is triggered manually, only the user who triggered it will receive any notifications. You
 don't have to worry about spamming your colleagues with messages when running orchestrations manually.
 
-**Important: Always set notifications for an error status in scheduled production orchestrations.**
+***Important:** Notifications are not supported in development branches. Always set error status notifications for scheduled production orchestrations.*

transformations/python-plain/index.md

@@ -82,7 +82,7 @@ it immediately. The following two examples show two ways of reading and manipula
 
 ## Dynamic Backends
 If you have a large amount of data in databases and complex queries, your transformation might run for a couple of hours.
-To speed it up, you can change the backend size in the configuration. Snowflake transformations suport the following sizes:
+To speed it up, you can change the backend size in the configuration. Python transformations suport the following sizes:
 - XSmall
 - Small _(default)_
 - Medium