diff --git a/doc/user-guide/weather-climate.rst b/doc/user-guide/weather-climate.rst
index 97513ef1175..7ba72cccefc 100644
--- a/doc/user-guide/weather-climate.rst
+++ b/doc/user-guide/weather-climate.rst
@@ -279,3 +279,64 @@ For data indexed by a :py:class:`~xarray.CFTimeIndex` xarray currently supports:
 .. _precision range: https://pandas.pydata.org/pandas-docs/stable/user_guide/timeseries.html#timestamp-limitations
 .. _ISO 8601 standard: https://en.wikipedia.org/wiki/ISO_8601
 .. _partial datetime string indexing: https://pandas.pydata.org/pandas-docs/stable/user_guide/timeseries.html#partial-string-indexing
+
+.. _cftime_arithmetic_limitations:
+
+Arithmetic limitations with non-standard calendars
+--------------------------------------------------
+
+A current limitation when working with non-standard calendars and :py:class:`cftime.datetime`
+objects is that they support arithmetic with :py:class:`datetime.timedelta`, but **not** with :py:class:`numpy.timedelta64`.
+
+This means that certain xarray operations (such as :py:meth:`~xarray.DataArray.diff`)
+may produce ``timedelta64`` results that cannot be directly combined with ``cftime`` coordinates.
+
+For example, lets define a cftime DataArray with a no-leap calendar:
+
+.. jupyter-execute::
+
+    import xarray as xr
+    import numpy as np
+    import pandas as pd
+    import cftime
+
+    time = xr.DataArray(
+        xr.date_range("2000", periods=3, freq="MS", calendar="noleap"),
+        dims="time"
+    )
+
+If you want to compute, e.g., midpoints in the time intervals, this will not work:
+
+.. code-block:: python
+
+    # Attempt to compute midpoints
+    time[:-1] + 0.5 * time.diff("time")
+
+and result in an error like this:
+
+.. code-block:: none
+
+   UFuncTypeError: ufunc 'add' cannot use operands with types dtype('O') and dtype('<m8[ns]')
+
+This is because :py:meth:`~xarray.DataArray.diff` returns ``timedelta64``, which is not
+compatible with ``cftime.datetime``.
+
+**Workarounds**
+
+One possible workaround is to use :py:meth:`numpy.diff` on the underlying values,
+which returns ``datetime.timedelta`` objects that are compatible:
+
+.. jupyter-execute::
+
+    mids = time[:-1] + 0.5 * np.diff(time.values)
+
+or you can convert ``timedelta64`` values to Python ``timedelta`` objects explicitly,
+for example via :py:meth:`pandas.to_timedelta`:
+
+.. jupyter-execute::
+
+    td = pd.to_timedelta(time.diff("time").values).to_pytimedelta()
+    mids = time[:-1] + 0.5 * td
+
+These limitations stem from the ``cftime`` library itself; arithmetic between
+``cftime.datetime`` and ``numpy.timedelta64`` is not implemented.
diff --git a/doc/whats-new.rst b/doc/whats-new.rst
index a46dba9f15a..f4808686af2 100644
--- a/doc/whats-new.rst
+++ b/doc/whats-new.rst
@@ -44,6 +44,8 @@ Bug fixes
 Documentation
 ~~~~~~~~~~~~~
 
+- Added section on the `limitations of CFtime arithmetics <https://docs.xarray.dev/en/stable/user-guide/weather-climate.html#arithmetic-limitations-with-non-standard-calendars>`_ (:pull:`10653`).
+  By `Lars Buntemeyer <https://github.com/larsbuntemeyer>`_
 
 Internal Changes
 ~~~~~~~~~~~~~~~~