@@ -9,7 +9,7 @@ Runtime Requirements
 
 ``cuda.bindings`` supports the same platforms as CUDA. Runtime dependencies are:
 
-* Linux (x86-64, arm64) and Windows (x86-64)
+* Linux (x86-64, arm64) and Windows (x86-64, arm64)
 * Python 3.11 - 3.15
 * Driver: Linux (580.65.06 or later) Windows (580.88 or later)
 * Optionally, NVRTC, nvJitLink, nvFatBin, NVVM, cuFile, and cuDLA from CUDA Toolkit 13.x
@@ -124,20 +124,20 @@ updates for development.
 Requirements
 ^^^^^^^^^^^^
 
-* CUDA Toolkit headers[^1]
-* CUDA Runtime static library[^2]
-* A git clone of the repository that includes tags[^3]
+* CUDA Toolkit headers [#]_
+* CUDA Runtime static library [#]_
+* A git clone of the repository that includes tags [#]_
 
-[^1]: User projects that ``cimport`` CUDA symbols in Cython must also use CUDA Toolkit (CTK) types as provided by the ``cuda.bindings`` major.minor version. This results in CTK headers becoming a transitive dependency of downstream projects through CUDA Python.
+.. [#] User projects that ``cimport`` CUDA symbols in Cython must also use CUDA Toolkit (CTK) types as provided by the ``cuda.bindings`` major.minor version. This results in CTK headers becoming a transitive dependency of downstream projects through CUDA Python.
 
-[^2]: The CUDA Runtime static library (``libcudart_static.a`` on Linux, ``cudart_static.lib`` on Windows) is part of the CUDA Toolkit. If using conda packages, it is contained in the ``cuda-cudart-static`` package.
+.. [#] The CUDA Runtime static library (``libcudart_static.a`` on Linux, ``cudart_static.lib`` on Windows) is part of the CUDA Toolkit. If using conda packages, it is contained in the ``cuda-cudart-static`` package.
 
-[^3]: The version is derived from git tags via ``setuptools-scm``, so the clone
-must include tags reaching back to at least the latest ``v*`` tag. Do not use
-``--depth`` or ``--no-tags``: a clone without reachable tags can build with a
-bogus version such as ``0.1.dev1+g0d22cb444``. See `Cloning the repository
-<https://github.com/NVIDIA/cuda-python/blob/main/CONTRIBUTING.md#cloning-the-repository>`_
-for details.
+.. [#] The version is derived from git tags via ``setuptools-scm``, so the clone
+   must include tags reaching back to at least the latest ``v*`` tag. Do not use
+   ``--depth`` or ``--no-tags``: a clone without reachable tags can build with a
+   bogus version such as ``0.1.dev1+g0d22cb444``. See `Cloning the repository
+   <https://github.com/NVIDIA/cuda-python/blob/main/CONTRIBUTING.md#cloning-the-repository>`_
+   for details.
 
 Source builds require that the provided CUDA headers are of the same major.minor version as the ``cuda.bindings`` you're trying to build. Despite this requirement, note that the minor version compatibility is still maintained. The build checks the header before it compiles anything. A mismatch stops the build with a message that names the ``cuda.h`` it found and the version this source tree needs. Use the ``CUDA_PATH`` (or ``CUDA_HOME``) environment variable to specify the location of your headers. If both are set, ``CUDA_PATH`` takes precedence. For example, if your headers are located in ``/usr/local/cuda/include``, then you should set ``CUDA_PATH`` with: