Apply suggestions from code review

Co-authored-by: Diogo Ferreira <[email protected]>
Co-authored-by: Jun Lee <[email protected]>

Author: 3 people

src/content/docs/workflows/build/events-and-parameters.mdx

@@ -84,7 +84,7 @@ When you pass your `YourEventType` to `WorkflowEvent` as a type parameter, the `
 
 ```ts title="src/index.ts"
 // Import the Workflow definition
-import { Workflow, WorkflowEvent, WorkflowStep } from "cloudflare:workflows"
+import { WorkflowEntrypoint, WorkflowStep, WorkflowEvent} from 'cloudflare:workers';
 
 export class MyWorkflow implements Workflow {
     // Pass your type as a type parameter to WorkflowEvent

src/content/docs/workflows/build/sleeping-and-retrying.mdx

@@ -60,10 +60,10 @@ If you do not provide your own retry configuration, Workflows applies the follow
 const defaultConfig: WorkflowStepConfig = {
 	retries: {
 		limit: 5,
-		delay: 1000,
-		backoff: "constant",
+		delay: 10000,
+		backoff: 'exponential',
 	},
-	timeout: "15 minutes",
+	timeout: '10 minutes',
 };
 ```
 

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

@@ -34,7 +34,7 @@ To bind to a Workflow from your Workers code, you need to define a [binding](/wo
 ```toml title="wrangler.toml"
 name = "workflows-tutorial"
 main = "src/index.ts"
-compatibility_date = "2024-10-15"
+compatibility_date = "2024-10-22"
 
 [[workflows]]
 # The name of the Workflow
@@ -153,7 +153,7 @@ Once stopped, the Workflow instance *cannot* be resumed.
 
 :::caution
 
-**Known issue**: Restarting a Workflow via the `restart()` method is not currently supported ad will throw an exception (error).
+**Known issue**: Restarting a Workflow via the `restart()` method is not currently supported and will throw an exception (error).
 
 :::
 

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

@@ -8,7 +8,7 @@ sidebar:
 
 import { MetaInfo, Type } from "~/components";
 
-This guide details the Workflows API within Cloudflare Workers, including methods, types and usage examples.
+This guide details the Workflows API within Cloudflare Workers, including methods, types, and usage examples.
 
 ## WorkflowEntrypoint
 
@@ -101,7 +101,7 @@ Workflows currently requires you to bind to a Workflow via `wrangler.toml` and d
 
 :::
 
-Workflows exposes a API directly to your Workers scripts via the [bindings](/workers/runtime-apis/bindings/#what-is-a-binding) concept. Bindings allow you to securely call a Workflow without having to manage API keys or clients.
+Workflows exposes an API directly to your Workers scripts via the [bindings](/workers/runtime-apis/bindings/#what-is-a-binding) concept. Bindings allow you to securely call a Workflow without having to manage API keys or clients.
 
 You can bind to a Workflow by defining a `[[workflows]]` binding within your `wrangler.toml` configuration.
 
@@ -133,7 +133,7 @@ Ensure you have `@cloudflare/workers-types` version `4.20241022.0` or later inst
 
 :::
 
-The `Workflow` type provides methods that allow you to create, inspect the status and manage running Workflow instances from within a Worker script.
+The `Workflow` type provides methods that allow you to create, inspect the status, and manage running Workflow instances from within a Worker script.
 
 ```ts
 interface Env {
@@ -230,7 +230,7 @@ Return the id of a Workflow.
 
 ### status
 
-Pause a running Workflow instance.
+Return the status of a running Workflow instance.
 
 * <code>status(): Promise&lt;void&gt;</code>
 

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

@@ -147,7 +147,7 @@ You can edit this Workflow by adding (or removing) additional `step` calls, chan
 
 ## 2. Deploy a Workflow
 
-Workflows are deployed via [`wrangler`](/workers/wrangler/install-and-update/), which is installed when you first ran `npm create cloudflare`, above. Workflows are Worker scripts, and are deployed the same way:
+Workflows are deployed via [`wrangler`](/workers/wrangler/install-and-update/), which is installed when you first ran `npm create cloudflare` above. Workflows are Worker scripts, and are deployed the same way:
 
 ```sh
 npx wrangler@latest deploy
@@ -195,7 +195,7 @@ For example, the following Worker will fetch the status of an existing Workflow
 
 ```ts title="src/index.ts"
 // Import the Workflow definition
-import { WorkflowEntrypoint, WorkflowEvent, WorkflowStep } from "cloudflare:workflows"
+import { WorkflowEntrypoint, WorkflowStep, WorkflowEvent} from 'cloudflare:workers';
 
 interface Env {
   // Matches the binding definition in your wrangler.toml

src/content/docs/workflows/observability/metrics-analytics.mdx

@@ -25,11 +25,11 @@ Metrics can be queried (and are retained) for the past 31 days.
 The `workflowsAdaptiveGroups` dataset provides the following dimensions for filtering and grouping query results:
 
 * `workflowName` - Workflow name - e.g. `my-workflow`
-* `instanceId` - Instance ID.
+* `instanceId` - Instance ID
 * `stepName` - Step name
 * `eventType` - Event type (see [event types](#event-types))
 * `stepCount` - Step number within a given instance
-* `date` - The date when trigger was triggered
+* `date` - The date when the Workflow was triggered
 * `datetimeFifteenMinutes` - The date and time truncated to fifteen minutes
 * `datetimeFiveMinutes` - The date and time truncated to five minutes
 * `datetimeHour` - The date and time truncated to the hour

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

@@ -1,7 +1,7 @@
 ---
 pcx_content_type: navigation
 title: Workflows REST API
-external_link: /api/operations/cloudflare-d1-create-database
+external_link: /api/paths/accounts-account_id--workflows/get
 sidebar:
   order: 10