Code

Ticket #9497: doctypos-r9328.diff

File doctypos-r9328.diff, 8.8 KB (added by ramiro, 5 years ago)
Line 
1diff --git a/docs/faq/admin.txt b/docs/faq/admin.txt
2--- a/docs/faq/admin.txt
3+++ b/docs/faq/admin.txt
4@@ -31,7 +31,7 @@
5 How can I prevent the cache middleware from caching the admin site?
6 -------------------------------------------------------------------
7 
8-Set the :setting:``CACHE_MIDDLEWARE_ANONYMOUS_ONLY`` setting to ``True``. See the
9+Set the :setting:`CACHE_MIDDLEWARE_ANONYMOUS_ONLY` setting to ``True``. See the
10 :ref:`cache documentation <topics-cache>` for more information.
11 
12 How do I automatically set a field's value to the user who last edited the object in the admin?
13diff --git a/docs/ref/contrib/databrowse.txt b/docs/ref/contrib/databrowse.txt
14--- a/docs/ref/contrib/databrowse.txt
15+++ b/docs/ref/contrib/databrowse.txt
16@@ -35,7 +35,7 @@
17          more.
18 
19        * Otherwise, determine the full filesystem path to the
20-         `:file:`django/contrib/databrowse/templates` directory, and add that
21+         :file:`django/contrib/databrowse/templates` directory, and add that
22          directory to your :setting:`TEMPLATE_DIRS` setting.
23 
24     2. Register a number of models with the Databrowse site::
25diff --git a/docs/ref/contrib/sites.txt b/docs/ref/contrib/sites.txt
26--- a/docs/ref/contrib/sites.txt
27+++ b/docs/ref/contrib/sites.txt
28@@ -207,7 +207,7 @@
29 files for both the LJWorld.com and Lawrence.com template directories. That
30 gives you more flexibility, but it's also more complex.
31 
32-It's a good idea to exploit the :class:`~django.contrib.sites.models.Site``
33+It's a good idea to exploit the :class:`~django.contrib.sites.models.Site`
34 objects as much as possible, to remove unneeded complexity and redundancy.
35 
36 Getting the current domain for full URLs
37diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt
38--- a/docs/ref/databases.txt
39+++ b/docs/ref/databases.txt
40@@ -271,11 +271,11 @@
41 version of ``pysqlite2`` (``pysqlite-2.x.x.win32-py2.5.exe``) that includes and
42 uses a newer version of SQLite. Python 2.6 ships with a newer version of
43 SQLite and is not affected by this issue.
44-
45-If you are in such platform and find yourself in the need to update
46-``pysqlite``/SQLite, you will also need to manually modify the
47-``django/db/backends/sqlite3/base.py`` file in the Django source tree so it
48-attempts to import ``pysqlite2`` before that ``sqlite3`` and so it can take
49+
50+If you are in such platform and find yourself in the need to update
51+``pysqlite``/SQLite, you will also need to manually modify the
52+``django/db/backends/sqlite3/base.py`` file in the Django source tree so it
53+attempts to import ``pysqlite2`` before than ``sqlite3`` and so it can take
54 advantage of the new ``pysqlite2``/SQLite versions.
55 
56 .. _oracle-notes:
57diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
58--- a/docs/ref/models/querysets.txt
59+++ b/docs/ref/models/querysets.txt
60@@ -35,7 +35,7 @@
61 
62     * **Slicing.** As explained in :ref:`limiting-querysets`, a ``QuerySet`` can
63       be sliced, using Python's array-slicing syntax. Usually slicing a
64-      ``QuerySet`` returns another (unevaluated )``QuerySet``, but Django will
65+      ``QuerySet`` returns another (unevaluated ) ``QuerySet``, but Django will
66       execute the database query if you use the "step" parameter of slice
67       syntax.
68 
69@@ -627,7 +627,7 @@
70     .. versionadded:: 1.0
71 
72     In some rare cases, you might wish to pass parameters to the SQL fragments
73-    in ``extra(select=...)```. For this purpose, use the ``select_params``
74+    in ``extra(select=...)``. For this purpose, use the ``select_params``
75     parameter. Since ``select_params`` is a sequence and the ``select``
76     attribute is a dictionary, some care is required so that the parameters
77     are matched up correctly with the extra select pieces.  In this situation,
78diff --git a/docs/ref/models/relations.txt b/docs/ref/models/relations.txt
79--- a/docs/ref/models/relations.txt
80+++ b/docs/ref/models/relations.txt
81@@ -19,7 +19,7 @@
82         >>> e = Entry.objects.get(id=234)
83         >>> b.entry_set.add(e) # Associates Entry e with Blog b.
84 
85-.. method:: QuerySet.create(**kwargs)`
86+.. method:: QuerySet.create(**kwargs)
87 
88     Creates a new object, saves it and puts it in the related object set.
89     Returns the newly created object::
90@@ -73,5 +73,5 @@
91 
92     Note this doesn't delete the related objects -- it just disassociates them.
93 
94-    Just like ``remove()``, ``clear()`` is only available on ``ForeignKey``s
95+    Just like ``remove()``, ``clear()`` is only available on ``ForeignKey``\s
96     where ``null=True``.
97diff --git a/docs/ref/templates/api.txt b/docs/ref/templates/api.txt
98--- a/docs/ref/templates/api.txt
99+++ b/docs/ref/templates/api.txt
100@@ -294,7 +294,7 @@
101     })
102 
103 The second difference is that it automatically populates the context with a few
104-variables, according to your :setting:`TEMPLATE_CONTEXT_PROCESSORS` setting`.
105+variables, according to your :setting:`TEMPLATE_CONTEXT_PROCESSORS` setting.
106 
107 The :setting:`TEMPLATE_CONTEXT_PROCESSORS` setting is a tuple of callables --
108 called **context processors** -- that take a request object as their argument
109@@ -384,7 +384,7 @@
110 
111     * ``LANGUAGES`` -- The value of the :setting:`LANGUAGES` setting.
112     * ``LANGUAGE_CODE`` -- ``request.LANGUAGE_CODE``, if it exists. Otherwise,
113-      the value of the :setting:`LANGUAGE_CODE` setting`.
114+      the value of the :setting:`LANGUAGE_CODE` setting.
115 
116 See :ref:`topics-i18n` for more.
117 
118diff --git a/docs/topics/auth.txt b/docs/topics/auth.txt
119--- a/docs/topics/auth.txt
120+++ b/docs/topics/auth.txt
121@@ -687,7 +687,7 @@
122           a query string, too.
123 
124         * ``site_name``: The name of the current
125-          :class:`~django.contrib.sites.models.Site``, according to the
126+          :class:`~django.contrib.sites.models.Site`, according to the
127           :setting:`SITE_ID` setting. If you're using the Django development version
128           and you don't have the site framework installed, this will be set to the
129           value of ``request.META['SERVER_NAME']``. For more on sites, see
130diff --git a/docs/topics/http/file-uploads.txt b/docs/topics/http/file-uploads.txt
131--- a/docs/topics/http/file-uploads.txt
132+++ b/docs/topics/http/file-uploads.txt
133@@ -153,8 +153,8 @@
134             ``0`` is very important: it indicates an octal number, which is the
135             way that modes must be specified. If you try to use ``644``, you'll
136             get totally incorrect behavior.
137-           
138-            **Always prefix the mode with a ``0``.**
139+
140+            **Always prefix the mode with a 0.**
141 
142     :setting:`FILE_UPLOAD_HANDLERS`
143         The actual handlers for uploaded files. Changing this setting allows
144diff --git a/docs/topics/http/urls.txt b/docs/topics/http/urls.txt
145--- a/docs/topics/http/urls.txt
146+++ b/docs/topics/http/urls.txt
147@@ -50,7 +50,7 @@
148     
149     4. Once one of the regexes matches, Django imports and calls the given
150        view, which is a simple Python function. The view gets passed an
151-       :class:`~django.http.HttpRequest`` as its first argument and any values
152+       :class:`~django.http.HttpRequest` as its first argument and any values
153        captured in the regex as remaining arguments.
154 
155 Example
156diff --git a/docs/topics/i18n.txt b/docs/topics/i18n.txt
157--- a/docs/topics/i18n.txt
158+++ b/docs/topics/i18n.txt
159@@ -298,7 +298,8 @@
160       currently active locale).
161 
162     * ``LANGUAGE_CODE`` is the current user's preferred language, as a string.
163-      Example: ``en-us``. (See "How language preference is discovered", below.)
164+      Example: ``en-us``. (See :ref:`how-django-discovers-language-preference`,
165+      below.)
166 
167     * ``LANGUAGE_BIDI`` is the current locale's direction. If True, it's a
168       right-to-left language, e.g.: Hebrew, Arabic. If False it's a
169@@ -514,7 +515,7 @@
170       out empty, so it's your responsibility to change it. Make sure you keep
171       the quotes around your translation.
172     * As a convenience, each message includes, in the form of a comment line
173-      prefixed with ``#`` and locted above the ``msgid`` line, the filename and
174+      prefixed with ``#`` and located above the ``msgid`` line, the filename and
175       line number from which the translation string was gleaned.
176 
177 Long messages are a special case. There, the first string directly after the
178@@ -565,6 +566,8 @@
179    If you're using Windows and need to install the GNU gettext utilities so
180    ``django-admin compilemessages`` works see `gettext on Windows`_ for more
181    information.
182+
183+.. _how-django-discovers-language-preference:
184 
185 3. How Django discovers language preference
186 ===========================================
187@@ -783,7 +786,6 @@
188 
189 The easiest way out is to store applications that are not part of the project
190 (and so carry their own translations) outside the project tree. That way,
191-
192 ``django-admin.py makemessages`` on the project level will only translate
193 strings that are connected to your explicit project and not strings that are
194 distributed independently.