Update documentation.

Author: Jadarma

README.md

@@ -96,7 +96,7 @@ In the above example:
    Inside the lambda you can define test cases.
    The `Solution` functions will only be invoked if the relevant part DSL is used.
    If you have not yet implemented the second part, or it doesn't exist
-   _(e.g.: Every year, part two of the last day just requires collecting all other 49 stars)_,
+   _(e.g.: Every year, part two of the last day just requires collecting all other stars)_,
    then you may simply omit it.
 5. To define a test case, use the `shouldOutput` function.
    Each usage will define another test case.

docs/topics/debugging.md

@@ -33,7 +33,7 @@ class Y9999D01 : AdventSpec<Y9999D01>({
         solution.partOne(input)
     }
 
-    // Every other declarations are effectively ignored ...
+    // Any other declarations are effectively ignored ...
 })
 ```
 

docs/topics/multiple-solutions.md

@@ -1,7 +1,7 @@
 # Multiple Solutions
 
 You sometimes might want to implement multiple solutions to the same puzzle.
-For example to compare imperative vs. functional code styles, or test different data structures, or algorithms.
+For example, to compare imperative vs. functional code styles, or test different data structures and algorithms.
 
 Since all these different implementations solve the same puzzle, they should have identical test cases.
 The `AdventSpec` is designed to test a single `Solution` at a time.

docs/topics/overview.md

@@ -121,7 +121,7 @@ In the above example:
    Inside the lambda you can define test cases.
    The `Solution` functions will only be invoked if the relevant part DSL is used.
    If you have not yet implemented the second part, or it doesn't exist
-   _(e.g.: Every year, part two of the last day just requires collecting all other 49 stars)_,
+   _(e.g.: Every year, part two of the last day just requires collecting all other stars)_,
    then you may simply omit it.
 5. To define a test case, use the `shouldOutput` function.
    Each usage will define another test case.

docs/topics/project-extension.md

@@ -25,7 +25,7 @@ It offers the following features:
 
     `AdventSpec`s will always execute in chronological order.
     All other specs will run before them, in the order they were discovered.
-    Note that this overrides Kotest's own [spec ordering`](https://kotest.io/docs/framework/spec-ordering.html).
+    Note that this overrides Kotest's own [spec ordering](https://kotest.io/docs/framework/spec-ordering.html).
 
 ## Registering The Extension
 
@@ -40,17 +40,7 @@ object TestConfig : AbstractProjectConfig() {
 }
 ```
 
-To make Kotest use this configuration, you must register it in the 
-[`kotest.properties`](https://kotest.io/docs/intellij/intellij-properties.html#specifying-the-properties-filename)
-file in your `src/test/resources`:
-
-```properties
-kotest.framework.config.fqn=my.aoc.TestConfig
-kotest.framework.classpath.scanning.autoscan.disable=true
-kotest.framework.classpath.scanning.config.disable=true
-```
-
-You should also register the fqn as a system property for Gradle:
+To make Kotest use this configuration, you must register the FQN as a system property for Gradle:
 
 ```kotlin
 tasks.test {

docs/topics/workflow.md

@@ -29,8 +29,8 @@ projectDir
 │  └── aockt
 │     └── y2015
 │        └── d01
-│           └── input.txt
-│           └── solution_part1.txt
+│           ├── input.txt
+│           ├── solution_part1.txt
 │           └── solution_part2.txt
 ├── solutions
 │  └── aockt
@@ -80,7 +80,7 @@ projectDir
     - Each day has a directory as a base path: `/aockt/y[year]/d[twoDigitDay]`
     - In that directory, the input is in the `input.txt` file.
     - The solutions use `solution_part1.txt` and `solution_part2.txt`.
-      They are added in as discovered.
+      They are added in gradually, as discovered.
 
 > ***DO NOT Commit Puzzle Inputs!***
 > 
@@ -121,7 +121,7 @@ object Y2015D01 : Solution
 
 > Your class _must have_ a zero-arg constructor.
 
-Following the same logic, create its `tests` analog:
+Following the same logic, create its `tests` counterpart:
 
 ```kotlin
 package aockt.y2015
@@ -155,7 +155,7 @@ class Y2015D01Test : AdventSpec<Y2015D01>({
 })
 ```
 
-Like many other puzzles, this day provides you with example inputs and outputs to test your solution.
+Like many other puzzles, this day provides you with example inputs and outputs to test your solution with.
 
 If that is the case, you can define them in a lambda.
 The syntax is `"string" shouldOutput "output"`, the output can be a string, or a number, it will be checked against its
@@ -188,7 +188,7 @@ Your first run should look like this:
 
 Each example has its own test, and since you added your input, it also tests against that.
 
-> If you're not interested in running on our input until validating the examples, you can
+> If you're not interested in running against your input until validating the examples first, you can
 > [ignore your input](test-config.md#executionmode) by setting:
 > 
 > `partOne(executionMode = ExecMode.ExamplesOnly)`
@@ -251,7 +251,7 @@ Go back to the website and submit it.
 
 **Congratulations on collecting the first star!** ⭐
 
-If not, try to look at what's special in your input, or hunt down any bugs.
+If not, try to look at what's special in your input, or [hunt down bugs](debugging.md).
 
 Once you have verified the right answer, paste it in `inputs/aockt/y2015/d01/solution_part1.txt`.
 Now, when you run the test, your code will be tested against the known answer: