edit

paigecalvert · paigecalvert · commit 1e664298768a · 2025-09-02T17:17:55.000-06:00
diff --git a/docs/partials/releases/_required-releases-description.mdx b/docs/partials/releases/_required-releases-description.mdx
@@ -1,3 +1,3 @@
 When a release is required, KOTS requires users to upgrade to that version before they can upgrade to a later version. For example, if you select **Prevent this release from being skipped during upgrades** for release 2.0.0, users with 1.5.0 deployed must upgrade to 2.0.0 before they can upgrade to 2.1.0.
 
-You can disable the **Prevent this release from being skipped during upgrades** option after promoting a release if needed to allow users to skip the release during upgrades. After a release's properties are changed in the Vendor Portal, its metadata is updated in the Admin Console the next time that an upstream update occurs.
+You can disable the **Prevent this release from being skipped during upgrades** option after promoting a release if needed. After a release's properties are changed in the Vendor Portal, its metadata is updated in the Admin Console the next time that an upstream update occurs.

Original file line number	Diff line number	Diff line change
`@@ -1,3 +1,3 @@`
`1`	`1`	`When a release is required, KOTS requires users to upgrade to that version before they can upgrade to a later version. For example, if you select Prevent this release from being skipped during upgrades for release 2.0.0, users with 1.5.0 deployed must upgrade to 2.0.0 before they can upgrade to 2.1.0.`
`2`	`2`
`3`		`-You can disable the Prevent this release from being skipped during upgrades option after promoting a release if needed to allow users to skip the release during upgrades. After a release's properties are changed in the Vendor Portal, its metadata is updated in the Admin Console the next time that an upstream update occurs.`
	`3`	`+You can disable the Prevent this release from being skipped during upgrades option after promoting a release if needed. After a release's properties are changed in the Vendor Portal, its metadata is updated in the Admin Console the next time that an upstream update occurs.`