Alexander review

Author: sarahhaggarty

docs/topics/kotlin-daemon.md

@@ -18,6 +18,7 @@ There are ways to configure some settings for the Kotlin daemon for Gradle or Ma
 
 ### Memory management
 
+The Kotlin daemon is a separate process that has its own memory space, isolated from the client.
 By default, the Kotlin daemon tries to inherit the heap size (`-Xmx`) of the launching JVM process.
 
 To configure specific memory limits, like `-Xmx` and `-XX:MaxMetaspaceSize`, use the following property:
@@ -45,20 +46,20 @@ For more information, see [`kotlin.daemon.jvmargs` property](gradle-compilation-
 
 There are two common lifetime strategies for the Kotlin daemon:
 
-* **Short-lived daemon**: Used when the client (like a build system) is long-running. The daemon shuts down shortly after the
-last compilation.
-* **Long-lived daemon**: Used when the client is short-lived (like command-line compilation). The daemon stays alive longer
+* **Detached daemon**: Used when the client (like a build system) is long-running. The daemon shuts down shortly after the
+client process shuts down or the daemon hasn't been used for a while.
+* **Attached daemon**: Used when the client is short-lived (like command-line compilation). The daemon stays alive longer
 to await potential follow-up requests.
 
 To configure the lifetime strategy, you can use the following options:
 
-| Option | Description                                                                                        | Default value |
-|--------|----------------------------------------------------------------------------------------------------|---------------|
-| `autoshutdownIdleSeconds` | How long the daemon should stay alive after the last compilation when a client is still connected. | 2 hours |
-| `autoshutdownUnusedSeconds` | How long the daemon waits to shut down after all clients disconnect.                               | 1 minute |
-| `shutdownDelayMilliseconds` | How long a newly started daemon waits for a first client before shutting down if unused.           | 1 second |
+| Option                      | Description                                                                                        | Default value |
+|-----------------------------|----------------------------------------------------------------------------------------------------|---------------|
+| `autoshutdownIdleSeconds`   | How long the daemon should stay alive after the last compilation when a client is still connected. | 2 hours       |
+| `autoshutdownUnusedSeconds` | How long the daemon waits to shut down after all clients disconnect.                               | 1 minute      |
+| `shutdownDelayMilliseconds` | How long a newly started daemon waits for a first client before shutting down if unused.           | 1 second      |
 
-To configure a short-lived daemon lifetime, set `shutdownDelayMilliseconds` to a **high** value.
+To configure a detached daemon lifetime, set `shutdownDelayMilliseconds` to a **high** value.
 
 <tabs group="build-system">
 <tab title="Gradle" group-key="gradle">
@@ -81,7 +82,7 @@ Add the following property to your `pom.xml` file:
 </tab>
 </tabs>
 
-To configure a long-lived daemon lifetime, set `autoshutdownIdleSeconds` to a **high** value and `shutdownDelayMilliseconds` to a **low** value.
+To configure an attached daemon lifetime, set `autoshutdownIdleSeconds` to a **high** value and `shutdownDelayMilliseconds` to a **low** value.
 
 <tabs group="build-system">
 <tab title="Gradle" group-key="gradle">