From 2c845a92899b6c3d333241c9380903b0dfb35b46 Mon Sep 17 00:00:00 2001 From: Michael Kubacki Date: Thu, 19 Sep 2024 15:17:35 -0400 Subject: [PATCH] Fix typo --- docs/How/release_process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/How/release_process.md b/docs/How/release_process.md index 8457b42f8..8c8978f32 100644 --- a/docs/How/release_process.md +++ b/docs/How/release_process.md @@ -46,7 +46,7 @@ content is considered stable. Moving forward, only bug and security fixes will b order to maintain its stability. All downstream consumers should always consume from the release branch, unless they are testing out new functionality only present in the dev branch. Project Mu will continue back porting bug and security fixes to release branches as part of LTS (Long-Term Support) for at least the next two releases (though it may be -longer based on community needs). Once LTS has ended, the releae branch will be archived following the process described +longer based on community needs). Once LTS has ended, the release branch will be archived following the process described [below](#post-lts-and-archiving). It is then a choice of the downstream consumer on when to upgrade release branches; this may be at a regular cadence or may stop after shipping a platform. For example, downstream consumers must