docs(swift-sdk): describe Swift SDK 0.0.32 in one reference

content/docs/(overview)/devices.mdx

@@ -37,7 +37,7 @@ The hydration **empties the copy first** if the instance's event log now ends be
 
 **For any other reason, the copy refuses reads and writes until a hydration, which empties it first.** Examples are another instance answering at the same address, or a credential whose reach changed.
 
-A copy made by an earlier build of the core can have a different shape. The device **refuses to open it** with `wrong_schema`, deletes nothing, and says how many writes the file holds that the server hasn't taken, because only the build that made it can send them. If some are of a kind the current build no longer sends, it names the kind. [Troubleshooting](/guides/troubleshooting#staying-in-step) says what to do. An app built on the core's Node or Swift binding can replace a refused copy that holds nothing unsent with an empty one.
+A copy made by an earlier build of the core can have a different shape. The device **refuses to open it** with `wrong_schema`, deletes nothing, and says how many writes the file holds that the server hasn't taken, because only the build that made it can send them. If some are of a kind the current build no longer sends, it names the kind. [Troubleshooting](/guides/troubleshooting#staying-in-step) says what to do. An app built on the core's Node or Swift binding can replace a refused copy that holds nothing unsent with an empty one; the files the copy downloaded stay.
 
 ## A write made offline
 

content/docs/(overview)/how-marfa-works.mdx

@@ -33,7 +33,7 @@ Nothing reads or writes your data without a **credential**, and a credential rea
 
 Every program that uses Marfa runs outside it and sends requests to its HTTP API. Programs differ in what sits between them and the API:
 
-- **The Swift SDK and the CLI** embed the **core**, a Rust engine that sends their requests and can keep a working copy of the data they need. A program that keeps a working copy is a **device**: it reads offline and sends its writes when it can reach the instance, as [Devices](/devices) explains.
+- **The Swift SDK and the CLI** embed the **core**, a Rust engine that sends their requests and can keep a working copy of the data they need. A program that keeps a working copy is a **device**: it reads offline and sends its writes when it can reach the instance, as [Devices](/devices) explains. The Swift SDK also sends the operations only the instance can do, such as registering a type, straight to the API.
 - **The TypeScript SDK** sends each request straight to the API, and keeps no copy.
 - **AI agents** use the CLI or the API like any script, with a key of their own, as [Use Marfa with AI agents](/guides/ai-agents) shows.
 - **Connectors** are programs you run that bring in records from another service, such as Todoist, as [Connectors](/connectors) explains.