[Workflows] Renaming the folder to Platform, adding subrequest limit (#24149)

* Renaming the folder to Platform, adding subrequest limit

* Updating internal links

* Reverting folder rename

Author: Oxyjun

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

@@ -224,7 +224,7 @@ Ensure you have a compatibility date `2024-10-22` or later installed when bindin
 
 The `Workflow` type provides methods that allow you to create, inspect the status, and manage running Workflow instances from within a Worker script.
 It is part of the generated types produced by [`wrangler types`](/workers/wrangler/commands/#types).
- 
+
 ```ts title="./worker-configuration.d.ts"
 interface Env {
   // The 'MY_WORKFLOW' variable should match the "binding" value set in the Wrangler config file

src/content/docs/workflows/reference/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-_]*$```_