diff --git a/docs/core/entity/conversation.md b/docs/core/entity/conversation.md
index db1e7bcc..abc3336b 100644
--- a/docs/core/entity/conversation.md
+++ b/docs/core/entity/conversation.md
@@ -72,6 +72,12 @@ A `ConversationInput` object contains the following data:
_We used to promote `async_process` as the method to process messages. This was changed to `_async_handle_message` to automatically include the chat log. The change is backwards compatible._
+#### Chat log
+
+The chat log object allows the conversation entity to read the conversation history and to add messages and tool calls to it.
+
+See [the Python interface](https://github.com/home-assistant/core/blob/dev/homeassistant/components/conversation/chat_log.py) for the full typed API.
+
### Prepare
As soon as Home Assistant knows a request is coming in, we will let the conversation entity prepare for it. This can be used to load a language model or other resources. This function is optional to implement.
diff --git a/docs/intent_conversation_api.md b/docs/intent_conversation_api.md
index b1e0bf9f..e2f72790 100644
--- a/docs/intent_conversation_api.md
+++ b/docs/intent_conversation_api.md
@@ -44,6 +44,7 @@ The JSON response from `/api/conversation/process` contains information about th
```json
{
+ "continue_conversation": true,
"response": {
"response_type": "action_done",
"language": "en",
@@ -91,6 +92,8 @@ The following properties are available in the `"response"` object:
The [conversation id](#conversation-id) is returned alongside the conversation response.
+If `continue_conversation` is set to true, the conversation agent expects a follow-up from the user.
+
## Response types
@@ -287,7 +290,7 @@ POST with the next input sentence:
```
-## Pre-loading sentences
+## Pre-loading sentences
Sentences for a language can be pre-loaded using the WebSocket API:
diff --git a/docs/voice/pipelines/index.md b/docs/voice/pipelines/index.md
index df196e85..c87c92cf 100644
--- a/docs/voice/pipelines/index.md
+++ b/docs/voice/pipelines/index.md
@@ -41,7 +41,7 @@ The following events can be emitted:
| Name | Description | Emitted | Attributes |
|----------------|------------------------------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `run-start` | Start of pipeline run | always | `pipeline` - ID of the pipeline
`language` - Language used for pipeline
`runner_data` - Extra WebSocket data: