Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Fixed #2769 -- Applied some ReST formatting fixes. Thanks, ramiro.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@3774 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
commit e947fb2111c575b6005c9a291c25d85a959e8b1f 1 parent d296e5e
Malcolm Tredinnick authored September 21, 2006
1  AUTHORS
@@ -122,6 +122,7 @@ answer newbie questions, and generally made Django that much better:
122 122
     Daniel Poelzleithner <http://poelzi.org/>
123 123
     J. Rademaker
124 124
     Michael Radziej <mir@noris.de>
  125
+    ramiro
125 126
     Brian Ray <http://brianray.chipy.org/>
126 127
     rhettg@gmail.com
127 128
     Oliver Rutherfurd <http://rutherfurd.net/>
2  docs/db-api.txt
@@ -1511,7 +1511,7 @@ Many-to-many relationships
1511 1511
 --------------------------
1512 1512
 
1513 1513
 Both ends of a many-to-many relationship get automatic API access to the other
1514  
-end. The API works just as a "backward" one-to-many relationship. See _Backward
  1514
+end. The API works just as a "backward" one-to-many relationship. See Backward_
1515 1515
 above.
1516 1516
 
1517 1517
 The only difference is in the attribute naming: The model that defines the
6  docs/forms.txt
@@ -136,7 +136,7 @@ template::
136 136
     {% endblock %}
137 137
 
138 138
 Before we get back to the problems with these naive set of views, let's go over
139  
-some salient points of the above template::
  139
+some salient points of the above template:
140 140
 
141 141
     * Field "widgets" are handled for you: ``{{ form.field }}`` automatically
142 142
       creates the "right" type of widget for the form, as you can see with the
@@ -148,8 +148,8 @@ some salient points of the above template::
148 148
       If you must use tables, use tables. If you're a semantic purist, you can
149 149
       probably find better HTML than in the above template.
150 150
 
151  
-    * To avoid name conflicts, the ``id``s of form elements take the form
152  
-      "id_*fieldname*".
  151
+    * To avoid name conflicts, the ``id`` values of form elements take the
  152
+      form "id_*fieldname*".
153 153
 
154 154
 By creating a creation form we've solved problem number 3 above, but we still
155 155
 don't have any validation. Let's revise the validation issue by writing a new

0 notes on commit e947fb2

Please sign in to comment.
Something went wrong with that request. Please try again.