From 4a954cfd11a5d034491f87fcbc920eb97a302bb3 Mon Sep 17 00:00:00 2001 From: Tobias Kunze Date: Mon, 17 Jun 2019 16:54:55 +0200 Subject: Fixed #30573 -- Rephrased documentation to avoid words that minimise the involved difficulty. This patch does not remove all occurrences of the words in question. Rather, I went through all of the occurrences of the words listed below, and judged if they a) suggested the reader had some kind of knowledge/experience, and b) if they added anything of value (including tone of voice, etc). I left most of the words alone. I looked at the following words: - simply/simple - easy/easier/easiest - obvious - just - merely - straightforward - ridiculous Thanks to Carlton Gibson for guidance on how to approach this issue, and to Tim Bell for providing the idea. But the enormous lion's share of thanks go to Adam Johnson for his patient and helpful review. --- docs/topics/forms/formsets.txt | 10 +++++----- docs/topics/forms/index.txt | 16 +++++++--------- docs/topics/forms/media.txt | 7 +++---- docs/topics/forms/modelforms.txt | 19 +++++++++---------- 4 files changed, 24 insertions(+), 28 deletions(-) (limited to 'docs/topics/forms') diff --git a/docs/topics/forms/formsets.txt b/docs/topics/forms/formsets.txt index 84635457ff..8a630f6c9f 100644 --- a/docs/topics/forms/formsets.txt +++ b/docs/topics/forms/formsets.txt @@ -569,8 +569,8 @@ Adding additional fields to a formset If you need to add additional fields to the formset this can be easily accomplished. The formset base class provides an ``add_fields`` method. You -can simply override this method to add your own fields or even redefine the -default fields/attributes of the order and deletion fields:: +can override this method to add your own fields or even redefine the default +fields/attributes of the order and deletion fields:: >>> from django.forms import BaseFormSet >>> from django.forms import formset_factory @@ -651,9 +651,9 @@ This is useful if you want to :ref:`use more than one formset in a view Using a formset in views and templates ====================================== -Using a formset inside a view is as easy as using a regular ``Form`` class. -The only thing you will want to be aware of is making sure to use the -management form inside the template. Let's look at a sample view:: +Using a formset inside a view is not very different from using a regular +``Form`` class. The only thing you will want to be aware of is making sure to +use the management form inside the template. Let's look at a sample view:: from django.forms import formset_factory from django.shortcuts import render diff --git a/docs/topics/forms/index.txt b/docs/topics/forms/index.txt index 6cf1570ab0..b6c6df0c16 100644 --- a/docs/topics/forms/index.txt +++ b/docs/topics/forms/index.txt @@ -26,11 +26,11 @@ allow a visitor to do things like enter text, select options, manipulate objects or controls, and so on, and then send that information back to the server. -Some of these form interface elements - text input or checkboxes - are fairly -simple and are built into HTML itself. Others are much more complex; an -interface that pops up a date picker or allows you to move a slider or -manipulate controls will typically use JavaScript and CSS as well as HTML form -```` elements to achieve these effects. +Some of these form interface elements - text input or checkboxes - are built +into HTML itself. Others are much more complex; an interface that pops up a +date picker or allows you to move a slider or manipulate controls will +typically use JavaScript and CSS as well as HTML form ```` elements to +achieve these effects. As well as its ```` elements, a form must specify two things: @@ -326,8 +326,7 @@ telling it where to go next. The template ~~~~~~~~~~~~ -We don't need to do much in our ``name.html`` template. The simplest example -is: +We don't need to do much in our ``name.html`` template: .. code-block:: html+django @@ -671,8 +670,7 @@ Useful attributes on ``{{ field }}`` include: Outputs a ``