diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
index db8b1131a..e092c419c 100644
--- a/.pre-commit-config.yaml
+++ b/.pre-commit-config.yaml
@@ -15,7 +15,7 @@ repos:
   - id: trailing-whitespace
 
 - repo: https://github.com/codespell-project/codespell
-  rev: v2.3.0
+  rev: v2.4.1
   hooks:
   - id: codespell
     args: ["-L", "ned,ist,oder", "--skip", "*.po"]
@@ -37,7 +37,7 @@ repos:
   - id: rst-inline-touching-normal
 
 - repo: https://github.com/astral-sh/ruff-pre-commit
-  rev: v0.7.1
+  rev: v0.12.2
   hooks:
     - id: ruff
     - id: ruff-format
diff --git a/source/specifications/pylock-toml.rst b/source/specifications/pylock-toml.rst
index d21294cf9..342e608c5 100644
--- a/source/specifications/pylock-toml.rst
+++ b/source/specifications/pylock-toml.rst
@@ -672,12 +672,12 @@ See :ref:`pylock-packages-archive-hashes`.
 
 - **Type**: array of tables
 - **Required?**: no
-- **Inspiration**: :ref:`  provenance-object`
+- **Inspiration**: :ref:`provenance-object`
 - A recording of the attestations for **any** file recorded for this package.
 - If available, tools SHOULD include the attestation identities found.
 - Publisher-specific keys are to be included in the table as-is
   (i.e. top-level), following the spec at
-  :ref:`  index-hosted-attestations`.
+  :ref:`index-hosted-attestations`.
 
 
 .. _pylock-packages-attestation-identities-kind:
@@ -687,7 +687,7 @@ See :ref:`pylock-packages-archive-hashes`.
 
 - **Type**: string
 - **Required?**: yes
-- **Inspiration**: :ref:`  provenance-object`
+- **Inspiration**: :ref:`provenance-object`
 - The unique identity of the Trusted Publisher.
 
 
@@ -698,9 +698,9 @@ See :ref:`pylock-packages-archive-hashes`.
 
 - **Type**: table
 - **Required?**: no
-- **Inspiration**: :ref:`  pyproject-tool-table`
+- **Inspiration**: :ref:`pyproject-tool-table`
 - Similar usage as that of the :ref:`pylock-tool` table from the
-  :ref:`  pyproject-toml-spec`, but at the package version level instead
+  :ref:`pyproject-toml-spec`, but at the package version level instead
   of at the lock file level (which is also available via :ref:`pylock-tool`).
 - Data recorded in the table MUST be disposable (i.e. it MUST NOT affect
   installation).