From c32cb9a0b2a5427afa8b328f58d69ed5dfcca5de Mon Sep 17 00:00:00 2001
From: Lerking <33354709+Lerking@users.noreply.github.com>
Date: Wed, 6 Mar 2024 07:54:38 +0100
Subject: [PATCH] Updated The birth of a python plugin architecture (markdown)

---
 The-birth-of-a-python-plugin-architecture.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/The-birth-of-a-python-plugin-architecture.md b/The-birth-of-a-python-plugin-architecture.md
index 014172a..e14a734 100644
--- a/The-birth-of-a-python-plugin-architecture.md
+++ b/The-birth-of-a-python-plugin-architecture.md
@@ -3,7 +3,7 @@
 ## Q&A
 Q. What is the plugin architecture design pattern?
 
-A. The plugin architecture design pattern (also known as microkernel) is a philosophy that surrounds a core application with a number of attachable/detachable modules. These module can be attached and detached in runtime.
+A. The plugin architecture design pattern (also known as microkernel) is a philosophy that surrounds a core application with a number of attachable/detachable modules (plugins). These can be attached and detached in runtime.
    The main benefits are the following.
    - A core application that needs little to no updating unless it's updated core functionality.
    - Functionality can be kept and maintained in small separate modules (plugins). A plugin can be updated regardless of the core application as long as it maintains the same interface to the core application.