From 9d041ad4d94f54822571a697b3f6f96b7d89e1c3 Mon Sep 17 00:00:00 2001
From: tadasant <3900899+tadasant@users.noreply.github.com>
Date: Wed, 25 Jun 2025 14:33:19 -0700
Subject: [PATCH] Open source

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

diff --git a/docs/design_principles.md b/docs/design_principles.md
index 3440d2b..ef400c2 100644
--- a/docs/design_principles.md
+++ b/docs/design_principles.md
@@ -4,7 +4,7 @@ These are the core constraints that guide the design of the MCP Registry. They a
 
 ## 1. Single Source of Truth
 
-The registry serves as the authoritative metadata repository for publicly-available MCP servers, both locally-run (open source) and remote (open or closed source). Server creators publish once, and all consumers (MCP clients, aggregators, etc.) reference the same canonical data.
+The registry serves as the authoritative metadata repository for publicly-available MCP servers, both locally-run and remote, open source and closed source. Server creators publish once, and all consumers (MCP clients, aggregators, etc.) reference the same canonical data.
 
 ## 2. Minimal Operational Burden
 
@@ -36,4 +36,4 @@ The registry serves as the authoritative metadata repository for publicly-availa
 - Start with MVP that provides immediate value
 - Build foundation that supports future features
 - Don't over-engineer for hypothetical needs
-- Each milestone should be independently valuable
\ No newline at end of file
+- Each milestone should be independently valuable