Apply suggestions from code review

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

Author: elithrar

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

@@ -151,7 +151,9 @@ Once stopped, the Workflow instance *cannot* be resumed.
 
 ### Restart a Workflow
 
-You can restart a Workflow instance by calling `restart` against a specific instance ID.
+:::caution
+
+**Known issue**: Restarting a Workflow via the `restart()` method is not currently supported ad will throw an exception (error).
 
 ```ts
 let instance = await env.MY_WORKFLOW.get("abc-123")

src/content/docs/workflows/examples/index.mdx

@@ -7,6 +7,8 @@ sidebar:
   order: 6
   group:
     hideIndex: true
+  group:
+    hideIndex: true
 
 ---
 

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

@@ -5,6 +5,8 @@ sidebar:
   order: 1
   group:
     hideIndex: true
+  group:
+    hideIndex: true
 
 ---
 

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

@@ -34,7 +34,7 @@ You can optionally select a time window to query. This defaults to the last 24 h
 
 You can programmatically query analytics for your Workflows via the [GraphQL Analytics API](/analytics/graphql-api/). This API queries the same datasets as the Cloudflare dashboard, and supports GraphQL [introspection](/analytics/graphql-api/features/discovery/introspection/).
 
-Workflows GraphQL datasets require an `accountTag` filter with your Cloudflare account ID and includes the `workflowsAdaptive`  and `workflowsAdaptiveGroups` datasets.
+Workflows GraphQL datasets require an `accountTag` filter with your Cloudflare account ID, and includes the `workflowsAdaptive`  and `workflowsAdaptiveGroups` datasets.
 
 ### Examples
 

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

@@ -8,7 +8,7 @@ sidebar:
 
 import { Render } from "~/components"
 
-Limits that apply to authoring, deploying and running Workflows are detailed below. 
+Limits that apply to authoring, deploying, and running Workflows are detailed below.
 
 Many limits are inherited from those applied to Workers scripts and as documented in the [Workers limits](/workers/platform/limits/) documentation.
 
@@ -26,7 +26,7 @@ Many limits are inherited from those applied to Workers scripts and as documente
 | Concurrent Workflow instances (executions) | 25 | 1,000 [^1] |
 | Retention limit for completed Workflow state | 3 days | 30 days [^2] |
 
-<beta>beta</beta> This limit will be reviewed and revised during the open beta for Workflows, and we'll update this page and our changelog.
+[^1]: This limit will be reviewed and revised during the open beta for Workflows, and we'll update this page and our changelog.
 
 [^2]: Workflow state and logs will be retained for 3 days on the Workers Free plan and 30 days on the Workers Paid plan.
 

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

@@ -21,7 +21,7 @@ Workflows pricing is identical to [Workers Standard pricing](/workers/platform/p
 * **CPU time**: the total amount of compute (measured in milliseconds) consumed by a given Workflow.
 * **Requests** (invocations): the number of Workflow invocations. [Subrequests](/workers/platform/limits/#subrequests) made from a Workflow do not incur additional request costs.
 
-A Workflow that is waiting on a response to an API call, paused as a result of calling `step.sleep`, or otherwise idle does not incur CPU time.
+A Workflow that is waiting on a response to an API call, paused as a result of calling `step.sleep`, or otherwise idle, does not incur CPU time.
 
 ## Frequently Asked Questions