[Checkins] SVN: zope3docs/ wording

Christian Theune ct at gocept.com
Thu Feb 19 12:28:24 EST 2009


Log message for revision 96782:
  wording
  

Changed:
  _U  zope3docs/
  U   zope3docs/source/codingstyle/index.rst

-=-

Property changes on: zope3docs
___________________________________________________________________
Modified: bzr:revision-info
   - timestamp: 2009-02-19 11:50:34.569000006 +0100
committer: Christian Theune <ct at gocept.com>
properties: 
	branch-nick: zope3docs.bzr

   + timestamp: 2009-02-19 14:34:02.355999947 +0100
committer: Christian Theune <ct at gocept.com>
properties: 
	branch-nick: zope3docs.bzr

Modified: bzr:file-ids
   - source/codingstyle/zcml-style.rst	96696 at 62d5b8a3-27da-0310-9561-8e5933582275:zope3docs:source%2Fcodingstyle%2Fzcml-style.rst

   + source/codingstyle/index.rst	96696 at 62d5b8a3-27da-0310-9561-8e5933582275:zope3docs:source%2Fcodingstyle%2Findex.rst

Modified: bzr:revision-id:v3-single-zope3docs
   - 16 ct at gocept.com-20090219095131-k60befy2nrfx9q99
17 ct at gocept.com-20090219101837-g1g0cg0op0o8a104
18 ct at gocept.com-20090219104745-nh3531xbm8hsd2v9
19 ct at gocept.com-20090219105006-0mre3cx94v8awk9m
20 ct at gocept.com-20090219105021-qywg1ei5q6a21223
21 ct at gocept.com-20090219105034-je5udw7hy1r7xel5

   + 16 ct at gocept.com-20090219095131-k60befy2nrfx9q99
17 ct at gocept.com-20090219101837-g1g0cg0op0o8a104
18 ct at gocept.com-20090219104745-nh3531xbm8hsd2v9
19 ct at gocept.com-20090219105006-0mre3cx94v8awk9m
20 ct at gocept.com-20090219105021-qywg1ei5q6a21223
21 ct at gocept.com-20090219105034-je5udw7hy1r7xel5
22 ct at gocept.com-20090219133402-h5djqf2t1nfow9k3


Modified: zope3docs/source/codingstyle/index.rst
===================================================================
--- zope3docs/source/codingstyle/index.rst	2009-02-19 17:28:22 UTC (rev 96781)
+++ zope3docs/source/codingstyle/index.rst	2009-02-19 17:28:24 UTC (rev 96782)
@@ -1,9 +1,9 @@
 Coding style
 ============
 
-The coding style is intended to support a more consistent code base by
-laying out rules for how to work with Zope 3 code, for example how to
-structure files, format your source code and naming things.
+The coding style is intended to support a consistent code base by laying
+out rules for how to work on Zope 3 code, for example how to structure
+files, format your source code and naming things.
 
 .. note::
     TODO This area includes code from the original Zope 3 wiki and needs



More information about the Checkins mailing list