From 47cd5847ee8ce1cec6057305e73ade93e7f3d9e7 Mon Sep 17 00:00:00 2001
From: Shiven Shekar <66806369+shiven01@users.noreply.github.com>
Date: Thu, 6 Nov 2025 07:09:56 -0800
Subject: [PATCH] Update butler-flow.mdx

Spelling mistake, fixed "vamilla" --> "vanilla"
---
 content/docs/butler-flow.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/docs/butler-flow.mdx b/content/docs/butler-flow.mdx
index 9c9b920..ee49333 100644
--- a/content/docs/butler-flow.mdx
+++ b/content/docs/butler-flow.mdx
@@ -24,7 +24,7 @@ In a nutshell, the basic development cycle is very simple.
 
 ### The Target Branch
 
-In stock, vamilla Git tooling, there is nothing specified as the production branch, no special "trunk". It is only by convention that this is enforced.
+In stock, vanilla Git tooling, there is nothing specified as the production branch, no special "trunk". It is only by convention that this is enforced.
 
 In GitButler, virtual branches will not work without the specification of a special "target branch". Everything exists in relation to this special branch, everything that differs from it must be accounted for by being owned by some other branch, until those changes are integrated.