Update passage about the paths for opm-common

Author: lisajulia

python/sphinx_docs/docs/common.rst

@@ -4,17 +4,15 @@ OPM Common Python Documentation
 Note on Import Paths
 --------------------
 
-In this documentation, you may notice that some classes are referenced with their full import paths (e.g., opm.io.deck.DeckItem), while others are shown with just the class name. This distinction reflects how these classes are structured within the package:
+In this documentation, some classes are referenced with their full import paths (e.g., opm.io.deck.DeckItem), while others are shown with just the class name. This distinction reflects how these classes are structured within the package:
 
-- Fully Qualified Paths: Classes displayed with their full import paths can be directly imported from their respective modules. For example:
+- Fully Qualified Class Names: Classes displayed with their full import paths can be imported from their respective modules. They have constructors and can be directly instantiated in Python using the __init__ method. For example:
 .. code-block:: python
 
     from opm.io.deck import DeckItem
 
 
-- Simplified Class Names: Classes displayed with just their names, e.g. Connectoin, are intended for internal use or may require additional context when importing. Refer to the specific module documentation for the correct import path if needed.
-
-This structure allows for a organized and modular package, helping to easily access commonly used classes while maintaining clarity for internal components.
+- Unqualified Class Names: Classes displayed with just their names, e.g., Connection, do not have constructors in Python and cannot be directly instantiated in Python. Objects of these classes might be return values of methods of other classes.
 
 Documentation
 -------------