who's -> whose

zopefoundation · Sep 6, 2016 · ea91cd7 · ea91cd7
1 parent 48f25ef
commit ea91cd7
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/documentation/guide/writing-persistent-objects.rst b/documentation/guide/writing-persistent-objects.rst
@@ -290,7 +290,7 @@ You can't change your mind in subclassing persistent
 
 Currently, you can't change your mind about whether a class is
 persistent (subclasses ``persistent.Persistent``) or not.  If you save
-objects in a database who's classes subclass ``persistent.Persistent``,
+objects in a database whose classes subclass ``persistent.Persistent``,
 you can't change your mind later and make them non-persistent, and the
 other way around.  This may be a `bug or misfeature
 <https://github.com/zopefoundation/ZODB/issues/99>`_.
@@ -431,7 +431,7 @@ Ghost
 
    An object that's loaded from the database is loaded as a
    ghost. This typically happens when the object is a subobject of
-   another object who's state is loaded.
+   another object whose state is loaded.
 
 We can interrogate and control an object's state, although somewhat
 indirectly.  To do this, we'll look at some special persistent-object