From 86d074540d36e7fa9f71ada79c139043b9ecaff8 Mon Sep 17 00:00:00 2001
From: Vecko <36369090+VeckoTheGecko@users.noreply.github.com>
Date: Thu, 6 Feb 2025 10:19:55 +0100
Subject: [PATCH] DOC: Fix 404

---
 doc/internals/chunked-arrays.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/internals/chunked-arrays.rst b/doc/internals/chunked-arrays.rst
index eb0a8b197e7..9694ace8748 100644
--- a/doc/internals/chunked-arrays.rst
+++ b/doc/internals/chunked-arrays.rst
@@ -13,7 +13,7 @@ Alternative chunked array types
 Xarray can wrap chunked dask arrays (see :ref:`dask`), but can also wrap any other chunked array type that exposes the correct interface.
 This allows us to support using other frameworks for distributed and out-of-core processing, with user code still written as xarray commands.
 In particular xarray also supports wrapping :py:class:`cubed.Array` objects
-(see `Cubed's documentation <https://tom-e-white.com/cubed/>`_ and the `cubed-xarray package <https://github.com/xarray-contrib/cubed-xarray>`_).
+(see `Cubed's documentation <https://cubed-dev.github.io/cubed/>`_ and the `cubed-xarray package <https://github.com/xarray-contrib/cubed-xarray>`_).
 
 The basic idea is that by wrapping an array that has an explicit notion of ``.chunks``, xarray can expose control over
 the choice of chunking scheme to users via methods like :py:meth:`DataArray.chunk` whilst the wrapped array actually