fixup! Introduce docs/separate-benchmark-module.md

Author: Abduqodiri Qurbonzoda

docs/separate-benchmark-module.md

@@ -2,13 +2,11 @@
 
 This guide will walk you through the process of creating a separate module for benchmarks in your Kotlin project. 
 Creating a separate module for benchmarks is especially beneficial when you are integrating benchmarks into an existing project. 
-Here are a few advantages of doing so:
+Here are a couple of advantages of doing so:
 
-1. **Organization**: It helps maintain a clean and organized project structure. Segregating benchmarks from the main code makes it easier to navigate and locate specific code segments.
+1. **Flexibility**: Creating a separate module allows you to manage your benchmarking code independently. You can compile, test, and run benchmarks without impacting your main source code.
 
-2. **Isolation**: Separating benchmarks ensures that the benchmarking code does not interfere with your main code or test code. This isolation guarantees accurate measurements without unintentional side effects.
-
-3. **Flexibility**: Creating a separate module allows you to manage your benchmarking code independently. You can compile, test, and run benchmarks without impacting your main source code.
+2. **Organization**: It helps maintain a clean and organized project structure. Segregating benchmarks from the main code makes it easier to navigate and locate specific code segments.
 
 ## Step-by-step Setup Guide
 
@@ -18,7 +16,7 @@ Below are the step-by-step instructions to set up a separate module for benchmar
 
 Follow these steps to set up a separate compilation for benchmarks:
 
-1. **Define New Compilation**:
+1. **Define New Compilation**
 
     Start by creating a new compilation in your target of choice (e.g. jvm, js, native, wasm etc.). 
     In this example, we're associating the new compilation `benchmark` with the `main` compilation of the `jvm` target. 
@@ -37,7 +35,7 @@ Follow these steps to set up a separate compilation for benchmarks:
     }
     ```
 
-2. **Register Benchmark Compilation**:
+2. **Register Benchmark Compilation**
 
     Conclude by registering your new benchmark compilation using its default source set name. 
     In this instance, `jvmBenchmark` is the name of the default source set of the `benchmark` compilation.
@@ -59,7 +57,7 @@ and the [documentation on associating compiler tasks](https://kotlinlang.org/doc
 
 Set up a separate benchmark source set by following these simple steps:
 
-1. **Define Source Set**:
+1. **Define Source Set**
 
     Begin by defining a new source set. We'll use `benchmark` as the name for the source set.
 
@@ -70,7 +68,7 @@ Set up a separate benchmark source set by following these simple steps:
     }
     ```
 
-2. **Propagate Dependencies**:
+2. **Propagate Dependencies**
 
     Next, propagate dependencies and output from the `main` source set to your `benchmark` source set. 
     This ensures the `benchmark` source set has access to classes and resources from the `main` source set.
@@ -85,7 +83,7 @@ Set up a separate benchmark source set by following these simple steps:
     You can also add output and `compileClasspath` from `sourceSets.test` in the same way 
     if you wish to reuse some of the test infrastructure.
 
-3. **Register Benchmark Source Set**:
+3. **Register Benchmark Source Set**
 
     Finally, register your benchmark source set. This informs the kotlinx-benchmark tool 
     that benchmarks reside within this source set and need to be executed accordingly.