From c25537f051c307078c85c714ae4d832b794b6db1 Mon Sep 17 00:00:00 2001 From: Ketan Umare <16888709+kumare3@users.noreply.github.com> Date: Mon, 22 Feb 2021 12:10:05 -0800 Subject: [PATCH] Update rsts/plugins/extend/intro.rst Co-authored-by: Katrina Rogan --- rsts/plugins/extend/intro.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/rsts/plugins/extend/intro.rst b/rsts/plugins/extend/intro.rst index 5ec45ae1be..6a39a079f1 100644 --- a/rsts/plugins/extend/intro.rst +++ b/rsts/plugins/extend/intro.rst @@ -5,7 +5,7 @@ When & How to Extend Flyte ########################### The Core of Flyte is a container execution engine, where you can write one or more tasks and string them together to form a data dependency DAG - called a ``workflow``. -If your work involves writing simple python or java tasks that can either perform operations on their own or can call out to external services - then there is ``NO NEED to extend FLYTE``. +If your work involves writing simple python or java tasks that can either perform operations on their own or can call out to external services - then there is **NO NEED to extend FLYTE**. But, in that case you can almost do everything using python / java or a container - So Why should you even have to extend Flyte? @@ -123,4 +123,4 @@ Use the conclusion of the flow-chart to refer to the right doc ================================================================ - :ref:`extend-plugin-flytekit-python` -- :ref:`extend-plugin-flyte-backend` \ No newline at end of file +- :ref:`extend-plugin-flyte-backend`