comment: update CHANGELOG notes

CHANGELOG.md

@@ -58,11 +58,11 @@ A brief description of the categories of changes:
 * (coverage): coverage reports are now created when the version-aware
   rules are used.
   ([#1600](https://github.com/bazelbuild/rules_python/issues/1600))
-* (bzlmod pip.parse) Use the same interpreter label that may make the lock file
-  almost the same for all platforms. It will, however be different in cases where
-  the lock file is introducing platform-specific deps (e.g. `colorama` may be
-  present only in the `windows` specific requirements lock file because it
-  is not used elsewhere.
+* (bzlmod pip.parse) Use a platform-independent reference to the interpreter
+  pip uses. This reduces (but doesn't eliminate) the amount of
+  platform-specific content in `MODULE.bazel.lock` files; Follow
+  [#1643](https://github.com/bazelbuild/rules_python/issues/1643) for removing
+  platform-specific content in `MODULE.bazel.lock` files.
 
 ### Added
 
@@ -74,7 +74,8 @@ A brief description of the categories of changes:
   that is suffixed with `_host`, that has a single label `:python` that is a
   symlink to the python interpreter for the host platform. The intended use is
   mainly in `repository_rule`, which are always run using `host` platform
-  Python.
+  Python. This means that `WORKSPACE` users can now copy the `requirements.bzl`
+  file for vendoring as seen in the updated `pip_parse_vendored` example.
 
 [0.XX.0]: https://github.com/bazelbuild/rules_python/releases/tag/0.XX.0