Fix link (#378)

temporalio · Jan 6, 2025 · 66ce0f6 · 66ce0f6
1 parent 8841c9f
commit 66ce0f6
Show file tree

Hide file tree

Showing 5 changed files with 5 additions and 5 deletions.
diff --git a/batch-sliding-window/README.md b/batch-sliding-window/README.md
@@ -14,7 +14,7 @@ To support larger window size and overall throughput multiple instances of Slidi
 
 #### Running the Sliding Window Batch Sample
 
-Make sure the [Temporal Server is running locally](https://docs.temporal.io/application-development/foundations#run-a-development-cluster).
+Make sure the [Temporal Server is running locally](https://learn.temporal.io/getting_started/go/dev_environment/#set-up-a-local-temporal-service-for-development-with-temporal-cli).
 
 From the root of the project, start a Worker:
 

diff --git a/branch/README.md b/branch/README.md
@@ -1,6 +1,6 @@
 ## Parallel Activities
 <!-- @@@SNIPSTART samples-go-branch-readme -->
-Make sure the [Temporal Server is running locally](https://docs.temporal.io/application-development/foundations#run-a-development-cluster).
+Make sure the [Temporal Server is running locally](https://learn.temporal.io/getting_started/go/dev_environment/#set-up-a-local-temporal-service-for-development-with-temporal-cli).
 
 From the root of the project, start a Worker:
 

diff --git a/cancellation/README.md b/cancellation/README.md
@@ -1,6 +1,6 @@
 ## Cancellation
 <!-- @@@SNIPSTART samples-go-cancellation-readme -->
-Make sure the [Temporal Server is running locally](https://docs.temporal.io/application-development/foundations#run-a-development-cluster).
+Make sure the [Temporal Server is running locally](https://learn.temporal.io/getting_started/go/dev_environment/#set-up-a-local-temporal-service-for-development-with-temporal-cli).
 
 From the root of the project, start a Worker:
 

diff --git a/child-workflow-continue-as-new/README.md b/child-workflow-continue-as-new/README.md
@@ -6,7 +6,7 @@ Parent Workflow Executions receive a notification that a Child Workflow Executio
 This feature is very useful when there is a need to process a large set of data.
 The Child Execution can iterate over the data set, calling Continue-As-New periodically without polluting the parents' history.
 
-Make sure the [Temporal Server is running locally](https://docs.temporal.io/application-development/foundations#run-a-development-cluster).
+Make sure the [Temporal Server is running locally](https://learn.temporal.io/getting_started/go/dev_environment/#set-up-a-local-temporal-service-for-development-with-temporal-cli).
 
 Start the Worker:
 

diff --git a/child-workflow/README.md b/child-workflow/README.md
@@ -1,6 +1,6 @@
 ## Child Workflow
 <!-- @@@SNIPSTART samples-go-child-workflow-example-readme -->
-Make sure the [Temporal Server is running locally](https://docs.temporal.io/application-development/foundations#run-a-development-cluster).
+Make sure the [Temporal Server is running locally](https://learn.temporal.io/getting_started/go/dev_environment/#set-up-a-local-temporal-service-for-development-with-temporal-cli).
 
 From the root of the project, start a Worker: