From 0ef70e52ae90ece589317be1022225e7d86b9be5 Mon Sep 17 00:00:00 2001
From: Adam Seitz <62191182+adamstz@users.noreply.github.com>
Date: Thu, 5 Feb 2026 22:03:57 -0500
Subject: [PATCH] Correct LSP definition in acronym guide

Relationship is flipped.
---
 data/guides/cap-base-solid-kiss-what-do-these-acronyms-mean.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/data/guides/cap-base-solid-kiss-what-do-these-acronyms-mean.md b/data/guides/cap-base-solid-kiss-what-do-these-acronyms-mean.md
index e31f002b..685230b6 100644
--- a/data/guides/cap-base-solid-kiss-what-do-these-acronyms-mean.md
+++ b/data/guides/cap-base-solid-kiss-what-do-these-acronyms-mean.md
@@ -42,7 +42,7 @@ The diagram below explains the common acronyms in system designs.
         Units of code should be open for extension but closed for modification.
 
     3.  LSP (Liskov Substitution Principle)
-        A subclass should be able to be substituted by its base class.
+        A base class should be able to be substituted by its subclass.
 
     4.  ISP (Interface Segregation Principle)
         Expose multiple interfaces with specific responsibilities.