aboutsummaryrefslogtreecommitdiffstats
path: root/docs/hazmat/primitives
diff options
context:
space:
mode:
authorAlex Gaynor <alex.gaynor@gmail.com>2014-12-19 13:19:17 -0800
committerAlex Gaynor <alex.gaynor@gmail.com>2014-12-19 13:19:17 -0800
commitc444254b756e0ecf33829cadb3427c6bc530740b (patch)
treed3c8c000e66e9cc1edfa2b9664520cb976ba0e90 /docs/hazmat/primitives
parent46cb9900a03b2921d8dafe0efed6856083b71706 (diff)
downloadcryptography-c444254b756e0ecf33829cadb3427c6bc530740b.tar.gz
cryptography-c444254b756e0ecf33829cadb3427c6bc530740b.tar.bz2
cryptography-c444254b756e0ecf33829cadb3427c6bc530740b.zip
Fixed reST mistake
Diffstat (limited to 'docs/hazmat/primitives')
-rw-r--r--docs/hazmat/primitives/asymmetric/rsa.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/hazmat/primitives/asymmetric/rsa.rst b/docs/hazmat/primitives/asymmetric/rsa.rst
index aa8a6fb1..7f902fff 100644
--- a/docs/hazmat/primitives/asymmetric/rsa.rst
+++ b/docs/hazmat/primitives/asymmetric/rsa.rst
@@ -79,7 +79,7 @@ Verification
The previous section describes what to do if you have a private key and want to
sign something. If you have a public key, a message, and a signature, you can
check that the public key genuinely was used to sign that specific message. You
-also need to know which signing algorithm was used::
+also need to know which signing algorithm was used:
.. doctest::