DOCSP-13383 certificate verbiage update (#207)

* DOCSP-13383 certificate verbiage update

* Rewrapping lines 200-205

* Address Jason's comments #1

Author: ianf-mongodb

source/core/security-transport-encryption.txt

@@ -198,13 +198,14 @@ To use TLS/SSL with MongoDB , you must have the TLS/SSL certificates as
 :file:`PEM` files, which are concatenated certificate containers.
 
 MongoDB can use any valid TLS/SSL certificate issued by a certificate
-authority or a self-signed certificate. If you use a self-signed
-certificate, although the communications channel will be encrypted,
-there will be *no* validation of server identity. Although such a
-situation will prevent eavesdropping on the connection, it leaves you
-vulnerable to a man-in-the-middle attack. Using a certificate signed by
-a trusted certificate authority will permit MongoDB drivers to verify
-the server's identity.
+authority or a self-signed certificate. For production use, your MongoDB
+deployment should use valid certificates generated and signed by the 
+same certificate authority. You can generate and maintain an independent
+certificate authority, or use certificates generated by a third-party 
+TLS/SSL vendor.
+
+Using a certificate signed by a trusted certificate authority allows 
+MongoDB drivers to verify the server's identity.
 
 For example, see :doc:`/tutorial/configure-ssl-clients`.