Trim LiveKit changelog entry to the essentials

Author: markbackman

CHANGELOG.md

@@ -13,30 +13,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   `pipecatcloud`. Like the other `*SessionArguments` types it subclasses the
   matching pipecat-ai runner type (`LiveKitRunnerArguments`), so it carries
   `room_name`, `url`, `token`, and `session_id`, and works with pipecat's
-  `create_transport` and `isinstance` checks.
-
-  Pipecat Cloud provisions nothing for LiveKit, unlike Daily, so a session's
-  connection details travel in the start body under a `livekit` key:
-
-  ```python
-  session = Session(
-      agent_name="my-agent",
-      api_key=api_key,
-      params=SessionParams(
-          data={
-              "livekit": {
-                  "url": "wss://your-project.livekit.cloud",
-                  "room_name": "your-room",
-                  "token": "the bot's access token",
-              }
-          }
-      ),
-  )
-  ```
-
-  Mint the room and both tokens with your own LiveKit API key and secret, join
-  with the user token, and send the bot's token. Base image 0.1.28 and later
-  turns that block into `LiveKitSessionArguments` before calling `bot()`.
+  `create_transport` and `isinstance` checks. Pass the LiveKit connection
+  details in the `body` request parameter when starting a session, under a
+  `livekit` key holding `url`, `room_name`, and the bot's `token`. Base image
+  0.1.28 and later turns that block into `LiveKitSessionArguments` before
+  calling `bot()`.
 
 - Architecture selection on deploy: `pipecat cloud deploy --architecture
   {amd64,arm64}` or an `architecture` key in `pcc-deploy.toml` (the flag