summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCasey Duncan <casey.duncan@gmail.com>2011-01-15 22:07:07 -0700
committerCasey Duncan <casey.duncan@gmail.com>2011-01-15 22:07:07 -0700
commit93d5dbd2bc8890a771425a8cd7f6dcd5aad66d58 (patch)
tree73e75076f529565cf75f9c69ef6fb8f6415cba0b
parent82e0452f9c71ddd71489cca74f6070dada94e5dd (diff)
downloadpyramid-93d5dbd2bc8890a771425a8cd7f6dcd5aad66d58.tar.gz
pyramid-93d5dbd2bc8890a771425a8cd7f6dcd5aad66d58.tar.bz2
pyramid-93d5dbd2bc8890a771425a8cd7f6dcd5aad66d58.zip
reword security intro paragraph
-rw-r--r--docs/narr/security.rst11
1 files changed, 6 insertions, 5 deletions
diff --git a/docs/narr/security.rst b/docs/narr/security.rst
index 43b5aaa19..814f232d7 100644
--- a/docs/narr/security.rst
+++ b/docs/narr/security.rst
@@ -6,11 +6,12 @@
Security
========
-:app:`Pyramid` provides an optional declarative authorization system that
-prevents a :term:`view` from being invoked when the user represented by
-credentials in the :term:`request` does not have an appropriate level of
-access when a particular resource is the :term:`context`. Here's how it
-works at a high level:
+:app:`Pyramid` provides an optional declarative authorization system
+that prevents a :term:`view` from being invoked based on an
+:term:`authorization policy`. Before a view is invoked, the
+authorization system can use the credentials in the :term:`request`
+along with the :term:`context` resource to determine if access will be
+allowed. Here's how it works at a high level:
- A :term:`request` is generated when a user visits the application.