Aleksey review

Author: sarahhaggarty

docs/topics/kotlin-daemon.md

@@ -1,14 +1,13 @@
 [//]: # (title: Kotlin daemon)
 
-The Kotlin daemon is a background process that build systems can use to improve Kotlin compilation performance.
-The Kotlin daemon speeds up build times by keeping the compiler and its environment ready to compile. This approach 
-avoids the overhead of starting a new Java Virtual Machine (JVM) instance and reinitializing the compiler for every 
-compilation, leading to reduced build times for incremental builds or frequent small changes.
+The Kotlin daemon is a background process that build systems can use to improve build times by keeping the compiler 
+and its environment ready to compile. This approach avoids starting a new Java Virtual Machine (JVM)
+instance and reinitializing the compiler for every compilation, leading to reduced build times for incremental builds 
+or frequent small changes.
 
-Some build systems, like [Gradle](https://docs.gradle.org/current/userguide/gradle_daemon.html) and [Maven](https://maven.apache.org/tools/mvnd.html),
-have their own daemons that help reduce startup costs. However, they miss the added benefit that the Kotlin daemon
-completely isolates the build system process from the compiler. This separation is useful in dynamic environments where
-system settings might change at runtime.
+Some build systems have their own daemons that help reduce startup costs, such as the [Gradle daemon](https://docs.gradle.org/current/userguide/gradle_daemon.html) and the [Maven daemon](https://maven.apache.org/tools/mvnd.html).
+Using the Kotlin daemon instead reduces startup costs while also completely isolating the build system process from the compiler.
+This separation is useful in dynamic environments where system settings might change at runtime.
 
 Although the Kotlin daemon has no direct user-facing interface, you can use it through build systems or the [build tools API](build-tools-api.md).
 
@@ -46,10 +45,8 @@ For more information, see [`kotlin.daemon.jvmargs` property](gradle-compilation-
 
 There are two common lifetime strategies for the Kotlin daemon:
 
-* **Attached 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.
-* **Detached daemon**: Used when the client is short-lived (like command-line compilation). The daemon stays alive longer
-to await potential follow-up requests.
+* **Attached daemon**: Shut down the daemon shortly after the client process shuts down or the daemon hasn't been used for a while. Use when the client is long-running. 
+* **Detached daemon**: Keep the daemon alive longer to await potential follow-up requests. Use when the client is short-lived. 
 
 To configure the lifetime strategy, you can use the following options:
 
@@ -59,7 +56,7 @@ To configure the lifetime strategy, you can use the following options:
 | `autoshutdownUnusedSeconds` | How long a newly started daemon waits for a first client before shutting down if unused.           | 1 minute      |
 | `shutdownDelayMilliseconds` | How long the daemon waits to shut down after all clients disconnect.                               | 1 second      |
 
-To configure an attached daemon lifetime, set `autoshutdownIdleSeconds` to a **high** value and `shutdownDelayMilliseconds` to a **low** value.
+To configure an attached daemon lifetime strategy, set `autoshutdownIdleSeconds` to a **high** value and `shutdownDelayMilliseconds` to a **low** value.
 
 <tabs group="build-system">
 <tab title="Gradle" group-key="gradle">
@@ -82,7 +79,7 @@ Use the following command:
 </tab>
 </tabs>
 
-To configure a detached daemon lifetime, set `shutdownDelayMilliseconds` to a **high** value.
+To configure a detached daemon lifetime strategy, set `shutdownDelayMilliseconds` to a **high** value.
 
 <tabs group="build-system">
 <tab title="Gradle" group-key="gradle">