From 39ae8d740e30c18e46873cf82aff76588f1974c7 Mon Sep 17 00:00:00 2001 From: Mariusz Felisiak Date: Thu, 17 Mar 2022 11:10:03 +0100 Subject: [PATCH] Added missing backticks to function names. --- docs/ref/models/querysets.txt | 4 ++-- docs/ref/utils.txt | 3 ++- docs/releases/0.95.txt | 6 +++--- docs/releases/1.7.txt | 6 +++--- docs/topics/db/examples/many_to_one.txt | 2 +- docs/topics/db/sql.txt | 2 +- docs/topics/forms/modelforms.txt | 4 ++-- 7 files changed, 14 insertions(+), 13 deletions(-) diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index 8311b63f7e..94614aad72 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -1618,8 +1618,8 @@ one, doing so will result in an error. the full set of fields for the model will be significant. Even if you think you are in the advanced use-case situation, **only use - defer() when you cannot, at queryset load time, determine if you will need - the extra fields or not**. If you are frequently loading and using a + ``defer()`` when you cannot, at queryset load time, determine if you will + need the extra fields or not**. If you are frequently loading and using a particular subset of your data, the best choice you can make is to normalize your models and put the non-loaded data into a separate model (and database table). If the columns *must* stay in the one table for some diff --git a/docs/ref/utils.txt b/docs/ref/utils.txt index 39c8e341ad..8c12294cd6 100644 --- a/docs/ref/utils.txt +++ b/docs/ref/utils.txt @@ -332,7 +332,8 @@ https://web.archive.org/web/20110718035220/http://diveintomark.org/archives/2004 .. class:: SyndicationFeed - Base class for all syndication feeds. Subclasses should provide write(). + Base class for all syndication feeds. Subclasses should provide + ``write()``. .. method:: __init__(title, link, description, language=None, author_email=None, author_name=None, author_link=None, subtitle=None, categories=None, feed_url=None, feed_copyright=None, feed_guid=None, ttl=None, **kwargs) diff --git a/docs/releases/0.95.txt b/docs/releases/0.95.txt index 5edb043b0a..9ba89dd919 100644 --- a/docs/releases/0.95.txt +++ b/docs/releases/0.95.txt @@ -71,9 +71,9 @@ The new features and changes introduced in 0.95 include: URLconfs/views on their own. Previously, the framework required that a database be configured, regardless of whether you actually used it. -* It's now more explicit and natural to override save() and delete() - methods on models, rather than needing to hook into the pre_save() and - post_save() method hooks. +* It's now more explicit and natural to override ``save()`` and ``delete()`` + methods on models, rather than needing to hook into the ``pre_save()`` and + ``post_save()`` method hooks. * Individual pieces of the framework now can be configured without requiring the setting of an environment variable. This permits use of, diff --git a/docs/releases/1.7.txt b/docs/releases/1.7.txt index 9263a5ab58..a57916bfb0 100644 --- a/docs/releases/1.7.txt +++ b/docs/releases/1.7.txt @@ -976,12 +976,12 @@ every time you change the schema. Additionally, like the rest of Django's old ``syncdb`` code, ``initial_data`` has been started down the deprecation path and will be removed in Django 1.9. -deconstruct() and serializability ---------------------------------- +``deconstruct()`` and serializability +------------------------------------- Django now requires all Field classes and all of their constructor arguments to be serializable. If you modify the constructor signature in your custom -Field in any way, you'll need to implement a deconstruct() method; +Field in any way, you'll need to implement a ``deconstruct()`` method; we've expanded the custom field documentation with :ref:`instructions on implementing this method `. diff --git a/docs/topics/db/examples/many_to_one.txt b/docs/topics/db/examples/many_to_one.txt index b9142243f9..bb4202ab66 100644 --- a/docs/topics/db/examples/many_to_one.txt +++ b/docs/topics/db/examples/many_to_one.txt @@ -169,7 +169,7 @@ Querying in the opposite direction:: >>> Reporter.objects.filter(article__headline__startswith='This').distinct() ]> -Counting in the opposite direction works in conjunction with distinct():: +Counting in the opposite direction works in conjunction with ``distinct()``:: >>> Reporter.objects.filter(article__headline__startswith='This').count() 3 diff --git a/docs/topics/db/sql.txt b/docs/topics/db/sql.txt index 4713fb6d50..0f4d6c3880 100644 --- a/docs/topics/db/sql.txt +++ b/docs/topics/db/sql.txt @@ -165,7 +165,7 @@ fields that are omitted from the query will be loaded on demand. For example:: From outward appearances, this looks like the query has retrieved both the first name and last name. However, this example actually issued 3 -queries. Only the first names were retrieved by the raw() query -- the +queries. Only the first names were retrieved by the ``raw()`` query -- the last names were both retrieved on demand when they were printed. There is only one field that you can't leave out - the primary key diff --git a/docs/topics/forms/modelforms.txt b/docs/topics/forms/modelforms.txt index ad0ab35231..26a5fc8b0f 100644 --- a/docs/topics/forms/modelforms.txt +++ b/docs/topics/forms/modelforms.txt @@ -247,8 +247,8 @@ validation step, right after the form's ``clean()`` method is called. .. _overriding-modelform-clean-method: -Overriding the clean() method -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +Overriding the ``clean()`` method +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ You can override the ``clean()`` method on a model form to provide additional validation in the same way you can on a normal form.