diff --git a/SDT/schema3.0/docs/SDT_Components.md b/SDT/schema3.0/docs/SDT_Components.md
index 13c6dfcd938bf0bd47db7173ea46f499799b8c53..b6e710dd7ff95bc371f446fa718a2c1e24e9dfac 100644
--- a/SDT/schema3.0/docs/SDT_Components.md
+++ b/SDT/schema3.0/docs/SDT_Components.md
@@ -185,7 +185,7 @@ The advantage of identifying a subset of generic *ModuleClasses*, described belo
 
 Every [Device](#Device) can then be described by a collection of *Modules* (functionality). In the simplest examples, where there are no extensions needed, each *ModuleClass* has exactly one "child" Module ... in such cases the software developer can consider the two terms to be the same.
 
-The relationship between a *ModuleClass* and a *Module* is very similar to the specification of a superclass and a subclass in an object oriented programming language.
+The relationship between a *ModuleClass* and a *Module* is very similar to the specification of a superclass and a class in an object oriented programming language.
 
 **ModuleClass**