Fix spelling and grammar issues in documentation

.agents/purpose.md

@@ -1,6 +1,6 @@
 # 🧠 Purpose
 
-> **EXECUTIVE SUMMARY**: This guide outlines how AI agents (ChatGPT, Codex, Junie, Claude, Gemeni)
+> **EXECUTIVE SUMMARY**: This guide outlines how AI agents (ChatGPT, Codex, Junie, Claude, Gemini)
 > collaborate on our Kotlin/Java project. It defines responsibilities, coding standards,
 > and workflows to maintain high code quality and architectural integrity.
 

.agents/running-builds.md

@@ -5,7 +5,7 @@
    ./gradlew build
    ```
 
-2. If Protobuf (`.proto`) files are modified run:
+2. If Protobuf (`.proto`) files are modified, run:
    ```bash
    ./gradlew clean build
    ```

README.md

@@ -8,11 +8,11 @@
 Spine Logging is a versatile library designed for Kotlin and Java projects, 
 with a potential for multi-platform use. 
 
-As for now, only JVM target is supported, with a JavaScript implementation 
+As of now, only JVM target is supported, with a JavaScript implementation 
 being our priority for future development.
 
 API and implementation are largely inspired by [Google Flogger][flogger],
-and the introduction of fluent logging API in [SLF4J in v2.0.0][fluent-slf4j].
+and the introduction of fluent logging API in [SLF4J v2.0.0][fluent-slf4j].
 
 ## Current status: Experimental
 

backends/probe-backend/README.md

@@ -12,7 +12,7 @@ instance or intercept the logged statements.
 
 ### Logging interception
 
-For log statements interception, this module exposes `captureLogData { ... }`. 
+For intercepting log statements, this module exposes `captureLogData { ... }`. 
 This function uses `DynamicBackendFactory` to catch all `LogData` emitted 
 during the execution of the passed `action`.
 

dependencies.md

@@ -1,6 +1,6 @@
 
 
-# Dependencies of `io.spine:spine-logging-fixtures:2.0.0-SNAPSHOT.258`
+# Dependencies of `io.spine:spine-logging-fixtures:2.0.0-SNAPSHOT.259`
 
 ## Runtime
 ## Compile, tests, and tooling

jvm/README.md

@@ -38,12 +38,12 @@ For example:
 
 Potentially, we can have different `Platform` implementations for different
 Java platforms. And this module was meant to generate different `PlatformProvider`
-classes on different platforms. But as for now, it always generates a provider
+classes on different platforms. But as of now, it always generates a provider
 that creates instances of `DefaultPlatform`.
 
 In the future, this module may be replaced with a single hard class. 
 
-Take a look on issue [#67](https://github.com/SpineEventEngine/logging/issues/67)
+Take a look at issue [#67](https://github.com/SpineEventEngine/logging/issues/67)
 for details.
 
 [flogger-github]: https://google.github.io/flogger

logging/README.md

@@ -3,7 +3,7 @@
 This module contains Spine Logging API.
 
 API and implementation are largely inspired by [Google Flogger][flogger] and
-the introduction of fluent logging API in [SLF4J in v2.0.0][fluent-slf4j].
+the introduction of fluent logging API in [SLF4J v2.0.0][fluent-slf4j].
 
 The library aims to be multiplatform, but as of now, only the JVM target is supported.
 

pom.xml

@@ -10,7 +10,7 @@ all modules and does not describe the project structure per-subproject.
  -->
 <groupId>io.spine</groupId>
 <artifactId>spine-logging</artifactId>
-<version>2.0.0-SNAPSHOT.258</version>
+<version>2.0.0-SNAPSHOT.259</version>
 
 <inceptionYear>2015</inceptionYear>
 

tests/smoke-test/README.md

@@ -11,19 +11,19 @@ better to have some real-life check-ups outside the development repository.
 
 ### Applicability
 
-As for now, it is only applicable to JVM modules. It is because testing involves usage 
-of JUL-based backend. This backend is default and allows to easier intercept the logged
+As of now, it is only applicable to JVM modules. It is because testing involves usage 
+of JUL-based backend. This backend is default and allows easier interception of the logged
 text for further assertion.
 
-Take a look on `AbstractLoggingSmokeTest` for usage example.
+Take a look at `AbstractLoggingSmokeTest` for usage example.
 
-Please note, presence of `spine-logging` and `spine-logging-backend` is expected due to 
-Gradle configuration of `jvm-module` script plugin, which is applied to Spine JVM modules.
+Please note, the presence of `spine-logging` and `spine-logging-backend` is expected due to 
+the Gradle configuration of `jvm-module` script plugin, which is applied to Spine JVM modules.
 
 `spine-logging` should be added manually if this smoke test is used in a module without
 `jvm-module` configuration:
 
 ```
 implementation("io.spine:spine-logging:$version")
-runtimeOnly("io.spine:spine-logging-backend:$version)
+runtimeOnly("io.spine:spine-logging-backend:$version")
 ```

version.gradle.kts

@@ -24,4 +24,4 @@
  * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  */
 
-val versionToPublish: String by extra("2.0.0-SNAPSHOT.258")
+val versionToPublish: String by extra("2.0.0-SNAPSHOT.259")