chore: update index.md

minor markup updates

Author: koshachy

src/pages/news/gsoc-2023-parallel-stacks/index.md

@@ -19,7 +19,8 @@ Upon initiating the IntelliJ IDEA debugger and encountering a breakpoint, an app
 
 ## Coroutine Stacks
 
-Here is a code sample with multiple coroutines:
+Consider the following code sample with multiple coroutines:
+
 ```kotlin
 import kotlinx.coroutines.*
 
@@ -42,25 +43,26 @@ fun main() = runBlocking<Unit> {
 ```
 
 Let’s add a breakpoint on the following line:
+
 ![breakpoint](image7.png)
 
-To open the Coroutine Stacks panel, click in the bottom right-hand corner of your main IDE panel:
+To open the **Coroutine Stacks** panel, click in the bottom right-hand corner of your main IDE panel:
 
 ![Open Coroutine Stacks](image5.png)
 
 After the debugger stops at the breakpoint and opens the panel, you will see something like this:
 
 ![Coroutine Stacks](image3.png)
 
-The Coroutine Stacks panel shows a graphical representation of different stack traces from different coroutines.
+The **Coroutine Stacks** panel shows a graphical representation of different stack traces from different coroutines.
 
-From the image above, it is clear that we have two coroutines in our application. Their stack traces share a number of frames up until resumeWith. After that, the control flow of these coroutines diverges. The stack trace with the blue border refers to the coroutine that contains the current breakpoint. The frames highlighted in yellow come from libraries. You can hide library frames by clicking the filter button:
+From the image above, it is clear that there are two coroutines in the application. Their stack traces share a number of frames up until resumeWith. After that, the control flow of these coroutines diverges. The stack trace with the blue border refers to the coroutine that contains the current breakpoint. The frames highlighted in yellow come from libraries. You can hide library frames by clicking the filter button:
 
 ![Filter](image8.png)
 
-Now we can see that the stack traces of the two running coroutines only have library frames in common.
+Now you can see that the stack traces of the two running coroutines only have library frames in common.
 
-In the example, all coroutines are running on the same dispatcher, but you can switch the dispatcher by using  the dropdown menu at the top of the panel:
+In the example, all coroutines are running on the same dispatcher, but you can switch the dispatcher by using the dropdown menu at the top of the panel:
 
 ![](image2.png)
 
@@ -85,15 +87,15 @@ You can click on the frames to navigate to the corresponding source code positio
 ## Installation
 
 1. Go to **Settings / Preferences** | **Plugins** in IntelliJ IDEA.
-2. Switch to **Marketplace** and search for **Coroutine Stacks**.
-    ![Install](image4.png)
-3. Select the plugin and click Install.
+2. Switch to **Marketplace** and search for **Coroutine Stacks**:
+
+   ![Install](image4.png)
+   
+3. Select the plugin and click **Install**.
 4. After the installation has been completed, restart the IDE.
 
-## Feel free to contribute!
+## Feel Free to Contribute!
 
-This is just the beginning! With new ideas and features, we can improve the tool to cover more use cases. If you’ve found a bug, don’t like how a feature works, or have other feedback, feel free to open an issue in our official GitHub repository:  
-https://github.com/nikita-nazarov/coroutine-stacks
+This is just the beginning! With new ideas and features, we can improve the tool to cover more use cases. If you’ve found a bug, don’t like how a feature works, or have other feedback, feel free to open an issue in our official GitHub repository: [https://github.com/nikita-nazarov/coroutine-stacks](https://github.com/nikita-nazarov/coroutine-stacks)
 
 Thank you to Raehat and Nikita for building an awesome new tool to help developers be more productive!
-