The following comments relate to inconsistencies and contextual issues identified in the OpenShift Data Foundation 4.18 documentation. These observations are intended to improve clarity and accuracy for readers referencing upgrade procedures and version-specific guidance. 

Link: 
https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.18/html/updating_openshift_data_foundation/overview-of-the-openshift-data-foundation-update-process_rhodf


Paragraph 4 
“OpenShift Data Foundation upgrades are tied to the OpenShift Container Platform upgrade to ensure that compatibility and interoperability are maintained with the OpenShift Container Platform. For OpenShift Data Foundation 4.18, OpenShift Container Platform 4.18 and 4.18 (when generally available) are supported.”


4.18 is repeated twice. 


Below paragraph 4 “Important” section 


“Due to fundamental Kubernetes design, all OpenShift Container Platform updates between minor versions must be serialized. You must update from OpenShift Container Platform 4.15 to 4.17 and then to 4.18. You cannot update from OpenShift Container Platform 4.17 to 4.18 directly. For more information, see Preparing to perform an EUS-to-EUS update of the Updating clusters guide in OpenShift Container Platform documentation.”


The paragraph above appears to contain conflicting or misleading information. OpenShift 4.15 is not an EUS (Extended Update Support) version, so referencing it in the context of EUS-to-EUS upgrades is confusing. Additionally, upgrading directly from 4.17 to 4.18 is a valid and supported path as part of the EUS upgrade flow from 4.16. This wording could mislead users into thinking that a 4.17 to 4.18 upgrade is unsupported when it is in fact required. I recommend reviewing and clarifying this section to avoid confusion.

“stable-4.17
You can use the stable-4.17 channel to upgrade from OpenShift Data Foundation 4.15 and upgrades within 4.17.”

The paragraph stating “You can use the stable-4.17 channel to upgrade from OpenShift Data Foundation 4.15 and upgrades within 4.17” appears to be out of context for the 4.18 documentation. This statement refers specifically to 4.17 channel behavior and should ideally reside in the 4.17 documentation set. Including it in the 4.18 context may cause confusion, as it does not reflect the upgrade paths relevant to the current documentation version.

    1.
    2.
    3.