anchor.diff:  from the CLI by running the following `oc` patch command:
   +
   ----
  -$ TARGET_NAMESPACE=openshift-cnv HCO_CHANNEL=2.2 oc patch -n "${TARGET_NAMESPACE}" $(oc get subscription -n ${TARGET_NAMESPACE} --no-headers -o name) --type='json' -p='[{"op": "replace", "path": "/spec/channel", "value":"'"${HCO_CHANNEL}"'"}, {"op": "replace", "path": "/spec/installPlanApproval", "value":"Automatic"}]'
  -----
  -+
  -This command points your subscription to upgrade channel `2.2` and enables automatic
  -updates.
  +$ TARGET_NAMESPACE=openshift-cnv HCO_CHANNEL=2.2 oc patch -n "${TARGET_NAMESPACE}" $(oc get subscription -n ${TARGET_NAMESPACE} --no-headers -o name) --type='json' -p='[{"op": "replace", "path": "/spec/channel", "value":"${HCO_CHANNEL}"}, {"op": "replace", "path": "/spec/installPlanApproval", "value":"Automatic"}]'
  +----
  ++
  +This command points your subscription to upgrade channel `2.2` and enables automatic updates.
  
positive.code: 
  == Known issues
  
  * If you have {CNVProductName} 2.1.0 deployed, you must first upgrade to 2.2.0
  before upgrading {product-title}.
  
  // Don't remove: this BZ is probably true for all 2.x releases
  * The `masquerade` binding method for virtual machines cannot be used in clusters with RHEL 7 compute nodes.
  
negative.code: :context: cnv-release-notes
  toc::[]
  
  == About {CNVProductName} {CNVVersion}
  
  include::modules/cnv-what-you-can-do-with-cnv.adoc[leveloffset=+2]
  