Doc updates

Author: aclark4life

docs/howto/queryable-encryption.rst

@@ -14,7 +14,7 @@ Encryption in your Django project.
 .. admonition:: MongoDB requirements
 
     Queryable Encryption can be used with MongoDB replica sets or sharded
-    clusters running version 7.0 or later. Standalone instances are not
+    clusters running version 8.0 or later. Standalone instances are not
     supported. The following table summarizes which MongoDB server products
     support each Queryable Encryption mechanism.
 
@@ -51,21 +51,36 @@ encryption keys.
 
     import os
 
-    from django_mongodb_backend import parse_uri
     from pymongo.encryption_options import AutoEncryptionOpts
 
     DATABASES = {
-        # ...
-        "encrypted": parse_uri(
-            DATABASE_URL,
-            options={
+        "default": {
+            "ENGINE": "django_mongodb_backend",
+            "HOST": "mongodb+srv://cluster0.example.mongodb.net",
+            "NAME": "my_database",
+            "USER": "my_user",
+            "PASSWORD": "my_password",
+            "PORT": 27017,
+            "OPTIONS": {
+                "retryWrites": "true",
+                "w": "majority",
+                "tls": "false",
+            },
+        },
+        "encrypted": {
+            "ENGINE": "django_mongodb_backend",
+            "HOST": "mongodb+srv://cluster0.example.mongodb.net",
+            "NAME": "encrypted",
+            "USER": "my_user",
+            "PASSWORD": "my_password",
+            "PORT": 27017,
+            "OPTIONS": {
                 "auto_encryption_opts": AutoEncryptionOpts(
-                    key_vault_namespace="keyvault.keyvault",
+                    key_vault_namespace="encrypted.keyvault",
                     kms_providers={"local": {"key": os.urandom(96)}},
                 )
             },
-            db_name="encrypted",
-        ),
+        },
     }
 
 Configuring the ``DATABASE_ROUTERS`` setting
@@ -88,10 +103,15 @@ configure a custom router for Queryable Encryption:
         Encryption.
         """
 
+        def db_for_read(self, model, **hints):
+            if model._meta.app_label == "myapp":
+                return "encrypted"
+            return None
+
+        db_for_write = db_for_read
+
         def allow_migrate(self, db, app_label, model_name=None, **hints):
-            # The patientdata app's models are only created in the encrypted
-            # database.
-            if app_label == "patientdata":
+            if app_label == "myapp":
                 return db == "encrypted"
             # Don't create other app's models in the encrypted database.
             if db == "encrypted":

docs/topics/queryable-encryption.rst

@@ -106,7 +106,7 @@ For example, to find a patient by their SSN, you can do the following::
     'Bob'
 
 
-QuerySet Limitations
+QuerySet limitations
 ~~~~~~~~~~~~~~~~~~~~
 
 When using Django QuerySets with MongoDB Queryable Encryption, it’s important to
@@ -128,8 +128,6 @@ be done client-side after decryption. Key limitations include:
 - **No joins on encrypted fields** – Filtering across relationships using
   encrypted foreign keys is unsupported because matching must happen
   client-side.
-- **Admin/debug limitations** – You’ll need to integrate client-side decryption
-  for Django admin or tools, otherwise you’ll see ciphertext.
 
 In short, when working with Queryable Encryption, design your queries to use
 exact matches only on encrypted fields, and plan to handle any sorting or