summaryrefslogtreecommitdiff
path: root/src/zope/interface/interface.py
diff options
context:
space:
mode:
authorJason Madden <jamadden@gmail.com>2021-03-17 07:35:12 -0500
committerJason Madden <jamadden@gmail.com>2021-03-17 07:39:49 -0500
commit488a317abdfa2a1fa04efd2f2d8d22a433beaaf8 (patch)
treeee112ad969b0ca5987d56b471dd34818e67f8a22 /src/zope/interface/interface.py
parentdd69666aae99afe0d47b3af81149fbd7e97f59fe (diff)
downloadzope-interface-docs-update.tar.gz
Update the Adaptation docs to be more concrete.docs-update
This should help provide better motivating use cases. Examples inspired by https://glyph.twistedmatrix.com/2021/03/interfaces-and-protocols.html Also some minor typo fixes and updates to comments.
Diffstat (limited to 'src/zope/interface/interface.py')
-rw-r--r--src/zope/interface/interface.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/zope/interface/interface.py b/src/zope/interface/interface.py
index d100aae..e3d67ae 100644
--- a/src/zope/interface/interface.py
+++ b/src/zope/interface/interface.py
@@ -425,7 +425,7 @@ class Specification(SpecificationBase):
# some bases that DO implement an interface, and some that DO
# NOT. In such a mixed scenario, you wind up with a set of
# bases to consider that look like this: [[..., Interface],
- # [..., object], ...]. Depending on the order if inheritance,
+ # [..., object], ...]. Depending on the order of inheritance,
# Interface can wind up before or after object, and that can
# happen at any point in the tree, meaning Interface can wind
# up somewhere in the middle of the order. Since Interface is