Apply suggestions from code review

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Author: rozza

CLAUDE.md

@@ -79,9 +79,10 @@ public APIs, and never advise users to depend on them.
 
 ## Code Style and Formatting
 
-Formatting is checked automatically via `./gradlew spotlessCheck` which runs
-as part of `check`. Use `./gradlew spotlessApply` to auto-fix formatting issues.
-Do not manually reformat files outside the scope of your changes.
+Formatting is enforced automatically because the Gradle `check` task depends on
+`./gradlew spotlessApply`, which formats sources. To run a check without modifying
+files, invoke `./gradlew spotlessCheck` manually. Do not manually reformat files
+outside the scope of your changes.
 
 ### Style Rules
 

driver-core/CLAUDE.md

@@ -25,7 +25,7 @@ Core driver internals shared by all driver variants (sync, reactive, Kotlin, Sca
 
 - Every package must have a `package-info.java`
 - Most extensive test suite — JUnit 5 + Spock (Groovy) + Mockito. Match surrounding patterns carefully.
-- `BuildConfig` is auto-generated by the `com.github.gmazzo.buildconfig` Gradle plugin — run `./gradlew generateBuildConfig` if missing
+- `com.mongodb.internal.build.MongoDriverVersion` is auto-generated by the `com.github.gmazzo.buildconfig` Gradle plugin — run `./gradlew :driver-core:generateMongoDriverVersion` if missing
 - Never block in async code paths
 
 ## Key Patterns