Aleksey review part 1

Author: sarahhaggarty

docs/topics/compiler-plugins.md

@@ -1,9 +1,9 @@
 [//]: # (title: Compiler plugins)
 
-This page explains the Kotlin compiler plugins available to you and what you can do if none of them suits your use case.
-
 Compiler plugins hook into the compilation process to analyze or change code while it's being compiled, without modifying the compiler itself. For example, they can annotate code or generate new code to make it compatible with other frameworks or APIs.
 
+This page explains the Kotlin compiler plugins available to you and what you can do if none of them suits your use case.
+
 The Kotlin team maintains the following compiler plugins:
 * [All-open](all-open-plugin.md)
 * [AtomicFU](https://github.com/Kotlin/kotlinx-atomicfu)
@@ -17,8 +17,9 @@ The Kotlin team maintains the following compiler plugins:
 * [SAM with receiver](sam-with-receiver-plugin.md)
 * [Serialization](serialization.md)
 
-The Android team at Google maintains the [Compose compiler Gradle plugin](https://developer.android.com/develop/ui/compose/compiler)
-and the [Parcelize plugin](https://plugins.gradle.org/plugin/org.jetbrains.kotlin.plugin.parcelize).
+The Android team at Google maintains:
+* [Compose compiler Gradle plugin](https://developer.android.com/develop/ui/compose/compiler)
+* [Parcelize plugin](https://plugins.gradle.org/plugin/org.jetbrains.kotlin.plugin.parcelize)
 
 If you need to adapt the compilation process in a way that these plugins don't cover, first check whether you can use the
 [Kotlin Symbol Processing (KSP) API](https://kotlinlang.org/docs/ksp-overview.html) or an external linter such as [Android lint](https://developer.android.com/studio/write/lint).
@@ -27,15 +28,15 @@ and ask for advice about your use case.
 
 If you _still_ can't find what you need, you can create a custom compiler plugin. Use this approach only as a last resort,
 because the Kotlin compiler plugin API is **unstable**. Maintaining a custom compiler plugin requires significant ongoing
-effort, since each new compiler release introduces breaking changes.
+effort, because each new compiler release introduces breaking changes.
 
 ## Custom compiler plugins
 
-> The Kotlin compiler plugin API is unstable and includes breaking changes in every release.
+> The Kotlin compiler plugin API is unstable and introduces breaking changes in every release.
 > 
 {style="warning"}
 
-Compiler plugins can influence different stages of the compilation process depending on their use case.
+Compiler plugins can influence different stages of the compilation process.
 
 ![Kotlin compiler stages](compiler-stages.svg){width=650}
 
@@ -109,10 +110,17 @@ The backend plugin API, also known as IR, has a single extension point: [`IrGene
 Use this extension point and override the `generate()` function to add bodies to declarations already generated by the 
 frontend or change existing declaration bodies.
 
-Changes made through this extension point are **not checked**. You must ensure that your changes don't break the compiler's
+Changes made through this extension point are **not checked** by the compiler. You must ensure that your changes don't break the compiler's
 expectations at this stage. For example, you might accidentally introduce an invalid type, an incorrect function reference,
 or a reference outside the correct scope.
 
+### Explore backend plugin code
+
+You can explore the Kotlin serialization plugin code to see what backend plugin compiler code looks like in practice.
+For example, [`SerializableCompanionIrGenerator.kt`](https://github.com/JetBrains/kotlin/blob/master/plugins/kotlinx-serialization/kotlinx-serialization.backend/src/org/jetbrains/kotlinx/serialization/compiler/backend/ir/SerializerIrGenerator.kt)
+fills in missing bodies for key serializer members. One example is the [`generateChildSerializersGetter()`](https://github.com/JetBrains/kotlin/blob/9cfa558902abc13d245c825717026af63ef82dd2/plugins/kotlinx-serialization/kotlinx-serialization.backend/src/org/jetbrains/kotlinx/serialization/compiler/backend/ir/SerializerIrGenerator.kt#L242)
+function, which collects a list of `KSerializer` expressions and returns them in an array.
+
 #### Check your backend plugin for problems
 
 You can check for problems in your backend plugin code in three main ways:
@@ -129,11 +137,6 @@ You can check for problems in your backend plugin code in three main ways:
 
     In the `convertToIr.kt` file, add breakpoints in the `convertToIrAndActualize()` function and run the compiler in debug mode to get more detailed information during compilation.
 
-You can also explore the Kotlin serialization plugin code to see what backend plugin compiler code looks like in practice. 
-For example, [`SerializableCompanionIrGenerator.kt`](https://github.com/JetBrains/kotlin/blob/master/plugins/kotlinx-serialization/kotlinx-serialization.backend/src/org/jetbrains/kotlinx/serialization/compiler/backend/ir/SerializerIrGenerator.kt) 
-fills in missing bodies for key serializer members. One example is the [`generateChildSerializersGetter()`](https://github.com/JetBrains/kotlin/blob/9cfa558902abc13d245c825717026af63ef82dd2/plugins/kotlinx-serialization/kotlinx-serialization.backend/src/org/jetbrains/kotlinx/serialization/compiler/backend/ir/SerializerIrGenerator.kt#L242)
-function, which collects a list of `KSerializer` expressions and returns them in an array.
-
 ### Test your plugin
 
 Once you implement your plugin, test it thoroughly. The [Kotlin compiler plugin template](https://github.com/Kotlin/compiler-plugin-template) 
@@ -157,5 +160,5 @@ new dump files become your latest _golden_ files: an approved and trusted source
 ### Get help
 
 If you run into issues developing a custom compiler plugin, reach out in [Kotlin Slack](https://surveys.jetbrains.com/s3/kotlin-slack-sign-up)
-in the [#compiler](https://kotlinlang.slack.com/archives/C7L3JB43G) channel. We can't promise a solution but we will try 
+in the [#compiler](https://slack-chats.kotlinlang.org/c/compiler) channel. We can't promise a solution but we will try 
 to help if we can.