From 9fcfad426fcafd138a054e65a37707bf1960b75d Mon Sep 17 00:00:00 2001
From: Tom Nicholas <tom@cworthy.org>
Date: Wed, 4 Dec 2024 20:52:04 -0700
Subject: [PATCH] Update doc/getting-started-guide/faq.rst

Co-authored-by: Maximilian Roos <5635139+max-sixty@users.noreply.github.com>
---
 doc/getting-started-guide/faq.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/getting-started-guide/faq.rst b/doc/getting-started-guide/faq.rst
index 0b694085804..4f5795882d9 100644
--- a/doc/getting-started-guide/faq.rst
+++ b/doc/getting-started-guide/faq.rst
@@ -423,7 +423,7 @@ How stable is Xarray's API?
 
 Xarray tries very hard to maintain backwards compatibility in our :ref:`api` between released versions.
 Whilst we do occasionally make breaking changes in order to improve the library,
-we try to `signpost changes <https://docs.xarray.dev/en/stable/contributing.html#backwards-compatibility>`_ with ``DeprecationWarnings`` for many months in advance.
+we `signpost changes <https://docs.xarray.dev/en/stable/contributing.html#backwards-compatibility>`_ with ``DeprecationWarnings`` for many releases in advance.
 (An exception is bugs - whose behaviour we try to fix as soon as we notice them.)
 Our `test-driven development practices <https://docs.xarray.dev/en/stable/contributing.html#test-driven-development-code-writing>`_ help to ensure any accidental regressions are caught.
 This philosophy applies to everything in the `public API <https://docs.xarray.dev/en/stable/getting-started-guide/faq.html#what-parts-of-xarray-are-considered-public-api>`_.