From d6c57402cfbfbf84c37ef26cf318c235ff22e4bc Mon Sep 17 00:00:00 2001
From: Shreyan Sood <42907041+shreyan241@users.noreply.github.com>
Date: Fri, 27 Sep 2024 21:27:43 -0700
Subject: [PATCH] Update Pipeline.md, fixed typo "=inputs" was repeated.
 (#1363)

---
 docs/core-concepts/Pipeline.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/core-concepts/Pipeline.md b/docs/core-concepts/Pipeline.md
index b3028d821..26000f809 100644
--- a/docs/core-concepts/Pipeline.md
+++ b/docs/core-concepts/Pipeline.md
@@ -248,7 +248,7 @@ main_pipeline = Pipeline(stages=[classification_crew, email_router])
 
 inputs = [{"email": "..."}, {"email": "..."}]  # List of email data
 
-main_pipeline.kickoff(inputs=inputs=inputs)
+main_pipeline.kickoff(inputs=inputs)
 ```
 
 In this example, the router decides between an urgent pipeline and a normal pipeline based on the urgency score of the email. If the urgency score is greater than 7, it routes to the urgent pipeline; otherwise, it uses the normal pipeline. If the input doesn't include an urgency score, it defaults to just the classification crew.
@@ -265,4 +265,4 @@ In this example, the router decides between an urgent pipeline and a normal pipe
 The `Pipeline` class includes validation mechanisms to ensure the robustness of the pipeline structure:
 
 - Validates that stages contain only Crew instances or lists of Crew instances.
-- Prevents double nesting of stages to maintain a clear structure.
\ No newline at end of file
+- Prevents double nesting of stages to maintain a clear structure.