From 76844ff330395a617bf449b307961d38aab03b31 Mon Sep 17 00:00:00 2001
From: ChAr-De <69584019+ChAr-De@users.noreply.github.com>
Date: Tue, 14 Jan 2025 09:54:53 +0100
Subject: [PATCH] Fix broken Numpy style guide link.

---
 docs/developer-guide/style-guide.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/developer-guide/style-guide.rst b/docs/developer-guide/style-guide.rst
index e1493817bd1..3dbfa9ad7c6 100644
--- a/docs/developer-guide/style-guide.rst
+++ b/docs/developer-guide/style-guide.rst
@@ -23,7 +23,7 @@ All functions, classes, and modules should contain appropriate API
 documentation in their *docstrings*.  The *docstrings* should be
 written in ReStructuredText format (same as the Sphinx high-level
 documentation), and should follow the `NumPy Docstring Standards
-<https://github.com/numpy/numpy/blob/master/doc/HOWTO_DOCUMENT.rst.txt#docstring-standard>`_
+<https://numpydoc.readthedocs.io/en/latest/format.html#docstring-standard>`_
 
 Documentation for all algorithms should contain citations to external
 works, which should be collected in ``bibliography.rst``. An example of