From 335b7eee93632e8696074d54f01aaee03f716a70 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?V=C3=ADt=20Ku=C4=8Dera?=
 <26327373+vkucera@users.noreply.github.com>
Date: Thu, 4 Jun 2026 19:32:11 +0200
Subject: [PATCH] O2 linter: Be more specific about the action log section

---
 docs/tools/o2linter.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/tools/o2linter.md b/docs/tools/o2linter.md
index ef9f93e9..8f3c16d5 100644
--- a/docs/tools/o2linter.md
+++ b/docs/tools/o2linter.md
@@ -51,13 +51,13 @@ In your fork O2Physics repository go to: "Settings -> Actions -> General -> Acti
 When you push to your remote branch, O2 linter will lint the files modified compared to the remote master branch in your fork.
 (If you want to lint only your commits, make sure your remote master branch is up to date.)
 
-The output can be found in the log of the GitHub action.
+The output can be found in the "Run tests" step of the log of the GitHub action.
 
 ### In GitHub pull requests
 
 O2 linter runs automatically on pull requests and lints files modified by the PR (compared to the target branch).
 
-The total numbers of errors, warnings, and disabled issues are reported for convenience as an auto-updating comment in the PR, while the detailed breakdown per test remains available in the log of the GitHub action.
+The total numbers of errors, warnings, and disabled issues are reported for convenience as an auto-updating comment in the PR, while the detailed breakdown per test remains available in the "Run tests" step of the log of the GitHub action.
 
 The first ten errors also appear as annotations directly in the source code.