[Workflows] Renaming the folder to Platform, adding subrequest limit

public/__redirects

@@ -1921,6 +1921,11 @@
 # workflows
 /workflows/reference/storage-options/ /workers/platform/storage-options/ 301
 /workflows/tutorials/ /workflows/examples 301
+/workflows/reference/changelog/ /workflows/platform/changelog/ 301
+/workflows/reference/glossary/ /workflows/platform/glossary/ 301
+/workflows/reference/limits/ /workflows/platform/limits/ 301
+/workflows/reference/pricing/ /workflows/platform/pricing/ 301
+/workflows/reference/wrangler-commands/ /workflows/platform/wrangler-commands/ 301
 
 # workers KV
 /kv/platform/environments/ /kv/reference/environments/ 301

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

@@ -29,10 +29,11 @@ Many limits are inherited from those applied to Workers scripts and as documente
 | Maximum number of [queued instances](/workflows/observability/metrics-analytics/#event-types) | 10,000 | 100,000 |
 | Retention limit for completed Workflow state | 3 days | 30 days [^2] |
 | Maximum length of a Workflow ID [^4]         | 64 characters | 64 characters |
+| Maximum number of subrequests per Workflow instance | 50/request | 1000/request |
 
 [^2]: Workflow state and logs will be retained for 3 days on the Workers Free plan and for 7 days on the Workers Paid plan.
 
-[^3]: A Workflow instance can run forever, as long as each step does not take more than the CPU time limit and the maximum number of steps per Workflow is not reached. 
+[^3]: A Workflow instance can run forever, as long as each step does not take more than the CPU time limit and the maximum number of steps per Workflow is not reached.
 
 [^4]: Match pattern: _```^[a-zA-Z0-9_][a-zA-Z0-9-_]*$```_