[Checkins] SVN: zope3docs/ Fix ReST warnings.

[Christian Theune]

Log message for revision 96731:
  Fix ReST warnings.
  

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

-=-

Property changes on: zope3docs
___________________________________________________________________
Added: bzr:revision-info
   + timestamp: 2009-02-19 10:51:31.335999966 +0100
committer: Christian Theune <ct at gocept.com>
properties: 
	branch-nick: zope3docs.bzr

Added: bzr:file-ids
   + source/codingstyle/writingtests.rst	96696 at 62d5b8a3-27da-0310-9561-8e5933582275:zope3docs:source%2Fcodingstyle%2Fwritingtests.rst

Added: bzr:text-parents
   + 
Added: bzr:revision-id:v3-single-zope3docs
   + 16 ct at gocept.com-20090219095131-k60befy2nrfx9q99


Modified: zope3docs/source/codingstyle/writingtests.rst
===================================================================
--- zope3docs/source/codingstyle/writingtests.rst	2009-02-19 09:32:35 UTC (rev 96730)
+++ zope3docs/source/codingstyle/writingtests.rst	2009-02-19 09:52:41 UTC (rev 96731)
@@ -47,9 +47,9 @@
 
 Within the unit tests themselves, the Zope3 style is to use
 the positive rather than the double negative assertions.
-Thus, use 'assertEqual' rather than 'failUnlessEqual', 
-'assertRaises' rather than 'failUnlessRaises', and 'assert_'
-rather than 'failUnless'.  (Yes, 'assert_' is an ugly name,
+Thus, use ``assertEqual`` rather than ``failUnlessEqual``, 
+``assertRaises`` rather than ``failUnlessRaises``, and ``assert_``
+rather than ``failUnless``.  (Yes, ``assert_`` is an ugly name,
 but it is still preferred.)
 
 There are certain other "Best Practices" the following of which