Gardening...

Author: maria-robobug

modules/project-docs/pages/sdk-release-notes.adoc

@@ -17,7 +17,8 @@ The full installation instructions that were previously on this page can now be
 
 == Version 3.3.1 (29 April 2022)
 
-Version 3.3.1 is the second release of the 3.2 series. It contains a single ticket (NCBC-3192) and is a re-release of 3.3.0 with (NCBC-3192) along with all of 3.3.0.
+Version 3.3.1 is the second release of the 3.3 series.
+It is a re-release of `3.3.0` containing an additional critical fix (NCBC-3192) impacting TLS/SSL.
 
 https://packages.couchbase.com/clients/net/3.3/Couchbase-Net-Client-3.3.1.zip[Download] |
 https://docs.couchbase.com/sdk-api/couchbase-net-client-3.3.1[API Reference] |
@@ -31,10 +32,13 @@ If you encounter a similar situation during migration and need help with mitigat
 
 === Fixed Issues
 
-* https://issues.couchbase.com/browse/NCBC-2543[NCBC-3192]: Erroneous InvalidArgumentException with default TLS settings
+* https://issues.couchbase.com/browse/NCBC-3192[NCBC-3192]:
+Fixed erroneous `InvalidArgumentException` with default TLS settings.
 
 == Version 3.3.0 (27 April 2022)
 
+WARNING: Do not use; use `3.3.1` instead due to NCBC-3192 which impacts TLS/SSL.
+
 Version 3.3.0 is the first release of the 3.3 series (delisted from NuGet 4/28/2022).
 
 https://packages.couchbase.com/clients/net/3.3/Couchbase-Net-Client-3.3.0.zip[Download] |
@@ -43,8 +47,6 @@ https://www.nuget.org/packages/CouchbaseNetClient/3.3.0[Nuget]
 
 === Special Note
 
-* Do not use; use 3.3.1 instead due to NCBC-3192 which impacts TLS/SSL.
-
 * During a rebalance upgrade from 6.x (or any earlier version) to 7x, in mixed mode (where you are communicating with Couchbase Server whilst some but not all nodes are upgraded), there is a known issue where data may be written to the wrong location.  
 The solution is to either upgrade to 3.2.9 or greater, or to quiesce application processing so there are no writes until you have upgraded all nodes.  
 If you encounter a similar situation during migration and need help with mitigation, please contact our support team.