wording

Author: charlypoly

troubleshooting/executions-not-processing.mdx

@@ -38,7 +38,7 @@ Otherwise, we won't be able to process your executions.
     Each account gets a maximum limit applied across all applications and environments:
 
     - Free plan: `2` concurrent executions
-    - Pro plan: `10` concurrent executions (or custom)
+    - Growth plan: `10` concurrent executions (or custom)
 
     Check all your applications and environments for running executions; if no executions are running, please refer to the next step.
 
@@ -48,7 +48,7 @@ Otherwise, we won't be able to process your executions.
 
     Workflows, especially on the Free plan -- with a concurrency limit of `2`, can lead to a _deadlock_ situation when a parent execution is waiting on a stuck child execution, exhausting the concurrency limit.
 
-    To resolve such an issue, wait for the child execution to timeout (30min) and consider upgrading to a Pro plan, which is better suited for workflows.
+    To resolve such an issue, wait for the child execution to timeout (30min) and consider upgrading to a Growth plan, which is better suited for workflows.
 
     </Accordion>
 

troubleshooting/executions-stuck.mdx

@@ -37,7 +37,7 @@ sidebarTitle: "Executions are stuck"
 
     To resolve such an issue, wait for the child execution to timeout (default: 30min) or cancel it from the Console.
 
-    Please consider upgrading to a Pro plan, which is better suited for workflows.
+    Please consider upgrading to a Growth plan, which is better suited for workflows.
 
     </Accordion>