Small tweaks

examples/kotlin/shared/src/commonTest/kotlin/com/mongodb/realm/realmkmmapp/EncryptARealmTest.kt

@@ -47,7 +47,7 @@ class EncryptARealmTest : RealmTest() {
                 .build()
             // Open the realm with the configuration
             val realm = Realm.open(config)
-            Log.v("Successfully opened encrypted realm:" + realm.configuration.name)
+            Log.v("Successfully opened encrypted realm: ${realm.configuration.name}")
             // :remove-start:
             assertEquals(generatedKey, realm.configuration.encryptionKey)
             realm.close()
@@ -64,15 +64,15 @@ class EncryptARealmTest : RealmTest() {
         runBlocking {
             val user = app.login(Credentials.anonymous())
             // :snippet-start: encrypt-synced-realm
-            val config = SyncConfiguration.Builder(user, setOf(Frog::class))
+            val syncConfig = SyncConfiguration.Builder(user, setOf(Frog::class))
                 .initialSubscriptions { realm ->
                     add(realm.query<Frog>())
                 }
                 // Specify the encryption key
                 .encryptionKey(generatedKey)
                 .build()
-            val realm = Realm.open(config)
-            Log.v("Successfully opened encrypted realm: ${realm.configuration}")
+            val realm = Realm.open(syncConfig)
+            Log.v("Successfully opened encrypted realm: ${realm.configuration.name}")
             // :snippet-end:
             assertEquals(generatedKey, realm.configuration.encryptionKey)
             realm.close()

source/examples/generated/kotlin/EncryptARealmTest.snippet.encrypt-a-realm.kt

@@ -21,5 +21,5 @@ runBlocking {
         .build()
     // Open the realm with the configuration
     val realm = Realm.open(config)
-    Log.v("Successfully opened encrypted realm:" + realm.configuration.name)
+    Log.v("Successfully opened encrypted realm: ${realm.configuration.name}")
 }

source/examples/generated/kotlin/EncryptARealmTest.snippet.encrypt-synced-realm.kt

@@ -1,9 +1,9 @@
-val config = SyncConfiguration.Builder(user, setOf(Frog::class))
+val syncConfig = SyncConfiguration.Builder(user, setOf(Frog::class))
     .initialSubscriptions { realm ->
         add(realm.query<Frog>())
     }
     // Specify the encryption key
     .encryptionKey(generatedKey)
     .build()
-val realm = Realm.open(config)
-Log.v("Successfully opened encrypted realm: ${realm.configuration}")
+val realm = Realm.open(syncConfig)
+Log.v("Successfully opened encrypted realm: ${realm.configuration.name}")

source/sdk/kotlin/realm-database/realm-files/encrypt-a-realm.txt

@@ -44,9 +44,8 @@ open an encrypted local realm:
 Encrypt a Synced Realm
 ----------------------
 
-You can also encrypt a :ref:`synced realm <kotlin-open-a-synced-realm>`, similar
-to encrypting a local realm. Refer to the :ref:`<kotlin-encryption-and-device-sync>`
-section on this page for more information.
+You can encrypt a :ref:`synced realm <kotlin-open-a-synced-realm>`, similar
+to encrypting a local realm. 
 
 To encrypt a synced realm, pass your encryption key to the
 `encryptionKey <{+kotlin-sync-prefix+}io.realm.kotlin.mongodb/-app-configuration/encryption-key.html>`__
@@ -60,13 +59,25 @@ The following code demonstrates how to open an encrypted synced realm:
    :language: kotlin
    :emphasize-lines: 5-6
 
-Considerations
---------------
+Encryption and Atlas Device Sync
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+.. include:: /includes/encrypt-atlas-device-sync.rst
 
-The following are key impacts to consider when encrypting a realm.
+If you need unique keys for each user of your application, you can use an OAuth provider or
+use one of the :ref:`Realm authentication providers <users-and-authentication>` 
+and an :ref:`authentication trigger<authentication-triggers>`
+to create a 64-bit key and store that key in a :ref:`user object <user-objects>`.
+
+Encrypt App Metadata
+~~~~~~~~~~~~~~~~~~~~
+
+You can also encrypt the App Services App metadata that Realm stores on the device. 
+
+To learn more, refer to :ref:`<kotlin-encrypt-app-metadata>`.
 
 Store & Reuse Keys
-~~~~~~~~~~~~~~~~~~
+------------------
 
 You **must** pass the same encryption key every time you open the encrypted realm. 
 If you don't provide a key or specify the wrong key for an encrypted
@@ -82,12 +93,12 @@ It is the developer's responsibility to ensure that attackers cannot access the
 key.
 
 Performance Impact
-~~~~~~~~~~~~~~~~~~
+------------------
 
 Reads and writes on encrypted realms can be up to 10% slower than unencrypted realms.
 
-Access an Encrypted Realm from Multiple Processes
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Access Encrypted Realm from Multiple Processes
+----------------------------------------------
 
 .. versionchanged:: 10.8.0
 
@@ -97,22 +108,3 @@ the same encrypted realm in multiple processes.
 If your app uses Realm Kotlin SDK version 10.7.1 or earlier, attempting to 
 open an encrypted realm from multiple processes throws this error:
 ``Encrypted interprocess sharing is currently unsupported.``
-
-.. _kotlin-encryption-and-device-sync:
-
-Encryption and Atlas Device Sync
---------------------------------
-
-.. include:: /includes/encrypt-atlas-device-sync.rst
-
-If you need unique keys for each user of your application, you can use an OAuth provider or
-use one of the :ref:`Realm authentication providers <users-and-authentication>` 
-and an :ref:`authentication trigger<authentication-triggers>`
-to create a 64-bit key and store that key in a :ref:`user object <user-objects>`.
-
-Encrypt App Metadata
-~~~~~~~~~~~~~~~~~~~~
-
-You can encrypt the App Services App metadata that Realm stores on the device. 
-
-To learn more, refer to :ref:`<kotlin-encrypt-app-metadata>`.