From f51a768e2a6608639213829423e6454ec5ee74bf Mon Sep 17 00:00:00 2001
From: Jeremiah Lowin <153965+jlowin@users.noreply.github.com>
Date: Thu, 22 May 2025 11:13:36 -0400
Subject: [PATCH] Update docs/getting-started/installation.mdx

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
---
 docs/getting-started/installation.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/getting-started/installation.mdx b/docs/getting-started/installation.mdx
index b28201471..3707f6416 100644
--- a/docs/getting-started/installation.mdx
+++ b/docs/getting-started/installation.mdx
@@ -65,7 +65,7 @@ Prior to `fastmcp==2.3.0` and `mcp==1.8.0`, the 2.x API always mirrored the 1.0
 While we make every effort not to introduce backwards incompatible changes to our public APIs and behavior, FastMCP exists in a rapidly evolving MCP landscape. We're committed to bringing the most cutting-edge features to our users, which occasionally necessitates changes to existing functionality.
 
 As a practice, breaking changes will only occur on minor version changes (e.g., 2.3.x to 2.4.0). A minor version change indicates either:
-- A new feature set significant enough to deserve a new line of features
+- A significant new feature set that warrants a new minor version
 - An implementation of breaking changes that could affect behavior if users upgrade blindly
 
 For users concerned about stability in production environments, we recommend pinning FastMCP to a specific version in your dependencies.