Update 02_Project_Setup.md

fixed grammar

Author: Miladinho

Full Stack Web App with Kotlin Multiplatform/02_Project_Setup.md

@@ -17,7 +17,7 @@ Let's start with an overview of the structure for our multiplatform Kotlin proje
 Like all Kotlin projects targeting more than one platform, our project uses the Kotlin `multiplatform` Gradle plugin. It provides a single point to configure the targets we need for our application (in our case Kotlin/JVM and Kotlin/JS), and exposes a number of lifecycle tasks for them. For a more detailed look, check out the reference on [Building Multiplatform Projects with Gradle](https://kotlinlang.org/docs/mpp-intro.html). Additionally, we add two more plugins:
 
 - The [`application`](https://docs.gradle.org/current/userguide/application_plugin.html) plugin, which takes care of running the server part of our application, which lives on the JVM.
-- The [`serialization`](https://github.com/Kotlin/kotlinx.serialization#gradle) plugin, which ensures provides multiplatform conversions between Kotlin objects and their JSON text representation JSON is available.
+- The [`serialization`](https://github.com/Kotlin/kotlinx.serialization#gradle) plugin, which provides multiplatform conversions between Kotlin objects and their JSON text representation JSON is available.
 
 ```kotlin
 plugins {
@@ -74,4 +74,4 @@ Each source set also corresponds to a folder in the `src` directory. In our proj
 
 For more detailed information on source sets, check out the [respective section](https://kotlinlang.org/docs/reference/mpp-discover-project.html#source-sets) in the guide. There are a few other snippets that are yet to be explained – but we will discuss them at later chapters in this hands-on, when they become relevant to what we are trying to achieve.
 
-For now, we will focus on building our application, starting with a strong backbone – a simple API server.
+For now, we will focus on building our application, starting with a strong backbone – a simple API server.