[Checkins] SVN: zope_secrets/trunk/source/ Fixed a few typos.
Maurits van Rees
m.van.rees at zestsoftware.nl
Mon Jan 2 13:21:20 UTC 2012
Log message for revision 123882:
Fixed a few typos.
Changed:
U zope_secrets/trunk/source/hooks.rst
U zope_secrets/trunk/source/security.rst
U zope_secrets/trunk/source/startup.rst
-=-
Modified: zope_secrets/trunk/source/hooks.rst
===================================================================
--- zope_secrets/trunk/source/hooks.rst 2012-01-02 13:06:15 UTC (rev 123881)
+++ zope_secrets/trunk/source/hooks.rst 2012-01-02 13:21:20 UTC (rev 123882)
@@ -19,7 +19,7 @@
* ``IDatabaseOpened``, notified when the main ZODB has been opened, but before
the root application object is set.
* ``IDatabaseOpenedWithRoot``, notified later in the startup cycle, when the
- application root has been set and initalised.
+ application root has been set and initialised.
* ``IProcessStarting``, notified when the Zope startup process has completed,
but before the Zope server runs (and so can listen to requests).
@@ -87,4 +87,4 @@
to register an adapter to ``IBrowserPublisher``.
An adapter to ``ITraversable`` can be used to implement namespace traversal
-(``.../++<namespace>++name/...``). See above for further details.
\ No newline at end of file
+(``.../++<namespace>++name/...``). See above for further details.
Modified: zope_secrets/trunk/source/security.rst
===================================================================
--- zope_secrets/trunk/source/security.rst 2012-01-02 13:06:15 UTC (rev 123881)
+++ zope_secrets/trunk/source/security.rst 2012-01-02 13:21:20 UTC (rev 123882)
@@ -516,7 +516,7 @@
----------------------
The list of known (valid) roles in any context is set in the attribute
-``__ac_roles__``. On the initalisation of the application root during startup,
+``__ac_roles__``. On the initialisation of the application root during startup,
in ``install_required_roles()`` in ``OFS.Application.AppInitializer``, this is
made to include at least ``Owner`` and ``Authenticated``. The ``RoleManager``
base class set it as a class variable to contain
@@ -590,4 +590,4 @@
The user folder implementations in ``AccessControl`` and PAS make specific
checks for this user during authentication and permission validation to ensure
this user can always log in and has virtually any permission, with the exception
-of ``_what_not_even_god_should_do`` (``ACCESS_NONE``).
\ No newline at end of file
+of ``_what_not_even_god_should_do`` (``ACCESS_NONE``).
Modified: zope_secrets/trunk/source/startup.rst
===================================================================
--- zope_secrets/trunk/source/startup.rst 2012-01-02 13:06:15 UTC (rev 123881)
+++ zope_secrets/trunk/source/startup.rst 2012-01-02 13:21:20 UTC (rev 123882)
@@ -152,7 +152,7 @@
``ZServer.medusa.http_server``, which in turn is an ``asyncore.dispatcher``.
Servers are created in ``ZopeStarter.setupServers()``, which loops over the
-``ZConfig``-defined server factories and call their ``create()`` metohod. The
+``ZConfig``-defined server factories and call their ``create()`` method. The
server factories are defined in ``ZServer.datatypes``. (The word ``datatypes``
refers to ``ZConfig`` data types.)
@@ -226,7 +226,7 @@
loops over this list, calling ``install_package()`` for each. This works very
much like ``install_product()``. When it is done, it calls the function
``OFS.metaconfigure.package_initialized()`` to remove the package from the
-list of packages to initalise.
+list of packages to initialise.
How do Zope 2 product constructors work?
----------------------------------------
@@ -435,4 +435,4 @@
constructor information from a persistent ``Product`` instance (from
``Control_Panel`` if there was one. This supports a (legacy) approach where
instead of calling ``registerClass()`` to register constructors, constructors
-are set in a dict called``_m`` at the root of the product.
\ No newline at end of file
+are set in a dict called``_m`` at the root of the product.
More information about the checkins
mailing list