From 99370b6b8652bd7d559ab4f9923562b130b3bd0c Mon Sep 17 00:00:00 2001
From: Eduardo Apolinario <653394+eapolinario@users.noreply.github.com>
Date: Wed, 21 Aug 2024 12:10:43 -0400
Subject: [PATCH 1/3] More concise definition of launchplan

Signed-off-by: Eduardo Apolinario <653394+eapolinario@users.noreply.github.com>
---
 .../tasks_workflows_and_launch_plans.md            | 14 +++++---------
 1 file changed, 5 insertions(+), 9 deletions(-)

diff --git a/docs/flyte_fundamentals/tasks_workflows_and_launch_plans.md b/docs/flyte_fundamentals/tasks_workflows_and_launch_plans.md
index c8ca7f2071..44f5933835 100644
--- a/docs/flyte_fundamentals/tasks_workflows_and_launch_plans.md
+++ b/docs/flyte_fundamentals/tasks_workflows_and_launch_plans.md
@@ -263,15 +263,11 @@ Learn more about chaining flyte entities in the {ref}`User Guide <chain_flyte_en
 
 ## Launch plans
 
-A Flyte {py:class}`~flytekit.LaunchPlan` is a partial or complete binding of
-inputs necessary to launch a workflow. You can think of it like
-the {py:func}`~functools.partial` function in the Python standard library where
-you can define default (overridable) and fixed (non-overridable) inputs.
-
-```{note}
-Additionally, `LaunchPlan` provides an interface for specifying run-time
-overrides such as notifications, schedules, and more.
-```
+A launch plan in Flyte is a mechanism to define and manage the execution of workflows with 
+predefined or fixed inputs, schedules, and runtime overrides like notifications. It allows
+workflows to be executed with specific configurations and can be shared for consistent and 
+reproducible executions. Each workflow has a default launch plan generated upon registration, 
+but custom launch plans can also be created to meet different requirements.
 
 Create a launch plan like so:
 

From 247d2d93584f72d23635dc02ad8ea94d54a65e9f Mon Sep 17 00:00:00 2001
From: Eduardo Apolinario <653394+eapolinario@users.noreply.github.com>
Date: Fri, 23 Aug 2024 11:25:38 -0400
Subject: [PATCH 2/3] Update
 docs/flyte_fundamentals/tasks_workflows_and_launch_plans.md

Co-authored-by: Nikki Everett <neverett@users.noreply.github.com>
Signed-off-by: Eduardo Apolinario <653394+eapolinario@users.noreply.github.com>
---
 docs/flyte_fundamentals/tasks_workflows_and_launch_plans.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/flyte_fundamentals/tasks_workflows_and_launch_plans.md b/docs/flyte_fundamentals/tasks_workflows_and_launch_plans.md
index 44f5933835..0c69cca54b 100644
--- a/docs/flyte_fundamentals/tasks_workflows_and_launch_plans.md
+++ b/docs/flyte_fundamentals/tasks_workflows_and_launch_plans.md
@@ -264,7 +264,7 @@ Learn more about chaining flyte entities in the {ref}`User Guide <chain_flyte_en
 ## Launch plans
 
 A launch plan in Flyte is a mechanism to define and manage the execution of workflows with 
-predefined or fixed inputs, schedules, and runtime overrides like notifications. It allows
+predefined or fixed inputs, schedules, and runtime overrides, like notifications. Launch plans allow
 workflows to be executed with specific configurations and can be shared for consistent and 
 reproducible executions. Each workflow has a default launch plan generated upon registration, 
 but custom launch plans can also be created to meet different requirements.

From d78a6150d849b3c6f355809daa5ae6193081ba98 Mon Sep 17 00:00:00 2001
From: Eduardo Apolinario <653394+eapolinario@users.noreply.github.com>
Date: Fri, 23 Aug 2024 11:25:45 -0400
Subject: [PATCH 3/3] Update
 docs/flyte_fundamentals/tasks_workflows_and_launch_plans.md

Co-authored-by: Nikki Everett <neverett@users.noreply.github.com>
Signed-off-by: Eduardo Apolinario <653394+eapolinario@users.noreply.github.com>
---
 docs/flyte_fundamentals/tasks_workflows_and_launch_plans.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/flyte_fundamentals/tasks_workflows_and_launch_plans.md b/docs/flyte_fundamentals/tasks_workflows_and_launch_plans.md
index 0c69cca54b..f66988343a 100644
--- a/docs/flyte_fundamentals/tasks_workflows_and_launch_plans.md
+++ b/docs/flyte_fundamentals/tasks_workflows_and_launch_plans.md
@@ -266,7 +266,7 @@ Learn more about chaining flyte entities in the {ref}`User Guide <chain_flyte_en
 A launch plan in Flyte is a mechanism to define and manage the execution of workflows with 
 predefined or fixed inputs, schedules, and runtime overrides, like notifications. Launch plans allow
 workflows to be executed with specific configurations and can be shared for consistent and 
-reproducible executions. Each workflow has a default launch plan generated upon registration, 
+reproducible executions. Each workflow has a default launch plan generated upon registration, with the same name as the workflow, 
 but custom launch plans can also be created to meet different requirements.
 
 Create a launch plan like so: