From 2f4edd7f656d8010799a162d1f17907fa7b7943c Mon Sep 17 00:00:00 2001 From: Jeev B Date: Mon, 21 Aug 2023 10:28:10 -0500 Subject: [PATCH] Fix doc reference to spark task (#3980) Signed-off-by: Jeev B --- rsts/concepts/workflow_lifecycle.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rsts/concepts/workflow_lifecycle.rst b/rsts/concepts/workflow_lifecycle.rst index 6e4ea2f037..7c79d45887 100644 --- 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 `, :ref:`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 `, :ref:`AWS Athena `, etc. A plugin requires code to live in multiple locations.