diff --git a/.github/workflows/docs-linkcheck.yml b/.github/workflows/docs-linkcheck.yml
index f34fcc17d..ea78626c3 100644
--- a/.github/workflows/docs-linkcheck.yml
+++ b/.github/workflows/docs-linkcheck.yml
@@ -3,6 +3,9 @@ on:
   schedule:
     # First day of month at 05:46 in every 2nd month
     - cron: '46 5 1 */2 *'
+  pull_request:
+    paths:
+      - .github/workflows/docs-linkcheck.yml
 
 jobs:
   test-sphinx-build:
@@ -10,7 +13,7 @@ jobs:
     runs-on: ${{matrix.os}}
     strategy:
       matrix:
-        python-version: [3.10]
+        python-version: ['3.10']
         os: [ubuntu-latest]
       fail-fast: False
     steps:
diff --git a/README.rst b/README.rst
index 035180a3c..aba1c2c09 100644
--- a/README.rst
+++ b/README.rst
@@ -121,7 +121,7 @@ To enable you to verify that a release file that you downloaded was indeed provi
 
 Starting with v21.4, all releases are signed via `sigstore <https://www.sigstore.dev>`_.
 The corresponding signature files are uploaded to the `GitHub releases page`_.
-To verify the signature, please install the `sigstore Python client <https://pypi.org/project/sigstore/>`_ and follow the instructions for `verifying signatures from GitHub Actions <https://github.com/sigstore/sigstore-python#signatures-from-github-actions>`_. As input for the ``--repository`` parameter, please use the value ``python-telegram-bot/python-telegram-bot``.
+To verify the signature, please install the `sigstore Python client <https://pypi.org/project/sigstore/>`_ and follow the instructions for `verifying signatures from GitHub Actions <https://github.com/sigstore/sigstore-python?tab=readme-ov-file>`_. As input for the ``--repository`` parameter, please use the value ``python-telegram-bot/python-telegram-bot``.
 
 Earlier releases are signed with a GPG key.
 The signatures are uploaded to both the `GitHub releases page`_ and the `PyPI project <https://pypi.org/project/python-telegram-bot/>`_ and end with a suffix ``.asc``.
@@ -232,4 +232,4 @@ License
 You may copy, distribute and modify the software provided that modifications are described and licensed for free under `LGPL-3 <https://www.gnu.org/licenses/lgpl-3.0.html>`_.
 Derivatives works (including modifications or anything statically linked to the library) can only be redistributed under LGPL-3, but applications that use the library don't have to be.
 
-.. _`GitHub releases page`: https://github.com/python-telegram-bot/python-telegram-bot/releases>
+.. _`GitHub releases page`: https://github.com/python-telegram-bot/python-telegram-bot/releases
diff --git a/telegram/_files/inputfile.py b/telegram/_files/inputfile.py
index d376d16a1..61e5a9419 100644
--- a/telegram/_files/inputfile.py
+++ b/telegram/_files/inputfile.py
@@ -56,8 +56,8 @@ class InputFile:
         read_file_handle (:obj:`bool`, optional): If :obj:`True` and :paramref:`obj` is a file
             handle, the data will be read from the file handle on initialization of this object.
             If :obj:`False`, the file handle will be passed on to the
-            `networking backend <telegram.request.BaseRequest.do_request>`_ which will have to
-            handle the reading. Defaults to :obj:`True`.
+            :attr:`networking backend <telegram.request.BaseRequest.do_request>` which will have
+            to handle the reading. Defaults to :obj:`True`.
 
             Tip:
                 If you upload extremely large files, you may want to set this to :obj:`False` to