ordering and links (#213)

cadence-workflow · Jan 15, 2025 · f5826e7 · f5826e7
1 parent 4b4b8f2
commit f5826e7
Show file tree

Hide file tree

Showing 19 changed files with 4 additions and 3 deletions.
diff --git a/docs/05-go-client/02.5-starting-workflows.md → docs/05-go-client/03-starting-workflows.md b/docs/05-go-client/02.5-starting-workflows.md → docs/05-go-client/03-starting-workflows.md
diff --git a/docs/05-go-client/03-activities.md → docs/05-go-client/04-activities.md b/docs/05-go-client/03-activities.md → docs/05-go-client/04-activities.md
diff --git a/docs/05-go-client/04-execute-activity.md → docs/05-go-client/05-execute-activity.md b/docs/05-go-client/04-execute-activity.md → docs/05-go-client/05-execute-activity.md
diff --git a/docs/05-go-client/05-child-workflows.md → docs/05-go-client/06-child-workflows.md b/docs/05-go-client/05-child-workflows.md → docs/05-go-client/06-child-workflows.md
diff --git a/docs/05-go-client/06-retries.md → docs/05-go-client/07-retries.md b/docs/05-go-client/06-retries.md → docs/05-go-client/07-retries.md
diff --git a/docs/05-go-client/07-error-handling.md → docs/05-go-client/08-error-handling.md b/docs/05-go-client/07-error-handling.md → docs/05-go-client/08-error-handling.md
diff --git a/docs/05-go-client/08-signals.md → docs/05-go-client/09-signals.md b/docs/05-go-client/08-signals.md → docs/05-go-client/09-signals.md
diff --git a/docs/05-go-client/09-continue-as-new.md → docs/05-go-client/10-continue-as-new.md b/docs/05-go-client/09-continue-as-new.md → docs/05-go-client/10-continue-as-new.md
diff --git a/docs/05-go-client/10-side-effect.md → docs/05-go-client/11-side-effect.md b/docs/05-go-client/10-side-effect.md → docs/05-go-client/11-side-effect.md
diff --git a/docs/05-go-client/11-queries.md → docs/05-go-client/12-queries.md b/docs/05-go-client/11-queries.md → docs/05-go-client/12-queries.md
diff --git a/...go-client/12-activity-async-completion.md → ...go-client/13-activity-async-completion.md b/...go-client/12-activity-async-completion.md → ...go-client/13-activity-async-completion.md
diff --git a/docs/05-go-client/13-workflow-testing.md → docs/05-go-client/14-workflow-testing.md b/docs/05-go-client/13-workflow-testing.md → docs/05-go-client/14-workflow-testing.md
diff --git a/docs/05-go-client/14-workflow-versioning.md → docs/05-go-client/15-workflow-versioning.md b/docs/05-go-client/14-workflow-versioning.md → docs/05-go-client/15-workflow-versioning.md
diff --git a/docs/05-go-client/15-sessions.md → docs/05-go-client/16-sessions.md b/docs/05-go-client/15-sessions.md → docs/05-go-client/16-sessions.md
diff --git a/docs/05-go-client/16-distributed-cron.md → docs/05-go-client/17-distributed-cron.md b/docs/05-go-client/16-distributed-cron.md → docs/05-go-client/17-distributed-cron.md
diff --git a/docs/05-go-client/17-tracing.md → docs/05-go-client/18-tracing.md b/docs/05-go-client/17-tracing.md → docs/05-go-client/18-tracing.md
diff --git a/...go-client/18-workflow-replay-shadowing.md → ...go-client/19-workflow-replay-shadowing.md b/...go-client/18-workflow-replay-shadowing.md → ...go-client/19-workflow-replay-shadowing.md
diff --git a/...nt/19-workflow-non-deterministic-error.md → ...nt/20-workflow-non-deterministic-error.md b/...nt/19-workflow-non-deterministic-error.md → ...nt/20-workflow-non-deterministic-error.md
@@ -1,7 +1,7 @@
 ---
 layout: default
 title: Workflow Non-deterministic errors
-permalink: /docs/go-client/workflow-non-deterministic-errors
+permalink: /docs/go-client/workflow-non-deterministic-error
 ---
 
 # Workflow Non-deterministic errors
@@ -175,4 +175,4 @@ Code changes that are free of non-deterministic erorrs normally do not involve d
 
 ### I want to check if my code change will produce non-deterministic errors, how can I debug?
 
-Cadence provides replayer test, which functions as an unit test on your local machine to replay your workflow history comparing to your potential code change. If you introduce a non-deterministic change and your history triggers it, the test should fail. Check out [this page](./18-workflow-replay-shadowing.md) for more details.
+Cadence provides replayer test, which functions as an unit test on your local machine to replay your workflow history comparing to your potential code change. If you introduce a non-deterministic change and your history triggers it, the test should fail. Check out [this page](./19-workflow-replay-shadowing.md) for more details.
diff --git a/sidebars.ts b/sidebars.ts
@@ -94,7 +94,7 @@ const sidebars: SidebarsConfig = {
         { type: 'doc', id: 'go-client/index' },
         { type: 'doc', id: 'go-client/workers' },
         { type: 'doc', id: 'go-client/create-workflows' },
-        { type: 'doc', id: 'go-client/02.5-starting-workflows' },
+        { type: 'doc', id: 'go-client/starting-workflows' },
         { type: 'doc', id: 'go-client/activities' },
         { type: 'doc', id: 'go-client/execute-activity' },
         { type: 'doc', id: 'go-client/child-workflows' },
@@ -111,6 +111,7 @@ const sidebars: SidebarsConfig = {
         { type: 'doc', id: 'go-client/distributed-cron' },
         { type: 'doc', id: 'go-client/tracing' },
         { type: 'doc', id: 'go-client/workflow-replay-shadowing' },
+        { type: 'doc', id: 'go-client/workflow-non-deterministic-error' },
       ],
     },
     {