Bug 1658995

Summary:	Upgrade documentation is referring v3.9.43 as the latest version
Product:	OpenShift Container Platform	Reporter:	Oscar Casal Sanchez <ocasalsa>
Component:	Documentation	Assignee:	Vikram Goyal <vigoyal>
Status:	CLOSED WONTFIX	QA Contact:	Xiaoli Tian <xtian>
Severity:	low	Docs Contact:	Vikram Goyal <vigoyal>
Priority:	unspecified
Version:	3.9.0	CC:	aos-bugs, jokerman, lmartinh, mmccomas, rsandu
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-14 09:46:18 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Oscar Casal Sanchez 2018-12-13 10:54:04 UTC

Document URL: 

https://docs.openshift.com/container-platform/3.9/upgrading/automated_upgrades.html#verifying-the-upgrade

and

https://access.redhat.com/documentation/en-us/openshift_container_platform/3.9/html-single/upgrading_clusters/

Section Number and Name: 


Describe the issue: 

As a user I can read several times in the documentation:

"Replace <tag> with v3.9.43 for the latest version." or "use v3.9.43 for the latest version"

But v3.9.43 is not more the latest version. The v3.9.51 is the latest.

Suggestions for improvement: 

If the documentation indicates the specify X.Y.Z version, it's going to be updated always that the version changes. It could be better to write:

"Replace <tag> with the latest version." or "use the latest version"

And indicate a place where the user could check what is the latest version

Additional information: