From 283494c2338dbd6e89a7da79a05318992ee04cfc Mon Sep 17 00:00:00 2001 From: Paul Winkler Date: Fri, 24 Feb 2012 14:24:50 -0500 Subject: More trivial typos --- docs/api/security.rst | 4 ++-- docs/designdefense.rst | 4 ++-- docs/narr/viewconfig.rst | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) (limited to 'docs') diff --git a/docs/api/security.rst b/docs/api/security.rst index 7086690e9..814b68e5a 100644 --- a/docs/api/security.rst +++ b/docs/api/security.rst @@ -72,13 +72,13 @@ Return Values The ACE "action" (the first element in an ACE e.g. ``(Allow, Everyone, 'read')`` that means allow access. A sequence of ACEs makes up an - ACL. It is a string, and it's actual value is "Allow". + ACL. It is a string, and its actual value is "Allow". .. attribute:: Deny The ACE "action" (the first element in an ACE e.g. ``(Deny, 'george', 'read')`` that means deny access. A sequence of ACEs - makes up an ACL. It is a string, and it's actual value is "Deny". + makes up an ACL. It is a string, and its actual value is "Deny". .. autoclass:: ACLDenied :members: diff --git a/docs/designdefense.rst b/docs/designdefense.rst index 84b6be907..bbcf9c2ec 100644 --- a/docs/designdefense.rst +++ b/docs/designdefense.rst @@ -1386,7 +1386,7 @@ predictability. actually the best-case circumstance for double-imports; if a module only mutates itself and its contents at import time, if it is imported twice, that's OK, because each decorator invocation will always be mutating an - independent copy of the object its attached to, not a shared resource like + independent copy of the object it's attached to, not a shared resource like a registry in another module. This has the effect that double-registrations will never be performed. @@ -1727,7 +1727,7 @@ reads something like this: (Paraphrased from a real email, actually.) -Let's take this criticism point-by point. +Let's take this criticism point-by-point. Too Complex +++++++++++ diff --git a/docs/narr/viewconfig.rst b/docs/narr/viewconfig.rst index 763c0e131..23b4fde68 100644 --- a/docs/narr/viewconfig.rst +++ b/docs/narr/viewconfig.rst @@ -900,7 +900,7 @@ When a non-``None`` ``http_cache`` argument is passed to a view configuration, Pyramid will set ``Expires`` and ``Cache-Control`` response headers in the resulting response, causing browsers to cache the response data for some time. See ``http_cache`` in :ref:`nonpredicate_view_args` for -the its allowable values and what they mean. +the allowable values and what they mean. Sometimes it's undesirable to have these headers set as the result of returning a response from a view, even though you'd like to decorate the view -- cgit v1.2.3