comments wording

Author: aignas

docs/sphinx/pip.md

@@ -72,7 +72,7 @@ If you would like to access [entry points][whl_ep], see the `py_console_script_b
 (per-os-arch-requirements)=
 ## Requirements for a specific OS/Architecture
 
-IN some cases you may need to use different requirements files for different OS, Arch combinations. This is enabled via the `requirements_by_platform` attribute in `pip.parse` extension and the `pip_parse` repository rule. The keys of the dictionary are labels to the file and the values are a list of comma separated target (os, arch) tuples.
+In some cases you may need to use different requirements files for different OS, Arch combinations. This is enabled via the `requirements_by_platform` attribute in `pip.parse` extension and the `pip_parse` repository rule. The keys of the dictionary are labels to the file and the values are a list of comma separated target (os, arch) tuples.
 
 For example:
 ```starlark

python/pip_install/pip_repository.bzl

@@ -613,7 +613,7 @@ pip_repository_attrs = {
         doc = """\
 The requirements files and the comma delimited list of target platforms as values.
 
-The keys are the requirement files and the values are coma-separated platform
+The keys are the requirement files and the values are comma-separated platform
 identifiers. For now we only support `<os>_<cpu>` values that are present in
 `@platforms//os` and `@platforms//cpu` packages respectively.
 """,

python/private/parse_requirements.bzl

@@ -14,7 +14,7 @@
 
 """Requirements parsing for whl_library creation.
 
-Usecases that the code needs to cover:
+Use cases that the code needs to cover:
 * A single requirements_lock file that is used for the host platform.
 * Per-OS requirements_lock files that are used for the host platform.
 * A target platform specific requirements_lock that is used with extra