terminology and wording fixes

Technologicat · Technologicat · commit 9eaa4c76c934 · 2021-05-15T12:47:02.000+03:00
diff --git a/doc/features.md b/doc/features.md
@@ -3135,7 +3135,7 @@ Based on my own initial experiments with this feature, the machinery itself work
 
 The machinery itself is also missing some advanced features, such as matching the most specific multimethod candidate instead of the most recently defined one; an `issubclass` equivalent that understands `typing` type specifications; and a mechanism to remove previously declared multimethods.
 
-**CAUTION**: Multiple dispatch can be dangerous. Particularly, `@augment` can be dangerous to the readability of your codebase. If methods are added for a generic function defined elsewhere, for types defined elsewhere, this may lead to [*spooky action at a distance*](https://lexi-lambda.github.io/blog/2016/02/18/simple-safe-multimethods-in-racket/) (as in [action at a distance](https://en.wikipedia.org/wiki/Action_at_a_distance_(computer_programming))). In the Julia community, this is known as [*type piracy*](https://docs.julialang.org/en/v1/manual/style-guide/#Avoid-type-piracy). Keep in mind that the multiple-dispatch table is global state!
+**CAUTION**: Multiple dispatch can be dangerous. Particularly, `@augment` can be dangerous to the readability of your codebase. If a new multimethod is added for a generic function defined elsewhere, for types defined elsewhere, this may lead to [*spooky action at a distance*](https://lexi-lambda.github.io/blog/2016/02/18/simple-safe-multimethods-in-racket/) (as in [action at a distance](https://en.wikipedia.org/wiki/Action_at_a_distance_(computer_programming))). In the Julia community, this is known as [*type piracy*](https://docs.julialang.org/en/v1/manual/style-guide/#Avoid-type-piracy). Keep in mind that the multiple-dispatch table is global state!
 
 
 #### ``typed``: add run-time type checks with type annotation syntax
diff --git a/unpythonic/dispatch.py b/unpythonic/dispatch.py
@@ -420,7 +420,7 @@ def _list_multimethods(dispatcher, self_or_cls=None):
     relevant_registries = [reversed(dispatcher._method_registry)]
 
     # But if this dispatcher is installed on a method, we must
-    # look up generic function methods also in the class's MRO.
+    # look up multimethods also in the class's MRO.
     #
     # For *static methods* MRO is not supported. Basically, one of
     # the roles of `cls` or `self` is to define the MRO; a static
diff --git a/unpythonic/tests/test_dispatch.py b/unpythonic/tests/test_dispatch.py
@@ -201,9 +201,9 @@ def instmeth(self, x: float):
                 return f"floating with {self.a * x}"
 
         tt2 = BabyTestTarget(3)
-        # the new generic-function methods become available, installed on the OOP method
+        # the new multimethods become available, installed on the OOP method
         test[tt2.instmeth(3.14) == "floating with 9.42"]
-        # old generic-function methods registered by the ancestor remain available
+        # old multimethods registered by the ancestor remain available
         test[tt2.instmeth("hi") == "hi hi hi"]
         test[tt2.instmeth(21) == 63]
         test[tt2.clsmeth(3.14) == "Test target floats: 6.28"]

Original file line number	Diff line number	Diff line change
`@@ -420,7 +420,7 @@ def _list_multimethods(dispatcher, self_or_cls=None):`
`420`	`420`	`relevant_registries = [reversed(dispatcher._method_registry)]`
`421`	`421`
`422`	`422`	`# But if this dispatcher is installed on a method, we must`
`423`		`- # look up generic function methods also in the class's MRO.`
	`423`	`+ # look up multimethods also in the class's MRO.`
`424`	`424`	`#`
`425`	`425`	`# For static methods MRO is not supported. Basically, one of`
`426`	`426`	# the roles of `cls` or `self` is to define the MRO; a static