[DOCUMENTATION] Minor fixes for regressions from last set of changes 🙈

Changes in file README.md:
 * minor rewording for readability

Changes in file multicast/__init__.py:
 * minor fixes for doctests
 * related work

Author: reactive-firewall

README.md

@@ -11,8 +11,8 @@ applications, making it straightforward to work with multicast sockets.
 ## Features
 
 - **Easy Multicast Communication**: Send and receive messages over multicast networks with
-  simple interfaces.
-- **Command-Line Tools**: Includes command-line utilities for quick multicast operations.
+  simple `Python` interfaces.
+- **Command-Line Tools**: Includes command-line utilities for quick multicast prototyping.
 - **Cross-Python Compatibility**: Designed to work with multiple Python versions.
 - **Support for UDP**: Works with UDP via IPv4 multicast addresses.
 
@@ -53,7 +53,7 @@ Install the package using `pip`:
 pip install multicast
 ```
 
-<details><summary>Other Methods</summary>
+<details><summary>Alternative Methods</summary>
 
 There are many ways to install the module besides using `pip`, but unless you have a specific need,
 using `pip` is recommended for most users.

multicast/__init__.py

@@ -273,9 +273,9 @@
 
 Key Features:
 	- Easy-to-use python interfaces for multicast communication.
-		- transmition via multicast.send
-		- high-level reciving via multicast.hear for building custom multicast services.
-		- low-level reciving via multicast.recv for advanced non-blocking use-cases.
+		- transmission via multicast.send
+		- high-level receiving via multicast.hear for building custom multicast services.
+		- low-level receiving via multicast.recv for advanced non-blocking use-cases.
 	- Command-line tools for quick multicast prototyping.
 	- Support for UDP multicast (currently IPv4 Only) via Python's built-in socket module.
 	- Compliance with RFC-6335 for dynamic/private port ranges.
@@ -398,7 +398,7 @@
 
 	> [!CAUTION]
 	> This value is NOT related to the actual packet size, the python socket module, and
-	> underlaying OS, firmware and even some hardware will handle all of that. If you need
+	> underlying OS, firmware and even some hardware will handle all of that. If you need
 	> to change buffers you are better off focusing on changing the underlying MTU of the
 	> entire network infrastructure instead (albeit that may not be possible for most users).
 
@@ -712,7 +712,7 @@ class mtool(abc.ABC):
 		>>> _multicast.mtool is not None
 		True
 		>>> type(_multicast.mtool) #doctest: +ELLIPSIS
-		<...multicast.mtool...>
+		<...abc.ABC...>
 		>>> hasattr(_multicast.mtool, "__abstractmethods__")
 		True
 		>>>
@@ -725,6 +725,7 @@ class mtool(abc.ABC):
 		>>> hasattr(_multicast.mtool, "__abstractmethods__")
 		True
 		>>> len(_multicast.mtool.__abstractmethods__) >= int(2)
+		True
 		>>> "doStep" in _multicast.mtool.__abstractmethods__
 		True
 		>>> "setupArgs" in _multicast.mtool.__abstractmethods__
@@ -739,12 +740,13 @@ class mtool(abc.ABC):
 		>>> hasattr(_multicast.mtool, "__abstractmethods__")
 		True
 		>>> len(_multicast.mtool.__abstractmethods__) >= int(2)
+		True
 		>>> "doStep" in _multicast.mtool.__abstractmethods__
 		True
 		>>> "setupArgs" in _multicast.mtool.__abstractmethods__
 		True
 		>>> _test_dir_fixture = dir(_multicast.mtool)
-		>>> _test_dir_fixture is not None:
+		>>> _test_dir_fixture is not None
 		True
 		>>> "buildArgs" in _test_dir_fixture
 		True