[Zope3-checkins] CVS: Zope3/src/zope/configuration - config.py:1.15 interfaces.py:1.4 zopeconfigure.py:1.3

[Gary Poster]

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

Modified Files:
	config.py interfaces.py zopeconfigure.py 
Log Message:
Just some typo fix ups.





=== Zope3/src/zope/configuration/config.py 1.14 => 1.15 ===
--- Zope3/src/zope/configuration/config.py:1.14	Thu Jan 22 18:53:15 2004
+++ Zope3/src/zope/configuration/config.py	Fri Jan 23 11:59:38 2004
@@ -240,7 +240,7 @@
     def action(self, discriminator, callable=None, args=(), kw={}):
         """Add an action with the given discriminator, callable and arguments
 
-        For testing purposes, the callable and arguments may be ommitted.
+        For testing purposes, the callable and arguments may be omitted.
         In that case, a default noop callable is used.
 
         The discriminator must be given, but it can be None, to indicate that
@@ -909,7 +909,7 @@
 
     namespace = zope.schema.URI(
         title=u"Namespace",
-        description=u"The namespace that directives' names will be defined in",
+        description=u"The namespace in which directives' names will be defined",
         )
 
 class IDirectivesContext(IDirectivesInfo, IConfigurationContext):
@@ -1027,7 +1027,7 @@
     ...    y = zope.schema.TextLine()
 
     We won't bother creating a special grouping directive class. We'll
-    just use GroupingContextDecorator, which simple sets up a grouping
+    just use GroupingContextDecorator, which simply sets up a grouping
     context that has extra attributes defined by a schema:
 
     >>> defineGroupingDirective(context, 'g', Ixy,


=== Zope3/src/zope/configuration/interfaces.py 1.3 => 1.4 ===
--- Zope3/src/zope/configuration/interfaces.py:1.3	Thu Jul 31 10:56:40 2003
+++ Zope3/src/zope/configuration/interfaces.py	Fri Jan 23 11:59:38 2004
@@ -46,7 +46,7 @@
         is in the foo package, then the dotted name foo.bar.spam can
         be shortened to .bar.spam.
 
-        If the current package is multiple levels deel, multiple
+        If the current package is multiple levels deep, multiple
         leading dots can be used to refer to higher-level modules.
         For example, if the current package is x.y.z, the dotted
         object name ..foo refers to x.y.foo.


=== Zope3/src/zope/configuration/zopeconfigure.py 1.2 => 1.3 ===
--- Zope3/src/zope/configuration/zopeconfigure.py:1.2	Sun Aug 17 02:08:49 2003
+++ Zope3/src/zope/configuration/zopeconfigure.py	Fri Jan 23 11:59:38 2004
@@ -14,7 +14,7 @@
 """Zope configure directive
 
 This file contains the implementation of the Zope configure directive.
-It is beoken out in a separate file to provide an example of a grouping
+It is broken out in a separate file to provide an example of a grouping
 directive.
 
 The zope configuration directive is a pure grouping directive.  It
@@ -23,7 +23,7 @@
 and file paths. It also allows an i18n domain to be specified.  The
 information collected is used by subdirectives.
 
-To define a grouping directive, we need to do 3 things:
+To define a grouping directive, we need to do three things:
 
 - Define a schema for the parameters passed to the directive
 
@@ -31,11 +31,11 @@
 
 - Register the class
 
-The parameter schema is given by IZopeConfigure. It specified a
+The parameter schema is given by IZopeConfigure. It specifies a
 package parameter and an i18n_domain paramter.  The package parameter
 is specified as a ``GlobalObject``. This means it must be given as a
 dotted name that can be resolved through import.  The i18n domain is
-just a plan (not unicode) string.
+just a plain (not unicode) string.
 
 The handler class has a constructor that takes a context to be adapted
 and zero or more arguments (depending on the paramter schema).  The
@@ -43,7 +43,7 @@
 ``zope.configuration.interfaces.IGroupingContext``, which defines
 hooks ``before`` and ``after``, that are called with no arguments
 before and after nested directives are processed.  If a grouping
-directibe handler creates any actions, or does any computation, this
+directive handler creates any actions, or does any computation, this
 is normally done in either the ``before`` or ``after`` hooks.
 Grouping handlers are normally decorators.
 
@@ -89,8 +89,8 @@
   </meta:groupingDirective>
 
 We use the groupingDirective meta-directive to register a grouping
-directive. The parameters are self explanitory.  The textual contents
-of the directive provides documentation text, exclusing parameter
+directive. The parameters are self explanatory.  The textual contents
+of the directive provide documentation text, excluding parameter
 documentation, which is provided by the schema.
 
 (The Zope ``configuration`` directive is actually registered using a