[Zope3-checkins] CVS: Zope3/src/zope/configuration/tests - test_nested.py:1.2

Gary Poster gary at zope.com
Fri Jan 23 11:59:40 EST 2004


Update of /cvs-repository/Zope3/src/zope/configuration/tests
In directory cvs.zope.org:/tmp/cvs-serv24987/tests

Modified Files:
	test_nested.py 
Log Message:
Just some typo fix ups.





=== Zope3/src/zope/configuration/tests/test_nested.py 1.1 => 1.2 ===
--- Zope3/src/zope/configuration/tests/test_nested.py:1.1	Sat Aug  2 08:45:53 2003
+++ Zope3/src/zope/configuration/tests/test_nested.py	Fri Jan 23 11:59:39 2004
@@ -33,9 +33,9 @@
 
 This file shows you how to handle the second case above. In this case,
 we have grouping directives that are meant to collaborate with
-specisific contained directives.  To do this, you have the grouping
+specific contained directives.  To do this, you have the grouping
 directives declare a more specific (or alternate) interface to
-``IConfigurationContext``. Directive's designed to work with those
+``IConfigurationContext``. Directives designed to work with those
 grouping directives are registered for the new interface.
 
 Let's look at example. Suppose we wanted to be able to define schema
@@ -54,8 +54,8 @@
 
 The class, ``Schema``, provides the handler for the schema directive. (If
 you haven't read the documentation in ``zopeconfigure.py``, you need
-to do so now.)  The constructor saves it's arguments as attributes
-and initializes it's ``fields`` attribute.
+to do so now.)  The constructor saves its arguments as attributes
+and initializes its ``fields`` attribute.
 
 The ``after`` method of the ``Schema`` class creates a schema and
 computes an action to register the schema in the schema registry.  The
@@ -63,8 +63,8 @@
 schema.
 
 It's important to note that when we call the ``action`` method on
-``self``, rather than on ``self.conntext``.  This is because, in a
-grouping directive handler, the handler instance is, itself a context.
+``self``, rather than on ``self.context``.  This is because, in a
+grouping directive handler, the handler instance is itself a context.
 When we call the ``action`` method, the method stores additional meta
 data associated with the context it was called on. This meta data
 includes an include path, used when resolving conflicting actions,




More information about the Zope3-Checkins mailing list