The "Performing RevisionBased update" section could be improved by showing the actual name of the Istio resource and the underlying IstioRevision resources. Right now, we don't show that the name of the IstioRevision is comprised of the Istio name and the version.

We also don't say anything about the automatic cleanup of the old IstioRevision once all the workloads have been moved to the new revision. We should explain the Istio.spec.updateStrategy.inactiveRevisionDeletionGracePeriodSeconds field in this section.

We should also explain that it's okay to run two IstioRevisions for an extended period of time and what a canary rollout would look like. This could be explained in the existing procedure or added as a new procedure explicitly explaining a canary rollout.

As OSSM 3.0 only supports one Istio version, we can defer these docs changes until OSSM 3.1.