Document URL: 
https://docs.openshift.com/container-platform/4.3/cnv/cnv_install/installing-container-native-virtualization.html#cnv-deploying-cnv_installing-container-native-virtualization

Section Number and Name:
Deploying container-native virtualization, point 3

Describe the issue:
On point 3, the document says:
Click the KubeVirt HyperConverged Cluster Operator Deployment tab and click Create HyperConverged Cluster.

And everything will be fine if the user simply confirms the proposed example as (implicitly) suggested in the doc.
On the other side, nothing on OCP admin console is explicitly preventing the user from trying to edit the proposed CR changing its name.

Even in 2.2, hco will only look for a CR named "hyperconverged-cluster", see:
https://github.com/kubevirt/hyperconverged-cluster-operator/blob/release-2.2/pkg/controller/hyperconverged/hyperconverged_controller.go#L48

Suggestions for improvement: 
I'd suggest to add an explicit comment/note/warning saying that the HyperConverged Cluster CR can be named only hyperconverged-cluster (which is the value proposed by default).

Additional information:
We are already documenting something similar for the name of the namespace:
You must only install the Operator in the openshift-cnv namespace.

In 2.3, as a new feature, we implemented a validation mechanism to explicitly fail at creation time on CR with a different name but we don't have it on 2.2.