anchor.diff:  
   * `/var/lib/containers`: Holds container-related content that can grow
   as more images and containers are added to a system.
  -* `/var/log`: Holds logging data that you might want to keep separate for
  -auditing purposes later.
  -
  -Storing the contents of a `/var` directory separately lets you more easily
  -grow storage to those areas as needed and possibly reinstall {product-title}
  +* `/var`: Holds data that you might want to keep separate for purposes such as
  +auditing.
  +
  +Storing the contents of a `/var` directory separately allows you to more easily
  +grow storage to those areas as needed, and to reinstall {product-title}
   at a later date and keep that data intact. In other words, you would not have
   to pull all your containers again or copy off massive log files when you
   update your systems.
  
positive.code: 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
  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.
  
  Saved partitions might be partitions from an existing {product-title}
  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
  
negative.code: 
  For an ISO installation:
  
  The following example illustrates running `coreos-installer` in a way that preserves
  the sixth (6) partition on the disk:
  
  [source,terminal]
  