@@ -24,7 +24,7 @@ information in the context of a real-world scenario:
2424- **How to implement Client-Side Field Level Encryption with the MongoDB
2525 driver** (`Implementation`_)
2626
27- .. admonition :: Download the Code
27+ .. note :: Download the Code
2828
2929 For a runnable example of all the functionality demonstrated in this guide,
3030 see the :ref:`Download Example Project <download-example-project>` section.
@@ -277,8 +277,7 @@ encrypt and decrypt document fields, are stored in a key vault collection in
277277the same MongoDB replica set as the encrypted data.
278278
279279
280- .. admonition:: Local Key Provider is not suitable for production
281- :class: important
280+ .. warning:: Local Key Provider is not suitable for production
282281
283282 The Local Key Provider is an insecure method of storage and is therefore
284283 **not recommended** if you plan to use CSFLE in production. Instead,
@@ -409,8 +408,7 @@ information:
409408- The BSON Type of each field (only required for deterministically
410409 encrypted fields)
411410
412- .. admonition:: CSFLE JSON Schema Does Not Support Document Validation
413- :class: important
411+ .. warning:: CSFLE JSON Schema Does Not Support Document Validation
414412
415413 MongoDB drivers use JSON Schema syntax to specify encrypted fields
416414 and *only* support field-level encryption-specific keywords documented
@@ -419,7 +417,7 @@ information:
419417 Any other document validation instances will cause the client to throw
420418 an error.
421419
422- .. admonition :: Server-side JSON Schema
420+ .. warning :: Server-side JSON Schema
423421
424422 You can prevent clients that are not configured with the appropriate
425423 client-side JSON Schema from writing unencrypted data to a field by
0 commit comments