summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorPavlo Kapyshin <i@93z.org>2015-01-07 14:51:45 +0200
committerPavlo Kapyshin <i@93z.org>2015-01-07 14:51:45 +0200
commit99d7c44610ad56bac0e90ba119b003ef11b2eb5a (patch)
treeae179b87be246c96cbf6ec09c70e38d785410213 /docs
parentb6ad615549fb52c40f55760027bffbdd1a919aa1 (diff)
downloadpyramid-99d7c44610ad56bac0e90ba119b003ef11b2eb5a.tar.gz
pyramid-99d7c44610ad56bac0e90ba119b003ef11b2eb5a.tar.bz2
pyramid-99d7c44610ad56bac0e90ba119b003ef11b2eb5a.zip
Fix rendering
Diffstat (limited to 'docs')
-rw-r--r--docs/narr/sessions.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/narr/sessions.rst b/docs/narr/sessions.rst
index 8da743a01..f20a36d81 100644
--- a/docs/narr/sessions.rst
+++ b/docs/narr/sessions.rst
@@ -44,7 +44,7 @@ It is digitally signed, however, and thus its data cannot easily be
tampered with.
You can configure this session factory in your :app:`Pyramid` application
-by using the :meth:`pyramid.config.Configurator.set_session_factory`` method.
+by using the :meth:`pyramid.config.Configurator.set_session_factory` method.
.. code-block:: python
:linenos:
@@ -380,7 +380,7 @@ Checking CSRF Tokens Manually
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In request handling code, you can check the presence and validity of a CSRF
-token with :func:`pyramid.session.check_csrf_token(request)``. If the token is
+token with ``pyramid.session.check_csrf_token(request)``. If the token is
valid, it will return ``True``, otherwise it will raise ``HTTPBadRequest``.
Optionally, you can specify ``raises=False`` to have the check return ``False``
instead of raising an exception.