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] 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.