From 1bc553a7f931cf53aed30631ca07a69116d93a15 Mon Sep 17 00:00:00 2001 From: Jim Fulton Date: Fri, 26 Aug 2016 11:58:53 -0400 Subject: [PATCH] typos --- documentation/guide/writing-persistent-objects.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/documentation/guide/writing-persistent-objects.rst b/documentation/guide/writing-persistent-objects.rst index 52e8d0e..30c82dc 100644 --- a/documentation/guide/writing-persistent-objects.rst +++ b/documentation/guide/writing-persistent-objects.rst @@ -13,13 +13,13 @@ Access and modification Two of the main jobs of the ``Persistent`` base class is to detect when an object has been accessed and when it has been modified. When -an object is accessed, it's state may need to be loaded from the +an object is accessed, its state may need to be loaded from the database. When an object is modified, the modification needs to be saved if a transaction is committed. ``Persistent`` detects object accesses by hooking into object attribute access and update. In the case of object update, there -maybe other ways of modifying state that we need to make provision for. +may be other ways of modifying state that we need to make provision for. Rules of persistence ====================