Section Number and Name:
"System Containers for docker, CRI-O"
Describe the issue:
1. In the table it says that support for docker and CRI-O system containers is deprecated. Then, in the link  it shows how to configure docker to run as a system container.
2. The link  has no explanation of how to run CRI-O as a system container.
3. The release notes  suggest that the default installation of CRI-O will be as a system container - "This setting pulls the openshift3/cri-o system container image from the Red Hat Registry by default."
4. I attempted an install of OCP 3.9 with Ansible inventory setting (openshift_use_crio=true) and it fails. I tried both an RPM install and a Container install, neither option will cause CRI-O to be installed.
5. In the release notes , it says - "The atomic-openshift-node service must be RPM- or system container-based when using CRI-O" but there are is no description of how to run atomic-openshift-node as a system container anywhere in the release notes, nor under the advanced installation instructions for system containers .
6. There is a reference to running "kublet" as a system container in the release notes  - "System Container for installer and Kubelet" - but, when you follow that link , there is only a description of how to run the installer as a system container.
Suggestions for improvement:
Sorry for the complex description, but I have installed/uninstalled OCP 3.9 in every possible permutation. There is too much conflicting documentation to determine what the right way is. I have even manually installed the RPMs, then ran the Ansible installer, but that fails as well.
Need to rewrite CRI-O docs, based on the above description. Consider moving CRI-O docs into main docs set once corrected.
*** Bug 1570142 has been marked as a duplicate of this bug. ***
These issues (from above) were corrected in the latest OpenShift 3.9 docs :
1) Description of the CRI-O system container was removed.
2) No need to document how to use CRI-O as a system container.
3) Default CRI-O installation is now noted as being RPM-based.
4) The RPM install is now properly documented.
5) All references to CRI-O as a system container are gone.
6) Reference to kubelet was removed.