From afb258f18897f5f96c025408c523b0133040e1fc Mon Sep 17 00:00:00 2001
From: Bagatur <22008038+baskaryan@users.noreply.github.com>
Date: Mon, 23 Dec 2024 06:02:01 -0500
Subject: [PATCH] Update docs/evaluation/tutorials/backtesting.mdx

Co-authored-by: Tanushree <87711021+tanushree-sharma@users.noreply.github.com>
---
 docs/evaluation/tutorials/backtesting.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/evaluation/tutorials/backtesting.mdx b/docs/evaluation/tutorials/backtesting.mdx
index d9cf1538..e2d194a2 100644
--- a/docs/evaluation/tutorials/backtesting.mdx
+++ b/docs/evaluation/tutorials/backtesting.mdx
@@ -5,7 +5,7 @@ sidebar_position: 5
 # Backtesting
 
 Deploying your application is just the beginning of a continuous improvement process.
-Typically, you'll want to refine your system by enhancing prompts, language models, tools, and architectures.
+After you deploy to production, you'll want to refine your system by enhancing prompts, language models, tools, and architectures.
 Backtesting involves assessing new versions of your application using historical data and comparing the new outputs to the original ones.
 Compared to evaluations using pre-production datasets, backtesting offers a clearer indication of whether the new version of your application is an improvement over the current deployment.