From fe17926eade322dab248b8a64a79aad0e80484a2 Mon Sep 17 00:00:00 2001 From: Mark Fussell Date: Fri, 11 Oct 2024 21:32:30 +0100 Subject: [PATCH] Fixed typo (#4389) --- .../content/en/operations/support/support-release-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/operations/support/support-release-policy.md b/daprdocs/content/en/operations/support/support-release-policy.md index e11b34ff342..fbba03b5f14 100644 --- a/daprdocs/content/en/operations/support/support-release-policy.md +++ b/daprdocs/content/en/operations/support/support-release-policy.md @@ -24,7 +24,7 @@ A supported release means: From the 1.8.0 release onwards three (3) versions of Dapr are supported; the current and previous two (2) versions. Typically these are `MINOR`release updates. This means that there is a rolling window that moves forward for supported releases and it is your operational responsibility to remain up to date with these supported versions. If you have an older version of Dapr you may have to do intermediate upgrades to get to a supported version. -There will be at least 13 weeks (3 months) between major.minor version releases giving users at least a 9 month rolling window for upgrading from a non-supported version. For more details on the releaase process read [release cycle and cadence](https://github.com/dapr/community/blob/master/release-process.md) +There will be at least 13 weeks (3 months) between major.minor version releases giving users at least a 9 month rolling window for upgrading from a non-supported version. For more details on the release process read [release cycle and cadence](https://github.com/dapr/community/blob/master/release-process.md) Patch support is for supported versions (current and previous).