diff --git a/docs/blog/posts/2026-09-20-clang-tidy-pull-requests-github-actions.md b/docs/blog/posts/2026-09-20-clang-tidy-pull-requests-github-actions.md
index e544037..5ffd258 100644
--- a/docs/blog/posts/2026-09-20-clang-tidy-pull-requests-github-actions.md
+++ b/docs/blog/posts/2026-09-20-clang-tidy-pull-requests-github-actions.md
@@ -107,8 +107,11 @@ language standard of the real build. It reads them from a compilation database,
 
 Two things commonly go wrong here:
 
-- **Third-party dependencies.** If the configure step runs `find_package(Foo)`, install
-  `libfoo-dev` (or restore your vcpkg/Conan cache) before it, exactly as your build job does.
+- **Third-party libraries.** clang-tidy finds a library's headers only through the `-I` paths
+  the compiler gets for each file, and it reads those from the database. Install the library
+  before the configure step, as your build job does (`libfoo-dev`, or your vcpkg or Conan cache),
+  so `find_package(Foo)` succeeds and its include paths are recorded. Without a build system, add
+  the paths to `extra-args` yourself, for example `-Ithird_party/fmt/include`.
 - **Generated headers.** Protobuf output, `config.h` and similar files only exist after the build
   step that produces them. Build those targets before running clang-tidy.
 
diff --git a/docs/overrides/home.html b/docs/overrides/home.html
index bdbc9a7..d81922f 100644
--- a/docs/overrides/home.html
+++ b/docs/overrides/home.html
@@ -282,7 +282,7 @@ <h3 class="cl-h3">Thread Comment</h3>
               <h3 class="cl-h3">Step Summary</h3>
               <code class="cl-inline-code">step-summary</code>
             </div>
-            <p>Set step-summary: true and the same report is added to the job summary of the workflow run. It needs no write access, so it also works on pull requests from forks and in private repositories, where thread comments are turned off.</p>
+            <p>Set step-summary: true and the same report is added to the job summary of the workflow run. It needs no write access, so it also works on pull requests from forks.</p>
           </article>
           <article class="cl-outcome">
             <div class="cl-outcome__art" aria-hidden="true">