anchor.diff:  auth  bootstrap.ign  master.ign  metadata.json  worker.ign
   ----
   
  -At this point, you can use the Ignition config files as input to the ISO or PXE bare
  +Now you can use the Ignition config files as input to the ISO or PXE bare
   metal installation procedures to install {op-system-first} systems.
   
   [id="installation-user-infra-machines-advanced_retaindisk_{context}"]
   === Retaining existing partitions
   For an ISO installation, you can add options to the `coreos-installer`
   that causes the installer to maintain one or more existing partitions.
  -For a PXE installation, you can APPEND coreos.inst options to preserve partitions.
  +For a PXE installation, you can APPEND `coreos.inst` options to preserve partitions.
   
   Saved partitions might be partitions from an existing {product-title}
  -system that has data partitions that you want to keep or partitions
  +system that has data partitions that you want to keep, or partitions
   that you just manually created. Here are a few tips:
   
   * Make sure you assign at least the recommended amount of disk space to the
  
positive.code: * Creating separate partitions: For greenfield installations on an empty
  disk, you may want to add separate storage to a partition. This is only
  officially supported for making `/var` or a subdirectory of `/var` a separate
  partition (not both). If you create more than one partitoin, Kubernetes
  will not be able to monitor them both.
  
  * Retaining existing partitions: For a brownfield installation, where you
  
negative.code: ----
  
  . Create a MachineConfig and add it to a file in the `openshift` directory.
  For example, name the file `98-var-partition.yaml`,
  change the device name to the name of the storage device on the `worker` systems,
  and set the storage size as appropriate. This attaches storage to a separate `/var`
  directory.
  
  +
  