Fix doc reference to spark task (#3980)

Signed-off-by: Jeev B <[email protected]>
flyteorg · Aug 21, 2023 · 2f4edd7 · 2f4edd7
1 parent 85861c9
commit 2f4edd7
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/rsts/concepts/workflow_lifecycle.rst b/rsts/concepts/workflow_lifecycle.rst
@@ -10,7 +10,7 @@ Let's understand how Flyte's plugin machinery works and how information flows fr
 
 Under the hood, Flyte relies on a primitive called “Plugins”. Every task that you run on Flyte is powered by a plugin. Some of these plugins are native and guaranteed by Flyte system. These native plugins, for example, run your Flyte tasks inside a k8s pod. There are three native plugins, namely, ``Container``, ``K8sPod``, and ``Sql``.
 
-Moreover, there are plugins that are actual extensions; they create additional infrastructure and communicate with SaaS on your behalf. Examples include :ref:`Spark <intermediate_using_spark_tasks>`, :ref:`AWS Athena <AWS Athena>`, etc.
+Moreover, there are plugins that are actual extensions; they create additional infrastructure and communicate with SaaS on your behalf. Examples include :ref:`Spark <spark_task>`, :ref:`AWS Athena <AWS Athena>`, etc.
 
 A plugin requires code to live in multiple locations.