chore: minor grammar fixes to docs (#805)

From https://github.com/aspect-build/docs/pull/171

Author: alexeagle

lint/bandit.bzl

@@ -2,7 +2,7 @@
 
 Typical usage:
 
-First, fetch `bandit[sarif]` package via your standard requirements file and pip calls.
+First, fetch `bandit[sarif]` package via your standard requirements file and python rules (pip, uv, etc).
 
 Note that the `sarif` extra is **required** for machine output and the `toml` extra
 is recommended to enable `pyproject.toml` support, see examples.
@@ -136,7 +136,7 @@ def lint_bandit_aspect(
     """A factory function to create a linter aspect.
 
     Args:
-        binary: a bandit executable. Can be obtained from pypi like so:
+        binary: a bandit executable. Obtain from pypi like so:
 
             load("@rules_python//python/entry_points:py_console_script_binary.bzl", "py_console_script_binary")
 

lint/buf.bzl

@@ -104,7 +104,7 @@ def lint_buf_aspect(config, toolchain = "@rules_buf//tools/protoc-gen-buf-lint:t
     """A factory function to create a linter aspect.
 
     Args:
-        config: label of the the buf.yaml file
+        config: label of the buf.yaml file
         toolchain: override the default toolchain of the protoc-gen-buf-lint tool
         rule_kinds: which [kinds](https://bazel.build/query/language#kind) of rules should be visited by the aspect
     """

lint/checkstyle.bzl

@@ -38,7 +38,7 @@ def checkstyle_action(ctx, executable, srcs, config, data, stdout, exit_code = N
 
     Args:
         ctx: Bazel Rule or Aspect evaluation context
-        executable: label of the the Checkstyle program
+        executable: label of the Checkstyle program
         srcs: java files to be linted
         config: label of the checkstyle.xml file
         data: labels of additional xml files such as suppressions.xml
@@ -112,7 +112,7 @@ def lint_checkstyle_aspect(binary, config, data = [], rule_kinds = ["java_binary
     """A factory function to create a linter aspect.
 
     Attrs:
-        binary: a Checkstyle executable. Can be obtained from rules_java like so:
+        binary: a Checkstyle executable. Obtain from rules_java like so:
 
             java_binary(
                 name = "checkstyle",

lint/flake8.bzl

@@ -2,7 +2,7 @@
 
 Typical usage:
 
-First, fetch the flake8 package via your standard requirements file and pip calls.
+First, fetch the flake8 package via your standard requirements file and python rules (pip, uv, etc).
 
 Then, declare a binary target for it, typically in `tools/lint/BUILD.bazel`:
 
@@ -37,7 +37,7 @@ def flake8_action(ctx, executable, srcs, config, stdout, exit_code = None, optio
 
     Args:
         ctx: Bazel Rule or Aspect evaluation context
-        executable: label of the the flake8 program
+        executable: label of the flake8 program
         srcs: python files to be linted
         config: label of the flake8 config file (setup.cfg, tox.ini, or .flake8)
         stdout: output file containing stdout of flake8
@@ -97,7 +97,7 @@ def lint_flake8_aspect(binary, config, rule_kinds = ["py_binary", "py_library"])
     """A factory function to create a linter aspect.
 
     Attrs:
-        binary: a flake8 executable. Can be obtained from rules_python like so:
+        binary: a flake8 executable. Obtain from rules_python like so:
 
             load("@rules_python//python/entry_points:py_console_script_binary.bzl", "py_console_script_binary")
 

lint/keep_sorted.bzl

@@ -38,7 +38,7 @@ def keep_sorted_action(ctx, executable, srcs, stdout, exit_code = None, options
 
     Args:
         ctx: Bazel Rule or Aspect evaluation context
-        executable: label of the the keep-sorted program
+        executable: label of the keep-sorted program
         srcs: files to be linted
         stdout: output file containing stdout
         exit_code: output file containing exit code

lint/pmd.bzl

@@ -38,7 +38,7 @@ def pmd_action(ctx, executable, srcs, rulesets, stdout, exit_code = None, option
 
     Args:
         ctx: Bazel Rule or Aspect evaluation context
-        executable: label of the the PMD program
+        executable: label of the PMD program
         srcs: java files to be linted
         rulesets: list of labels of the PMD ruleset files
         stdout: output file to generate
@@ -108,7 +108,7 @@ def lint_pmd_aspect(binary, rulesets, rule_kinds = ["java_binary", "java_library
     """A factory function to create a linter aspect.
 
     Attrs:
-        binary: a PMD executable. Can be obtained from rules_java like so:
+        binary: a PMD executable. Obtain from rules_java like so:
 
             java_binary(
                 name = "pmd",

lint/pylint.bzl

@@ -2,7 +2,7 @@
 
 Typical usage:
 
-First, fetch the pylint package via your standard requirements file and pip calls.
+First, fetch the pylint package via your standard requirements file and python rules (pip, uv, etc).
 
 Then, declare a binary target for it, typically in `tools/lint/BUILD.bazel`:
 
@@ -104,7 +104,7 @@ def lint_pylint_aspect(binary, config, rule_kinds = ["py_binary", "py_library",
     """A factory function to create a linter aspect.
 
     Args:
-        binary: a pylint executable. Can be obtained from rules_python like so:
+        binary: a pylint executable. Obtain from rules_python like so:
 
             load("@rules_python//python/entry_points:py_console_script_binary.bzl", "py_console_script_binary")
 

lint/rubocop.bzl

@@ -124,7 +124,7 @@ def rubocop_action(
     This means that a change to any config file invalidates the action cache
     entries for ALL RuboCop actions.
 
-    However this is needed because RuboCop's logic for selecting the
+    However, this is important because RuboCop's logic for selecting the
     appropriate config needs to traverse the directory hierarchy.
 
     Args:

lint/ruff.bzl

@@ -60,14 +60,14 @@ def ruff_action(ctx, executable, srcs, config, stdout, exit_code = None, env = {
     This means that a change to any config file invalidates the action cache entries for ALL
     ruff actions.
 
-    However this is needed because:
+    However, this is important because:
 
     1. ruff has an `extend` field, so it may need to read more than one config file
     2. ruff's logic for selecting the appropriate config needs to read the file content to detect a `[tool.ruff]` section.
 
     Args:
         ctx: Bazel Rule or Aspect evaluation context
-        executable: label of the the ruff program
+        executable: label of the ruff program
         srcs: python files to be linted
         config: labels of ruff config files (pyproject.toml, ruff.toml, or .ruff.toml)
         stdout: output file of linter results to generate

lint/shellcheck.bzl

@@ -26,7 +26,7 @@ def shellcheck_action(ctx, executable, srcs, config, stdout, exit_code = None, o
 
     Args:
         ctx: Bazel Rule or Aspect evaluation context
-        executable: label of the the shellcheck program
+        executable: label of the shellcheck program
         srcs: bash files to be linted
         config: label of the .shellcheckrc file
         stdout: output file containing stdout of shellcheck