aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAlex Gaynor <alex.gaynor@gmail.com>2014-06-25 10:24:03 -0700
committerAlex Gaynor <alex.gaynor@gmail.com>2014-06-25 10:24:03 -0700
commitd99fc650967456d63beee80c5637e5e9de8fca6f (patch)
tree5effb27a3a5ad6fa538804fe1addd22d0084854a
parent0690f91e01472f0b233a74ddd0c5d4211e14ea68 (diff)
downloadcryptography-d99fc650967456d63beee80c5637e5e9de8fca6f.tar.gz
cryptography-d99fc650967456d63beee80c5637e5e9de8fca6f.tar.bz2
cryptography-d99fc650967456d63beee80c5637e5e9de8fca6f.zip
Use the short link version for various things
-rw-r--r--docs/hazmat/primitives/symmetric-encryption.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/hazmat/primitives/symmetric-encryption.rst b/docs/hazmat/primitives/symmetric-encryption.rst
index bcb1fb35..abc2b076 100644
--- a/docs/hazmat/primitives/symmetric-encryption.rst
+++ b/docs/hazmat/primitives/symmetric-encryption.rst
@@ -430,9 +430,9 @@ Interfaces
make a message the correct size. ``CipherContext`` will not automatically
apply any padding; you'll need to add your own. For block ciphers the
recommended padding is
- :class:`cryptography.hazmat.primitives.padding.PKCS7`. If you are using a
+ :class:`~cryptography.hazmat.primitives.padding.PKCS7`. If you are using a
stream cipher mode (such as
- :class:`cryptography.hazmat.primitives.modes.CTR`) you don't have to worry
+ :class:`~cryptography.hazmat.primitives.modes.CTR`) you don't have to worry
about this.
.. method:: update(data)
@@ -443,7 +443,7 @@ Interfaces
When the ``Cipher`` was constructed in a mode that turns it into a
stream cipher (e.g.
- :class:`cryptography.hazmat.primitives.ciphers.modes.CTR`), this will
+ :class:`~cryptography.hazmat.primitives.ciphers.modes.CTR`), this will
return bytes immediately, however in other modes it will return chunks
whose size is determined by the cipher's block size.