[Zodb-checkins] CVS: Zope3/lib/python/Persistence - IPersistent.py:1.5 Module.py:1.24

Florent Guillaume fg@nuxeo.com
Thu, 3 Oct 2002 15:44:55 -0400


Update of /cvs-repository/Zope3/lib/python/Persistence
In directory cvs.zope.org:/tmp/cvs-serv23573/lib/python/Persistence

Modified Files:
	IPersistent.py Module.py 
Log Message:
Fixed pervasive it's/its grammatical error in comments or docstrings.


=== Zope3/lib/python/Persistence/IPersistent.py 1.4 => 1.5 ===
--- Zope3/lib/python/Persistence/IPersistent.py:1.4	Thu Oct  3 10:18:42 2002
+++ Zope3/lib/python/Persistence/IPersistent.py	Thu Oct  3 15:44:23 2002
@@ -59,7 +59,7 @@
 
     - Ghost
 
-      the object is in memory but it's state has not been loaded from
+      the object is in memory but its state has not been loaded from
       the database (or has been unloaded).  In this state, the object
       doesn't contain any data.
 
@@ -78,13 +78,13 @@
       This transition occurs when someone sets an attribute or sets
       _p_changed to a true value on an up-to-date or sticky
       object. When the transition occurs, the persistent object is
-      required to call the register method on it's data manager,
+      required to call the register method on its data manager,
       passing itself as the only argument.
 
     - Saved -> Sticky
 
       This transition occurs when C code marks the object as sticky to
-      prevent it's deactivation and transition to the ghost state.
+      prevent its deactivation and transition to the ghost state.
 
     - Saved -> Ghost
 
@@ -95,7 +95,7 @@
     - Sticky -> Saved
 
       This transition occurs when C code unmarks the object as sticky to
-      allow it's deactivation and transition to the ghost state.
+      allow its deactivation and transition to the ghost state.
 
     - Changed -> Saved
 


=== Zope3/lib/python/Persistence/Module.py 1.23 => 1.24 ===
--- Zope3/lib/python/Persistence/Module.py:1.23	Thu Oct  3 00:16:59 2002
+++ Zope3/lib/python/Persistence/Module.py	Thu Oct  3 15:44:23 2002
@@ -40,7 +40,7 @@
 # load the state confuses things.  The first call to setstate attempts
 # to reference an attribute of the module.  That getattr() fails because
 # the module is not a ghost, but does have any empty dict.  Since
-# that getattr() fails, it's state can't be unpickled.
+# that getattr() fails, its state can't be unpickled.
 #
 # Not sure what to do about this.