DOCSP-7006 fix admonition, add link to server-side encryption schema (#574)

* DOCSP-7006 CSFLE - fix admonition, add link to server-side encryption schema

Author: Chris Cho

source/use-cases/client-side-field-level-encryption-guide.txt

@@ -365,12 +365,14 @@ locally-managed master key.
 C. Define a JSON Schema
 ~~~~~~~~~~~~~~~~~~~~~~~
 
-`JSON Schema <http://json-schema.org/>`_ is a vocabulary that allows you
-to annotate and validate JSON documents. MongoDB drivers use an extended
-version of the JSON Schema standard to configure automatic client-side
-encryption and decryption of specific fields of the documents in a
-collection. The extended MongoDB CSFLE standard requires the following
-information:
+In this section, MedcoMD engineers configure the fields that the client
+automatically encrypts and decrypts using JSON Schema.
+`JSON Schema <http://json-schema.org/>`_ is a vocabulary
+that allows you to annotate and validate JSON documents.
+MongoDB drivers use an extended version of the JSON Schema standard to
+configure automatic client-side encryption and decryption of specific fields
+of the documents in a collection. The MongoDB CSFLE extended JSON Schema
+standard requires the following information:
 
 - The encryption algorithm to use when encrypting each field
   (:manual:`Deterministic Encryption
@@ -383,16 +385,26 @@ information:
 - The BSON Type of each field (only required for deterministically
   encrypted fields)
 
-.. admonition::Automatic Client-Side Field Level Encryption JSON Schema Does Not Support Document Validation
-   :important:
+.. admonition:: CSFLE JSON Schema Does Not Support Document Validation
+   :class: important:
 
-   MongoDB drivers only use JSON Schema syntax to configure automatic
-   client-side field level encryption and support *only* field-level
-   encryption-specific keywords documented in :manual:`Automatic Encryption
-   JSON Schema Syntax </reference/security-client-side-automatic-json-schema/>`.
+   MongoDB drivers use JSON Schema syntax to specify encrypted fields
+   and *only* support field-level encryption-specific keywords documented
+   in :manual:`Automatic Encryption JSON Schema Syntax
+   </reference/security-client-side-automatic-json-schema/>`.
    Any other document validation instances will cause the client to throw
    an error.
 
+.. admonition:: Server-side JSON Schema
+
+   You can prevent clients that are not configured with the appropriate
+   client-side JSON Schema from writing unencrypted data to a field by
+   using server-side JSON Schema. The server-side JSON Schema provides
+   only supplemental enforcement of the client-side JSON Schema. For
+   more details on server-side document validation implementation,
+   see :manual:`Enforce Field Level Encryption Schema
+   </core/security-client-side-encryption/#enforce-field-level-encryption-schema>`.
+
 The MedcoMD engineers receive specific requirements for the fields of
 data and their encryption strategies. The following table illustrates
 the data model of the Medco Management System.
@@ -473,8 +485,6 @@ upon deterministic encryption based on the following properties:
         }
     }
 
-
-
 Blood Type
 ++++++++++
 
@@ -494,7 +504,6 @@ random encryption based on the following properties:
         }
     }
 
-
 Medical Records
 +++++++++++++++
 
@@ -542,7 +551,6 @@ decide upon deterministic encryption based on the following properties:
         }
     }
 
-
 Recap
 +++++
 
@@ -551,7 +559,6 @@ requirements of making sensitive data queryable and secure. View the
 full `JSON Schema for the Medco Medical Management System
 <https://raw.githubusercontent.com/mongodb/docs-assets/DOCSP-json-schema-helper-and-json/MedcoMDSchema.json>`_.
 
-
 .. tabs-drivers::
 
    .. tab::
@@ -714,7 +721,6 @@ unencrypted:
         }
     }
 
-
 .. note::
 
    For queries using a client that is not configured to use CSFLE, such