summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorCasey Duncan <casey.duncan@gmail.com>2010-12-02 23:15:36 -0700
committerCasey Duncan <casey.duncan@gmail.com>2010-12-02 23:15:36 -0700
commit19c9224cfdebfd6e7ba8d13cb7e0c974bd4ac71f (patch)
tree149ade2462f8b25e7724fbf6df08548a1c06daff /docs
parent150a32920d364fdd2de0f4005dd5fb995cba7692 (diff)
downloadpyramid-19c9224cfdebfd6e7ba8d13cb7e0c974bd4ac71f.tar.gz
pyramid-19c9224cfdebfd6e7ba8d13cb7e0c974bd4ac71f.tar.bz2
pyramid-19c9224cfdebfd6e7ba8d13cb7e0c974bd4ac71f.zip
change For example to As an example
Diffstat (limited to 'docs')
-rw-r--r--docs/narr/views.rst19
1 files changed, 9 insertions, 10 deletions
diff --git a/docs/narr/views.rst b/docs/narr/views.rst
index 29adc5f14..cecba9f7a 100644
--- a/docs/narr/views.rst
+++ b/docs/narr/views.rst
@@ -1030,16 +1030,15 @@ via the ``request.params``, ``request.GET``, or ``request.POST`` APIs
.. note::
Many people find the difference between Unicode and UTF-8 confusing.
- Unicode is a standard for representing text that supports most of
- the world's writing systems. However, there are many ways that Unicode
- data can be encoded into bytes for transmittal and storage. UTF-8
- is a specific encoding for Unicode, that is backwards-compatible
- with ASCII. This makes UTF-8 very convenient for encoding data
- where a large subset of that data is ASCII characters, which is
- largely true on the web. UTF-8 is also the standard character
- encoding for URLs.
-
-For example, let's assume that the following form page is served up to
+ Unicode is a standard for representing text that supports most of the
+ world's writing systems. However, there are many ways that Unicode
+ data can be encoded into bytes for transmittal and storage. UTF-8 is
+ a specific encoding for Unicode, that is backwards-compatible with
+ ASCII. This makes UTF-8 very convenient for encoding data where a
+ large subset of that data is ASCII characters, which is largely true
+ on the web. UTF-8 is also the standard character encoding for URLs.
+
+As an example, let's assume that the following form page is served up to
a browser client, and its ``action`` points at some :app:`Pyramid`
view code: