CONN-38 Notes for 3.28.0 on PYTHON-1350 (#1167)

Co-authored-by: Jamie Gillenwater <jamie.gillenwater@datastax.com>

Author: absurdfarce

docs/column_encryption.rst

@@ -14,19 +14,11 @@ also available, although in this case values must be manually encrypted and/or d
 Client-side encryption and decryption should work against all versions of Cassandra and DSE.  It does not
 utilize any server-side functionality to do its work.
 
-WARNING: Consider upgrading to 3.28.0 or later
+WARNING: Encryption format changes in 3.28.0
 ------------------------------------------------
-There is a significant issue with the column encryption functionality in Python driver 3.27.0.
-To be able to decrypt your data, you must preserve the cipher initialization vector (IV) used by 
-the :class:`~.AES256ColumnEncryptionPolicy` when your data was written.
-To decrypt your data, you must supply this IV when creating a policy to read this data.
-If you do not supply this IV in the policy to read this data, you will **NOT BE ABLE TO DECRYPT YOUR DATA**. 
-See 
-`PYTHON-1350 <https://datastax-oss.atlassian.net/browse/PYTHON-1350>`_ for more detail. 
-
-DataStax recommends upgrading to Python driver 3.28.0 or later to avoid this issue. 3.28.0 or later manages the IV automatically.  
-Because of this change in functionality, any encrypted data written in 3.27.0 will **NOT** be readable by 3.28.0 or later. 
-After upgrading to Python driver 3.28.0 or later, it is critical that you re-encrypt your data with the new driver version.
+Python driver 3.28.0 introduces a new encryption format for data written by :class:`~.AES256ColumnEncryptionPolicy`.
+As a result, any encrypted data written by Python driver 3.27.0 will **NOT** be readable.
+If you upgraded from 3.27.0, you should re-encrypt your data with 3.28.0.
 
 Configuration
 -------------