Fixing REST API links

Not fixing it blocks merge.

Author: Oxyjun

src/content/docs/workflows/build/trigger-workflows.mdx

@@ -9,7 +9,7 @@ sidebar:
 You can trigger Workflows both programmatically and via the Workflows APIs, including:
 
 1. With [Workers](/workers) via HTTP requests in a `fetch` handler, or bindings from a `queue` or `scheduled` handler
-2. Using the [Workflows REST API](/api/paths/accounts-account_id--workflows/get)
+2. Using the [Workflows REST API](/api/operations/wor-list-workflows)
 2. Via the [wrangler CLI](/workers/wrangler/commands/#workflows) in your terminal
 
 ## Workers API (Bindings)
@@ -166,7 +166,7 @@ Restarting an instance will immediately cancel any in-progress steps, erase any
 
 ## REST API (HTTP)
 
-Refer to the [Workflows REST API documentation](/api/paths/accounts-account_id--workflows--workflow_name--instances/post).
+Refer to the [Workflows REST API documentation](/api/operations/wor-create-new-workflow-instance).
 
 ## Command line (CLI)
 

src/content/docs/workflows/get-started/cli-quick-start.mdx

@@ -155,7 +155,7 @@ npx wrangler@latest deploy
 
 ## 3. Run a Workflow
 
-You can run a Workflow via the `wrangler` CLI, via a Worker binding, or via the Workflows [REST API](/api/paths/accounts-account_id--workflows/get).
+You can run a Workflow via the `wrangler` CLI, via a Worker binding, or via the Workflows [REST API](/api/operations/wor-list-workflows).
 
 ### `wrangler` CLI
 

src/content/docs/workflows/get-started/guide.mdx

@@ -179,7 +179,7 @@ We have a very basic Workflow definition, but now need to provide a way to call
 1. External HTTP requests via a `fetch()` handler
 2. Messages from a [Queue](/queues/)
 3. A schedule via [Cron Trigger](/workers/configuration/cron-triggers/)
-4. Via the [Workflows REST API](/api/paths/accounts-account_id--workflows/get) or [wrangler CLI](/workers/wrangler/commands/#workflows)
+4. Via the [Workflows REST API](/api/operations/wor-list-workflows) or [wrangler CLI](/workers/wrangler/commands/#workflows)
 
 Return to the `src/index.ts` file we created in the previous step and add a `fetch` handler that _binds_ to our Workflow. This binding allows us to create new Workflow instances, fetch the status of an existing Workflow, pause and/or terminate a Workflow.