Value Statement

Ensure the issue title clearly reflects the value of this spike story.
(Explain the "WHY")

• ACM currently uses the phrase "upgrade" to describe both the available OCP versions for hub/managed clusters and the action of "upgrading" clusters. OpenShift OCP itself however, has made an organized effort to consolidate their use of this language to "update"/"updates", and have added the language to their official glossary.
  • https://github.com/openshift/openshift-docs/pull/40525
  • https://github.com/openshift/openshift-docs/blob/a68b6073254a76d1369185875f7ffcb317c459f8/contributing_to_docs/term_glossary.adoc#update 
• Our product management leadership has expressed approval with aligning on "updates" (though followup action has not yet been prioritized). (Slack)
• This spike will track an assessment and itemization of locations where "upgrade" is used in the ACM Console, tasks to seek approval on new language (where necessary) and if containable, stories to deliver updated language and achieve alignment, and finally, a task to provide a broadcast for the broader organization, to bring attention to the use of update over upgrade. 
• Note: The stated goals are relatively broad in scope for tracking in a Spike, but the overhead in terms of coding is so minimal that for practical reasons it makes sense to keep this effort self-contained.

Definition of Done for Engineering Story Owner (Checklist)

• We provide a list (spreadsheet?) of affected copy within the console.
• Where necessary we solicit feedback from Doc or UX for new copy and store it (in the same spreadsheet).
• We replace the old copy in the console.
• We broadcast to the organization that we will use update in the ACM console moving forward.

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.