Skip to content

Commit f1649ef

Browse files
committed
Changed to in Update Channels section of upgrade docs
1 parent dbb1a99 commit f1649ef

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

modules/understanding-upgrade-channels.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,8 +13,8 @@ In {product-title} 4.1, Red Hat introduced the concept of channels for
1313
recommending the appropriate release versions for cluster upgrade. By controlling
1414
the pace of upgrades, these upgrade channels allow you to choose an upgrade
1515
strategy. Upgrade channels are tied to a minor version of
16-
{product-title}. For instance, {product-title} {product-version}
17-
upgrade channels will never include an upgrade to a 4.7 release. This strategy ensures that
16+
{product-title}. For instance, {product-title} 4.7
17+
upgrade channels will never include an upgrade to a 4.8 release. This strategy ensures that
1818
administrators explicitly decide to upgrade to the next minor version of
1919
{product-title}. Upgrade channels control only release selection and do not impact the version of the cluster that you install; the `openshift-install`
2020
binary file for a specific version of {product-title} always installs that version.

0 commit comments

Comments
 (0)