chore(book): edit for clarity

Author: coriolinus

cc-book/modules/ROOT/pages/client.adoc

@@ -19,15 +19,16 @@ This means `CoreCrypto` can be freely passed to background tasks or across threa
 == Read-Only Operations
 
 Most MLS work happens inside a transaction (see xref:transactions.adoc[]), but a handful of read-only operations are available directly on `CoreCrypto` without opening one.
-These operations are intentionally narrow.
+The set of read-only operations available on `CoreCrypto` is intentionally kept narrow.
+
 Any operation that might change state — creating or deleting a conversation, adding members, encrypting or decrypting a message — requires a transaction.
 
 == Lifecycle
 
 A `CoreCrypto` instance is typically created once at application startup and kept alive for the life of the process.
 The initialization sequence is:
 
-[source]
+[source,typescript]
 ----
 const db = await Database.open(path, key);       // open the keystore
 const cc = CoreCrypto.new(db);                   // construct CoreCrypto

cc-book/modules/ROOT/pages/database.adoc

@@ -17,7 +17,7 @@ All entries are encrypted at rest using the `DatabaseKey` provided at open time.
 
 == Backing Storage
 
-On platforms with an operating system the database is backed by https://www.zetetic.net/sqlcipher/[SQLCipher], an encrypted SQLite variant.
+On non-browser platforms the database is backed by https://www.zetetic.net/sqlcipher/[SQLCipher], an encrypted SQLite variant.
 On the browser, the database sits atop IndexedDB and uses item-level encryption managed by CoreCrypto.
 In both cases, data is encrypted at rest.
 
@@ -45,7 +45,7 @@ If the key is lost, the database contents are unrecoverable.
 
 == Opening the Database
 
-All platforms define an async `Database.open` static method accepting a location and key. On platforms with an OS, the location is a filesystem path. On WASM, the location is the IndexedDB store naem.
+All platforms define an async `Database.open` static method accepting a location and key. On platforms with an OS, the location is a filesystem path. On WASM, the location is the IndexedDB store name.
 
 All platforms define an async static method to open a transient database in memory. On WASM, this is `Database.inMemory`. For Kotlin and Swift, this is an overload of `Database.open`.
 
@@ -72,10 +72,9 @@ db.close()
 == Single-Transaction Constraint
 
 Only one transaction may write to the database at a time.
-If `newTransaction()` is called while another transaction is open, the call will block until the first transaction calls `finish()` or `abort()`.
+If a transaction is requested while another transaction is in flight, the call will block until the first transaction concludes.
 
-This has a direct consequence for application architecture: long-running transactions (for example, processing a large backlog of incoming messages) can block other operations that need to write, such as sending a new message.
-Keep transactions short-lived — acquire, mutate, finish, release.
+For more detail, see xref:transactions.adoc#_concurrency[Transactions -> Concurrency].
 
 == Exporting a Copy
 

cc-book/modules/ROOT/pages/mls.adoc

@@ -26,7 +26,7 @@ Wire's convention is to encode the client ID as a UTF-8 string of the form `user
 
 === `MlsTransport`
 
-CoreCrypto does not know how to innately send data over the network; instead, the caller provides an implementation of this interface that CoreCrypto calls on demand.
+CoreCrypto intentionally abstains from communication with the Wire backend; instead, the caller provides an implementation of this interface that CoreCrypto calls on demand.
 
 `sendCommitBundle(commitBundle)`::
   Called whenever a commit is produced — for example when creating a conversation, adding or removing members, or rotating keys.
@@ -99,7 +99,7 @@ Key packages::
 
 == Ciphersuites
 
-A MLS ciphersuite is a composite designation which specifies the KEM, AEAD, hash, and signature algorithms.
+An MLS ciphersuite is a composite designation which specifies the KEM, AEAD, hash, and signature algorithms.
 CoreCrypto formally supports any of the ciphersuites specified in the RFC, but is primarily tested on ciphersuite 1 (MLS_128_DHKEMX25519_AES128GCM_SHA256_Ed25519).
 
 The ciphersuite is fixed per conversation at the conversation's creation.

cc-book/modules/ROOT/pages/proteus.adoc

@@ -9,7 +9,7 @@ This effect is compounded by the fact that a logical user in the sense of a huma
 This O(n²) overhead is manageable for small groups, but becomes expensive as they scale, and it was the primary motivation for adopting MLS.
 
 Proteus remains supported for backwards compatibility, but has not received direct development work in some time.
-Its implementaion is already feature-gated for easy removal, and is intended to be removed as soon as we can confirm that a sufficiency of clients have upgraded their conversations to MLS.
+Its implementation is already feature-gated for easy removal, and is intended to be removed as soon as we can confirm that a sufficiency of clients have upgraded their conversations to MLS.
 
 == Initialization
 
@@ -26,7 +26,7 @@ All other Proteus methods will return an error if called before `proteusInit()`
 == Identity and Fingerprints
 
 A Proteus identity is a long-lived Ed25519 keypair tied to the device.
-CoreCrypto exposes three fingerprint accessors, each returning a lowercase hex string:
+CoreCrypto exposes several fingerprint accessors, each returning a hex string:
 
 `proteusFingerprint()`::
   The local device's public key.

cc-book/modules/ROOT/partials/cc10-migration.adoc

@@ -19,13 +19,13 @@ ifeval::[{platform} != browser]
 endif::[]
   As before with `deferredInit()`, call `mlsInit()` in a transaction to initialize MLS.
 
-== MLS Initialization.
+== MLS Initialization
 
 . `mlsInit()` was decoupled from key package creation.
   To create key packages after initializing MLS, call `clientKeypackages()` in a transaction.
 
 . removed `CoreCrypto.provideTransport()`, added `transport` parameter to `CoreCryptoContext.mlsInit()`
-  Instead of providing transport separately from MLS initialization provide it when calling `mlsInit()``.
+  Instead of providing transport separately from MLS initialization provide it when calling `mlsInit()`.
 
 == Logging
 

cc-book/modules/browser/pages/cc10-migration.adoc

@@ -3,7 +3,7 @@
 = Migrating from v9.x to v10.0
 
 == Browser Module Location
-We want to set the ground for a native module.
+We want to prepare the ground for a native module, which runs on node or bun.
 Therefore, the browser module is now exported as `@wireapp/core-crypto/browser`.
 Update your imports from `@wireapp/core-crypto` to `@wireapp/core-crypto/browser`.
 
@@ -38,7 +38,7 @@ https://jhugman.github.io/uniffi-bindgen-react-native/idioms/errors.html#enums-a
 ==== Example Usage
 
 .Extracting the abort reason given via an `MlsTransportResponse`
-[source, typescript]
+[source,typescript]
 ----
   import { CoreCryptoError, MlsError } from "core-crypto";
 
@@ -56,7 +56,7 @@ https://jhugman.github.io/uniffi-bindgen-react-native/idioms/errors.html#enums-a
 ----
 
 .Optional: use `switch` to handle multiple errors in one go
-[source, typescript]
+[source,typescript]
 ----
   import { CoreCryptoError, MlsError, MlsError_Tags } from "core-crypto";
 
@@ -78,7 +78,7 @@ https://jhugman.github.io/uniffi-bindgen-react-native/idioms/errors.html#enums-a
 ----
 
 .Catch a proteus error
-[source, typescript]
+[source,typescript]
 ----
   import { CoreCryptoError, ProteusError } from "core-crypto";