fix broken ref

Signed-off-by: nikki everett <[email protected]>
flyteorg · Nov 20, 2023 · b028b5d · b028b5d
1 parent e1722a1
commit b028b5d
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 2 deletions.
diff --git a/docs/getting_started/running_workflows_locally.md b/docs/getting_started/running_workflows_locally.md
@@ -18,6 +18,8 @@ jupytext:
 
 ### Steps (with example)
 
+(getting_started_running_workflow_local_cluster)=
+
 ## Running a workflow in a local cluster
 
 [TK - Intro - why run in a local cluster]

diff --git a/examples/advanced_composition/advanced_composition/waiting_for_external_inputs.py b/examples/advanced_composition/advanced_composition/waiting_for_external_inputs.py
@@ -234,7 +234,7 @@ def conditional_wf(data: typing.List[float]) -> dict:
 # ## Sending inputs to `wait_for_input` and `approve` nodes
 #
 # Assuming that you've registered the above workflows on a Flyte cluster that's
-# been started with {ref}`flytectl demo start <getting_started_running_workflows_locally>`,
+# been started with {ref}`flytectl demo start <getting_started_running_workflow_local_cluster>`,
 # there are two ways of using `wait_for_input` and `approve` nodes:
 #
 # ### Using the Flyte UI

diff --git a/examples/productionizing/productionizing/use_secrets.py b/examples/productionizing/productionizing/use_secrets.py
@@ -24,7 +24,7 @@
 #
 # - Install [kubectl](https://kubernetes.io/docs/tasks/tools/).
 # - Have access to a Flyte cluster, for e.g. with `flytectl demo start` as
-#   described {ref}`here <getting_started_running_workflows_locally>`.
+#   described {ref}`here <getting_started_running_workflow_local_cluster>`.
 # :::
 #
 # The first step to using secrets in Flyte is to create one on the backend.