README cleanup

README.md

@@ -2,7 +2,7 @@
 
 [Advent of Code][aoc] – an annual event in December since 2015.
 Every year since then, with the first day of December, a programming puzzles contest is published every day for twenty-four days.
-A set of Christmas-oriented challenges provide any input you have to use to answer using the language of your choice.
+A set of Christmas-oriented challenges provides any input you have to use to answer using the language of your choice.
 We offer you a template prepared to use with [Kotlin][kotlin] language within this repository.
 
 ![][file:cover]
@@ -17,25 +17,25 @@ After creating a new project based on this template in your account, a dedicated
 It will also personalize code to use your username and project name in namespaces and Gradle properties.
 How cool is that?
 
-Right after the [@actions-user][actions-user] actor pushes the second commit to your repository, you're ready to clone it within the IntelliJ IDEA.
+You can clone it within the IntelliJ IDEA whenever the [@actions-user][actions-user] actor pushes the second commit to your repository.
 
 > [!IMPORTANT]
 >
 > Right after opening the project in IntelliJ IDEA, verify if you use at least **Java 11** as Project SDK.
 > To do that, visit [Project Structure Settings][docs-project-structure] (<kbd>⌘ Cmd</kbd><kbd>;</kbd> on macOS or <kbd>Ctrl</kbd><kbd>Alt</kbd><kbd>Shift</kbd><kbd>S</kbd> on Windows/Linux).
 
-From now, everything's in your hands!
-Join the [Advent of Code][aoc] contest, solve the *Day 01* as soon as it is published.
+From now on, everything's in your hands!
+Join the [Advent of Code][aoc] contest to solve the *Day 01* as soon as it is published.
 
-For the following days, copy the `Day01.kt` solution file and increment the day number.
+Copy the `Day01.kt` solution file for the following days and increment the day number.
 
 > [!NOTE]
 >
 > Remember to join the Kotlin contest!
-> 
+>
 > To do that, edit your project's _About_ section with ⚙️ icon and add the `aoc-2023-in-kotlin` topic to your project.
-> 
-> **We will find your repository and count you in our giveaway.** 
+>
+> **We will find your repository and count you in our giveaway.**
 
 ## Setup
 
@@ -46,12 +46,12 @@ After you create a new project based on the current template repository using th
 ├── README.md               README file
 ├── build.gradle.kts        Gradle configuration created with Kotlin DSL
 ├── settings.gradle.kts     Gradle project settings
-├── gradle*                 Gradle wraper files
+├── gradle*                 Gradle wrapper files
 └── src
     ├── Day01.kt            An empty implementation for the first AoC day
     ├── Utils.kt            A set of utility methods shared across your days
     │                       
-    │                       (files needed to be manually created)
+    │                       (create those files manually)
     ├── Day01.txt           An empty file for the Day 01 input data
     └── Day01_test.txt      An optional Day 01 test input data used for checks
 ```
@@ -60,8 +60,8 @@ After you create a new project based on the current template repository using th
 >
 > All task input files (`src/*.txt`) are excluded from the repository with `.gitignore` – we should not post them publicly, as [Eric Wastl requested for](https://twitter.com/ericwastl/status/1465805354214830081).
 
-When the first puzzle appears, go to the `Day01.kt` and for each `part1` and `part2` functions, provide an algorithm implementation using the `input` data loaded from the `src/Day01.txt` file.
-This input data is common for both parts, and you can find it on the bottom of each day on the [Advent of Code][aoc] page.
+When the first puzzle appears, go to the `Day01.kt`, and for each `part1` and `part2` function, provide an algorithm implementation using the `input` data loaded from the `src/Day01.txt` file.
+This input data is common for both parts, and you can find it at the bottom of each day on the [Advent of Code][aoc] page.
 
 To read the input data, you can go with the `readInput(name: String)` utility method provided in the [`Utils.kt`][file:utils] file, like:
 
@@ -78,18 +78,18 @@ fun main() {
 
 ## Running
 
-To call the algorithm you're implementing, click on the green Play button next to the `fun main()` definition.
+To call the algorithm you're implementing, click the green Play button next to the `fun main()` definition.
 
 ![img.png](.github/readme/run.png)
 
 > [!IMPORTANT]
 >
-> Before running tasks or tests, make sure to create relevant files, like: `src/Day01.txt` or `src/Day01_test.txt`.
+> Create relevant files Before running tasks or tests, like: `src/Day01.txt` or `src/Day01_test.txt`.
 
 The [`Utils.kt`][file:utils] file also contains the `String.md5()` method for generating MD5 hash out of the given string and expects more helper functions for the sake of the [KISS principle][kiss].
 
 Each puzzle describes some test conditions, a small portion of the information that helps check if the produced value for the given test input is valid.
-To handle that case, you can put such an input into a separated file and perform a check against the output, like:
+To handle that case, you can put such an input into a separate file and perform a check against the output, like:
 
 ```kotlin
 fun main() {
@@ -101,11 +101,11 @@ fun main() {
 ```
 
 The current approach of providing both `part1` and `part2` solutions within the single `Day##.kt` file may sometimes bring a disadvantage due to the first solution calculation when we expect to work on the second part only.
-With simple cases that don't consume too much of your time and resources that can be almost unnoticeable, but when solution takes seconds, it is worth considering breaking daily solution into two separated pieces, like `Day07_part1.kt` and `Day07_part2.kt`.
+With simple cases that don't consume too much of your time and resources that can be almost unnoticeable, but when the solution takes seconds, it is worth considering breaking the daily solution into two separated pieces, like `Day07_part1.kt` and `Day07_part2.kt`.
 
 The final result of your algorithm will be printed on the screen so that you can pass it to the Advent of Code website.
 
-To go with the next day, place the `Day02.txt` file into the `src` with relevant input data and create `Day02.kt` file with a similar code scaffold:
+To go with the next day, place the `Day02.txt` file into the `src` with relevant input data and create a `Day02.kt` file with a similar code scaffold:
 
 ```kotlin
 fun main() {
@@ -124,14 +124,14 @@ fun main() {
 ```
 
 > [!NOTE]
-> 
-> There is a fork of this repository available which utilizes the Amper tool for project configuration, recently [introduced by JetBrains][amper].
-> 
-> For more, see: [Advent of Code Kotlin Template — Amper][amper-template] project.
+>
+> There is a fork of this repository available that utilizes the Amper tool for project configuration, recently [introduced by JetBrains][amper].
+>
+> For more, see [Advent of Code Kotlin Template — Amper][amper-template] project.
 
 ## Getting help
 
-If you stuck with Kotlin-specific questions or anything related to this template, check out the following resources:
+If you are stuck with Kotlin-specific questions or anything related to this template, check out the following resources:
 
 - [Kotlin docs][docs]
 - [Kotlin Slack][slack]