Replace `channel` with `conversation` throughout the API.

This is a **breaking change** for essentially all clients. Thankfully, there's presently just the one, so we don't need to go to much effort to accommoate that; the client is modified in this commit to adapt, users can reload their client, and life will go on.

1 files changed, 1 insertions, 1 deletions

diff --git a/docs/developer/server/testing.md b/docs/developer/server/testing.md
index 8e87568..a3109cb 100644
--- a/docs/developer/server/testing.md
+++ b/docs/developer/server/testing.md
@@ -22,6 +22,6 @@ Prefer writing "flat" fixtures that do one thing, over compound fixtures that do
 
 Prefer role-specific names for test values: use, for example, `sender` for a login related to sending messages, rather than `login`. Fixture data is cheap, so make as many entities as make sense for the test. They'll vanish at the end of the test anyways.
 
-Prefer testing a single endpoint at a time. Other interactions, which may be needed to set up the scenario or verify the results, should be done against the `app` abstraction directly. It's okay if this leads to redundant tests (see for example `src/channel/routes/test/on_send.rs` and `src/events/routes/test.rs`, which overlap heavily).
+Prefer testing a single endpoint at a time. Other interactions, which may be needed to set up the scenario or verify the results, should be done against the `app` abstraction directly. It's okay if this leads to redundant tests (see for example `src/conversation/routes/test/on_send.rs` and `src/events/routes/test.rs`, which overlap heavily).
 
 Panicking in tests is fine. Panic messages should describe why the preconditions were expected, and can be terse.