From 5a60e4510a02c97457db41acb2dcec8a20c0e215 Mon Sep 17 00:00:00 2001 From: Ville Tuulos Date: Mon, 15 Dec 2025 20:41:35 -0800 Subject: [PATCH] fix typo --- .../scheduling-metaflow-flows/scheduling-with-kubeflow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/production/scheduling-metaflow-flows/scheduling-with-kubeflow.md b/docs/production/scheduling-metaflow-flows/scheduling-with-kubeflow.md index e502456b..b5fdfd26 100644 --- a/docs/production/scheduling-metaflow-flows/scheduling-with-kubeflow.md +++ b/docs/production/scheduling-metaflow-flows/scheduling-with-kubeflow.md @@ -144,7 +144,7 @@ python parameter_flow.py kubeflow-pipelines trigger --alpha 0.5 You can also trigger a run as a specific [Kubeflow Experiment](https://www.kubeflow.org/docs/components/pipelines/concepts/experiment/): ``` -python parameter_flow.py kubeflow-pipelines trigger --alpha 0.5 --experiment new_moddel +python parameter_flow.py kubeflow-pipelines trigger --alpha 0.5 --experiment new_model ``` By default, the latest version of the flow is triggered. You can trigger an older version by specifying `--version-name`: