[Zope3-checkins] SVN: Zope3/trunk/src/zope/ Minor fixes.

[Gintautas Miliauskas]

Log message for revision 29999:
  Minor fixes.
  

Changed:
  U   Zope3/trunk/src/zope/app/form/browser/widget_macros.pt
  U   Zope3/trunk/src/zope/i18n/i18nobject.txt
  U   Zope3/trunk/src/zope/i18nmessageid/messages.txt

-=-
Modified: Zope3/trunk/src/zope/app/form/browser/widget_macros.pt
===================================================================
--- Zope3/trunk/src/zope/app/form/browser/widget_macros.pt	2005-04-15 10:27:06 UTC (rev 29998)
+++ Zope3/trunk/src/zope/app/form/browser/widget_macros.pt	2005-04-15 12:29:54 UTC (rev 29999)
@@ -19,4 +19,4 @@
       </div>
     </metal:block>
   </body>
-</html>
\ No newline at end of file
+</html>

Modified: Zope3/trunk/src/zope/i18n/i18nobject.txt
===================================================================
--- Zope3/trunk/src/zope/i18n/i18nobject.txt	2005-04-15 10:27:06 UTC (rev 29998)
+++ Zope3/trunk/src/zope/i18n/i18nobject.txt	2005-04-15 12:29:54 UTC (rev 29999)
@@ -44,7 +44,7 @@
 ------------
 
 There will be an interface called II18nObject (which inherits I18nContent
-of course), which is a cameleon-like container, as it adapts to the
+of course), which is a chameleon-like container, as it adapts to the
 properties of the contained object type. In order to accomplish all this,
 you will have to implement your own traverser which looks up the correct
 subobject.

Modified: Zope3/trunk/src/zope/i18nmessageid/messages.txt
===================================================================
--- Zope3/trunk/src/zope/i18nmessageid/messages.txt	2005-04-15 10:27:06 UTC (rev 29998)
+++ Zope3/trunk/src/zope/i18nmessageid/messages.txt	2005-04-15 12:29:54 UTC (rev 29999)
@@ -50,9 +50,10 @@
   >>> robot.default
   u'${name} is a robot.'
   >>> robot.mapping
-  >>> 
+  >>> robot.domain
+  'futurama'
 
-The messags's attributes are considered part of the immutable message
+The message's attributes are considered part of the immutable message
 object.  They cannot be changed once the message id is created:
 
   >>> robot.domain = "planetexpress"
@@ -110,8 +111,8 @@
 
 The proposed solution for backward compatability is to support both
 implementations in parallel, deprecating the mutable one.  A separate
-factory, 'I18nMessageFactory', will instanciate immutable message ids,
-while the deprecated oldone will continue to work like before.
+factory, 'I18nMessageFactory', will instantiate immutable message ids,
+while the deprecated old one will continue to work like before.
 
 The roadmap to immutable-only message ids is proposed as follows: