added info that step sleep do not count towards steps limit.

Author: bruxodasilva

src/content/docs/workflows/build/workers-api.mdx

@@ -69,6 +69,12 @@ Refer to the [events and parameters](/workflows/build/events-and-parameters/) do
   * `name` - the name of the step.
   * `timestamp` - a JavaScript `Date` object or seconds from the Unix epoch to sleep the Workflow instance until.
 
+:::note
+
+`step.sleep` and `step.sleepUntil` methods do not count towards the maximum Workflow steps limit. More information is available [here](/workflows/reference/limits/) regarding the limits imposed to Workflow.
+
+:::
+
 ## WorkflowStepConfig
 
 ```ts

src/content/docs/workflows/reference/limits.mdx

@@ -21,7 +21,7 @@ Many limits are inherited from those applied to Workers scripts and as documente
 | Maximum persisted state per step          | 1MiB (2^20 bytes) | 1MiB (2^20 bytes) |
 | Maximum state that can be persisted per Workflow instance | 100MB | 1GB |
 | Maximum `step.sleep` duration             | 365 days (1 year) [^1] | 365 days (1 year) [^1] |
-| Maximum steps per Workflow                | 512 [^1] | 512 [^1] |
+| Maximum steps per Workflow [^5]           | 512 [^1] | 512 [^1] |
 | Maximum Workflow executions               | 100,000 per day [shared with Workers daily limit](/workers/platform/limits/#worker-limits) | Unlimited |
 | Concurrent Workflow instances (executions)   | 25 | 100 [^1] |
 | Retention limit for completed Workflow state | 3 days | 30 days [^2] |
@@ -35,4 +35,6 @@ Many limits are inherited from those applied to Workers scripts and as documente
 
 [^4]: Match pattern: _```^[a-zA-Z0-9_][a-zA-Z0-9-_]*$```_
 
+[^5]: `step.sleep` do not count towards the max. steps limit
+
 <Render file="limits_increase" product="workers" />