Fixed #25755 -- Unified spelling of "website".

This commit is contained in:
Agnieszka Lasyk 2015-11-15 13:05:15 +01:00 committed by Tim Graham
parent 53326e2c8a
commit 1f8dad6915
33 changed files with 55 additions and 55 deletions

View file

@ -11,7 +11,7 @@ Working with forms
the forms API, see :doc:`/ref/forms/api`, :doc:`/ref/forms/fields`, and
:doc:`/ref/forms/validation`.
Unless you're planning to build Web sites and applications that do nothing but
Unless you're planning to build websites and applications that do nothing but
publish content, and don't accept input from your visitors, you're going to
need to understand and use forms.
@ -172,7 +172,7 @@ example with:
* data received from a previous HTML form submission
The last of these cases is the most interesting, because it's what makes it
possible for users not just to read a Web site, but to send information back
possible for users not just to read a website, but to send information back
to it too.
Building a form
@ -181,7 +181,7 @@ Building a form
The work that needs to be done
------------------------------
Suppose you want to create a simple form on your Web site, in order to obtain
Suppose you want to create a simple form on your website, in order to obtain
the user's name. You'd need something like this in your template:
.. code-block:: html+django
@ -269,7 +269,7 @@ We'll have to provide those ourselves in the template.
The view
^^^^^^^^
Form data sent back to a Django Web site is processed by a view, generally the
Form data sent back to a Django website is processed by a view, generally the
same view which published the form. This allows us to reuse some of the same
logic.
@ -400,7 +400,7 @@ More on fields
--------------
Consider a more useful form than our minimal example above, which we could use
to implement "contact me" functionality on a personal Web site:
to implement "contact me" functionality on a personal website:
.. snippet::
:filename: forms.py