small update in the docs regarding the changing behaviour of the gh actions bot

Author: Jolanrensen

CONTRIBUTING.md

@@ -60,7 +60,7 @@ so do familiarize yourself with the following guidelines.
 4. The contributor answers the comments or fixes the proposed PR.
 5. The reviewer marks the PR with the word "LGTM."
 6. The maintainer could suggest merging the `master` branch to the PR branch a few times due to changes in the `master` branch.
-7. If the PR influences generated code/samples, a bot will inform about this in the PR comments.
+7. If the PR influences generated code/samples, a bot will inform about this in the PR checks.
 8. The maintainer runs TeamCity builds (unit tests and examples as integration tests).
 9. TeamCity writes the result (passed or not passed) to the PR checks at the bottom of the proposed PR.
 10. If it is possible, maintainers share the details of the failed build with the contributor.

KDOC_PREPROCESSING.md

@@ -58,7 +58,7 @@ This can be seen in action in the `core:processKDocsMain` and `core:changeJarTas
 To make sure the generated sources can be seen and reviewed on GitHub,
 since [PR #731](https://github.com/Kotlin/dataframe/pull/731),
 there's a [GitHub action](.github/workflows/generated-sources.yml) that runs the `core:processKDocsMain` task and
-comments the results on the PR. After a PR is merged, [another action](.github/workflows/generated-sources-master.yml)
+shows the results in the PR checks. After a PR is merged, [another action](.github/workflows/generated-sources-master.yml)
 runs on the master branch and commits the generated sources automatically.
 This way, the generated sources are always up to date with the latest changes in the code.
 This means you don't have to run and commit the generated sources yourself, though it's