fix typos in HomeNames javadoc comments#956
Conversation
|
@edmoffo It is not a good idea to name Git branches the way you named this one: " |
|
@rultor merge |
@volodya-lombrozo OK, I'll try to merge now. You can check the progress of the merge here. |
@edmoffo @volodya-lombrozo Oops, I failed. You can see the full log here (spent 4min). |
|
@volodya-lombrozo Thanks for the review! You've earned +4 points for this: +12 as a basis; -8 for absolutely no comments posted; -4 for too few (6) hits-of-code; +4 to give you at least something. Your running score is +464; don't forget to check your Zerocracy account too). |
|
@rultor merge |
@volodya-lombrozo OK, I'll try to merge now. You can check the progress of the merge here. |
@edmoffo @volodya-lombrozo Oops, I failed. You can see the full log here (spent 4min). |
|
Thanks for the contribution! Unfortunately this PR cannot be merged as-is because the repo requires all commits to have verified GPG or SSH signatures, and your commit is unsigned. Please sign your commits (see https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) and feel free to reopen — we'd be happy to review it again. |
Three small wording errors in
src/main/groovy/org/eolang/lints/HomeNames.groovymade the javadoc harder to read. The phrasein the term of accessbecomesin terms of access, and twothe value us pathinstances becomethe value is path.The change touches only
@returndoc comments and one prose sentence insideplaceCsv()'s javadoc; no executable code, signatures, or test fixtures are altered.The fix is comment-only so no local build was needed; CI will run the standard
mvn clean install -Pqulicepipeline on the branch.