Remove reference to the logs admin page from docs

https://gitlab.com/gitlab-org/gitlab/-/merge_requests/31973

doc/administration/repository_checks.md

@@ -7,8 +7,8 @@ integrity of all data committed to a repository. GitLab administrators
 can trigger such a check for a project via the project page under the
 admin panel. The checks run asynchronously so it may take a few minutes
 before the check result is visible on the project admin page. If the
-checks failed you can see their output on the admin log page under
-'repocheck.log'.
+checks failed you can see their output on in the [`repocheck.log`
+file.](logs.md#repochecklog)
 
 NOTE: **Note:**
 It is OFF by default because it still causes too many false alarms.
@@ -31,12 +31,10 @@ panel.
 ## What to do if a check failed
 
 If the repository check fails for some repository you should look up the error
-in `repocheck.log`:
+in the [`repocheck.log` file](logs.md#repochecklog) on disk:
 
-- in the [admin panel](logs.md#repochecklog)
-- or on disk, see:
-  - `/var/log/gitlab/gitlab-rails` for Omnibus installations
-  - `/home/git/gitlab/log` for installations from source
+- `/var/log/gitlab/gitlab-rails` for Omnibus installations
+- `/home/git/gitlab/log` for installations from source
 
 If the periodic repository check causes false alarms, you can clear all repository check states by
 navigating to **Admin Area > Settings > Repository**