diff --git a/.github/workflows/vale-docs-linter.yml b/.github/workflows/vale-docs-linter.yml
index 43404c4cf6..ea36c75d34 100644
--- a/.github/workflows/vale-docs-linter.yml
+++ b/.github/workflows/vale-docs-linter.yml
@@ -23,8 +23,15 @@ jobs:
       - name: run reviewdog and linter
         uses: errata-ai/vale-action@reviewdog
         with:
+          # tj-actions/changed-files emits a space-separated list, so telling the
+          # action it is comma-separated made it pass Vale one argument holding
+          # every path joined by spaces. That is a valid path only when a PR
+          # changed exactly one file, so from 2023 this check worked on
+          # single-file PRs and silently skipped every larger one: Vale answers
+          # an unmatched path with an empty result and exit 0. See
+          # docs-tracking#375.
           files: ${{ steps.changed-files.outputs.all_changed_and_modified_files }}
-          separator: ","
+          separator: " "
           # added, diff_context, file, nofilter
           filter_mode: file
           # github-pr-check, github-pr-review, github-check
diff --git a/litefs/how-it-works.mdx b/litefs/how-it-works.mdx
index b95df6a419..2de40ac544 100644
--- a/litefs/how-it-works.mdx
+++ b/litefs/how-it-works.mdx
@@ -85,7 +85,7 @@ rolling checksum.
 ## Cluster management using leases
 
 SQLite operates as a single-writer database which means only one transaction can
-write at a time. Because of this, we utilize a lease system whereby a single
+write at a time. Because of this, we use a lease system whereby a single
 node acts as the "primary" node at any given time. All writes should be directed
 to that node and it will propagate changes to the rest of the cluster.