diff --git a/docs/column_encryption.rst b/docs/column_encryption.rst
index 289f9cd62..1392972fa 100644
--- a/docs/column_encryption.rst
+++ b/docs/column_encryption.rst
@@ -21,6 +21,7 @@ and adding information about columns to be encrypted to it.  This policy is then
 when it's created.
 
 .. code-block:: python
+
     import os
 
     from cassandra.policies import ColDesc, AES256ColumnEncryptionPolicy, AES256_KEY_SIZE_BYTES
@@ -57,6 +58,7 @@ supplied parameters.  For example, we can create a prepared statement to insert
 by executing the following code after creating a :class:`~.Cluster` in the manner described above:
 
 .. code-block:: python
+
     session = cluster.connect()
     prepared = session.prepare("insert into ks1.table1 (column1) values (?)")
     session.execute(prepared, (1000,))
@@ -70,6 +72,7 @@ standard serialization methods employed by the driver.  The result is then encry
 of the policy.  Using this approach the example above could be implemented along the lines of the following:
 
 .. code-block:: python
+
     session = cluster.connect()
     session.execute("insert into ks1.table1 (column1) values (%s)",(cl_policy.encode_and_encrypt(col_desc, 1000),))
 
@@ -88,4 +91,4 @@ of the cryptography package, although wheels exist for many common platforms.
 
 Client-side encryption has been implemented for both the default Cython and pure Python row processing logic.
 This functionality has not yet been ported to the NumPy Cython implementation.  During testing,
-the NumPy processing works on Python 3.7 but fails for Python 3.8.
\ No newline at end of file
+the NumPy processing works on Python 3.7 but fails for Python 3.8.