openjpa-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r564011 - /openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_caching.xml
Date Wed, 08 Aug 2007 20:25:48 GMT
Author: clr
Date: Wed Aug  8 13:25:47 2007
New Revision: 564011

Fix typos in caching section of doc


Modified: openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_caching.xml
--- openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_caching.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_caching.xml Wed Aug  8 13:25:47
@@ -341,7 +341,7 @@
 Most caches are of limited size. Pinning an identity to the cache ensures that
-the cache will mill not kick the data for the corresponding instance out of the
+the cache will will not kick the data for the corresponding instance out of the
 cache, unless you manually evict it. Note that even after manual eviction, the
 data will get pinned again the next time it is fetched from the store. You can
 only remove a pin and make the data once again available for normal cache
@@ -709,11 +709,11 @@
-Invoking <methodname>OpenJPAEntityManager.evict</methodname><emphasis>does
+Invoking <methodname>OpenJPAEntityManager.evict</methodname><emphasis>
does not
 </emphasis> result in the corresponding data being dropped from the data cache,
 unless you have set the proper configuration options as explained above (see
 <xref linkend="ref_guide_cache_pmevict"/>). Other methods related to the
-<classname>EntityManager</classname> cache also do not effect the data cache.
+<classname>EntityManager</classname> cache also do not affect the data cache.
 The data cache assumes that it is up-to-date with respect to the datastore, so

View raw message