pr review

Author: andrewjschuang

docs-v2/pages/troubleshooting.mdx

@@ -250,13 +250,13 @@ Use Pipedream's [built-in Delay actions](/workflows/flow-control/#delay) to dela
 
 Here are a few things that can help your workflow execute faster:
 
-1. **Increase Memory Allocation:** Increase your [workflow memory](/workflows/settings#memory) to at least 512 MB. Raising the memory limit will proportionally increase CPU resources, leading to improved performance and reduced latency.
+1. **Increase memory:** Increase your [workflow memory](/workflows/settings#memory) to at least 512 MB. Raising the memory limit will proportionally increase CPU resources, leading to improved performance and reduced latency.
 
-2. **Return Static HTTP Responses:** If your workflow is triggered by an HTTP source, return a [static HTTP response](/workflows/triggers#http-responses) directly from the trigger configuration. This ensures the HTTP response is sent to the caller immediately, before the rest of the workflow steps are executed.
+2. **Return static HTTP responses:** If your workflow is triggered by an HTTP source, return a [static HTTP response](/workflows/triggers#http-responses) directly from the trigger configuration. This ensures the HTTP response is sent to the caller immediately, before the rest of the workflow steps are executed.
 
-3. **Simplify Your Workflow:** Reduce the number of [steps](/workflows/steps#code-actions) and [segments](/workflows/control-flow#workflow-segments) in your workflow. This lowers the overhead involved in managing step execution and exports.
+3. **Simplify your workflow:** Reduce the number of [steps](/workflows/steps#code-actions) and [segments](/workflows/control-flow#workflow-segments) in your workflow, combining multiple steps into one, if possible. This lowers the overhead involved in managing step execution and exports.
 
-4. **Activate Warm Workers:** Use and increase the number of dedicated workers to [eliminate cold starts](/workflows/settings#eliminate-cold-starts), ensuring your workflow is ready to execute immediately.
+4. **Activate warm workers:** Use [warm workers](/workflows/settings#eliminate-cold-starts) to reduce the startup time of workflows. Set [as many warm workers](/workflows/settings#how-many-workers-should-i-configure) as you want for high-volume traffic.
 
 ### How can I save common functions as steps?
 

docs-v2/pages/workflows/settings.mdx

@@ -113,11 +113,9 @@ By default, workflows run with {process.env.MEMORY_LIMIT} of memory. If you're p
 Increasing your workflow's memory gives you a proportional increase in CPU, so increasing your workflow's memory can reduce its overall runtime and make it more performant.
 
 <Callout type="info">
-**Reducing Workflow Latency**
-
-To reduce latency from the trigger to the end of your workflow, consider increasing the memory allocation to at least 512MB. This will result in significantly better performance compared to the default 256MB.
-For other ways to improve your workflow's performance, see [Troubleshooting](/troubleshooting#how-can-my-workflow-run-faster).
+**How can my workflow run faster?**
 
+See [our guide on running workflows faster](/troubleshooting#how-can-my-workflow-run-faster).
 </Callout>
 
 **Pipedream charges credits proportional to your memory configuration**. When you modify your memory settings, Pipedream will show you the number of credits you'll be charged per execution. [Read more here](/pricing/#how-does-workflow-memory-affect-credits).

docs-v2/pages/workflows/triggers.mdx

@@ -296,10 +296,9 @@ When you're processing HTTP requests, you often don't need to issue any special
 
 
 <Callout type="info">
-**Reducing Workflow Latency**
-
-To reduce latency for HTTP requests, return a static response directly from the trigger configuration. This ensures the HTTP response is sent to the caller immediately, before the rest of the workflow steps are executed. For more information, see [Sources](https://pipedream.com/docs/sources).
+**How can my workflow run faster?**
 
+See [our guide on running workflows faster](/troubleshooting#how-can-my-workflow-run-faster).
 </Callout>
 
 #### Customizing the HTTP response