Polish README.md

Author: wldeh

README.md

@@ -198,7 +198,7 @@ To run benchmarks in Kotlin/JVM:
     <details>
       <summary><b>Explanation</b></summary>
 
-    Consider you annotated each of your benchmark classes with `@State(Scope.Benchmark)`:
+    Assume that you've annotated each of your benchmark classes with `@State(Scope.Benchmark)`:
 
     ```kotlin
     // MyBenchmark.kt
@@ -315,24 +315,91 @@ Note: Kotlin/WASM is an experimental compilation target for Kotlin. It may be dr
 
 ### Writing Benchmarks
 
-Now you can write your benchmarks.
+After setting up your project and configuring targets, you can start writing benchmarks:
 
-// A short introduction to writing benchmarks.
+1. **Create Benchmark Class**: Create a class in your source set where you'd like to add the benchmark. Annotate this class with `@State(Scope.Benchmark)`.
+
+    ```kotlin
+    @State(Scope.Benchmark)
+    class MyBenchmark {
+
+    }
+    ```
+
+2. **Set up Parameters and Variables**: Define variables needed for the benchmark.
+
+    ```kotlin
+    var param: Int = 10
+
+    private var list: MutableList<Int> = ArrayList()
+    ```
+
+3. **Initialize Resources**: Within the class, you can define any setup or teardown methods using `@Setup` and `@TearDown` annotations respectively. These methods will be executed before and after the entire benchmark run.
+
+    ```kotlin
+    @Setup
+    fun prepare() {
+        for (i in 0 until size) {
+            list.add(i)
+        }
+    }
+
+    @TearDown
+    fun cleanup() {
+        list.clear()
+    }
+    ```
+
+4. **Define Benchmark Method**: Next, create methods that you would like to be benchmarked within this class and annotate them with `@Benchmark`.
+
+    ```kotlin
+    @Benchmark
+    fun benchmarkMethod(): Int {
+        return list.sum()
+    }
+    ```
+
+Your final benchmark class will look something like this:
+
+    @State(Scope.Benchmark)
+    class MyBenchmark {
+
+        var param: Int = 10
+
+        private var list: MutableList<Int> = ArrayList()
+
+        @Setup
+        fun prepare() {
+            for (i in 0 until size) {
+                list.add(i)
+            }
+        }
+
+        @Benchmark
+        fun benchmarkMethod(): Int {
+            return list.sum()
+        }
+
+        @TearDown
+        fun cleanup() {
+            list.clear()
+        }
+    }
 
 Note: Benchmark classes located in the common source set will be run in all platforms, while those located in a platform-specific source set will be run only in the corresponding platform.
 
-See <TBD-document> to for a complete guide for writing benchmarks.
+See [writing benchmarks](docs/writing-benchmarks.md) for a complete guide for writing benchmarks.
 
 ### Running Benchmarks
 
-To run your benchmarks in all registered platforms run `benchmark` Gradle task in your project.
-To run in only in a specific platform run `<target-name>Benchmark`, e.g., `jvmBenchmark`.
+To run your benchmarks in all registered platforms, run `benchmark` Gradle task in your project.
+To run only on a specific platform, run `<target-name>Benchmark`, e.g., `jvmBenchmark`.
 
-Learn more about the tasks kotlinx-benchmark plugin creates in [this guide](docs/tasks-overview.md).
+For more details about the tasks created by the kotlinx-benchmark plugin, refer to [this guide](docs/tasks-overview.md).
 
 ### Benchmark Configuration Profiles
 
-The kotlinx-benchmark library provides ability to create multiple configuration profiles. The `main` configuration is already created by Toolkit.
+The kotlinx-benchmark library provides the ability to create multiple configuration profiles. The `main` configuration is already created by the Toolkit.
 Additional profiles can be created as needed in the `configurations` section of the `benchmark` block:
 
 ```kotlin
@@ -370,4 +437,4 @@ These examples showcase various use cases and offer practical insights into the
 
 ## Contributing
 
-We welcome contributions to kotlinx-benchmark! If you want to contribute, please refer to our Contribution Guidelines.
+We welcome contributions to kotlinx-benchmark! If you want to contribute, please refer to our [Contribution Guidelines](CONTRIBUTING.md).