anchor.diff:  |`imagefs.inodesFree` = `node.stats.runtime.imagefs.inodesFree`
   |===
   
  -The node supports two filesystem partitions when detecting disk pressure.
  -
  -* The `nodefs` filesystem that the node uses for local disk volumes, daemon logs, etc (i.e. the filesystem that provides `/`)
  -* The `imagefs` filesystem that the container runtime uses for storing images and individual container writable layers.
  -
  -The node auto-discovers these filesystems using `cAdvisor`.
  -
  -If you store volumes and logs in a dedicated filesystem, the node will not monitor that filesystem at this time.
  +The node supports two file system partitions when detecting disk pressure.
  +
  +* The `nodefs` file system that the node uses for local disk volumes, daemon logs,
  +and so on (for example, the file system that provides `/`).
  +* The `imagefs` file system that the container runtime uses for storing images and
  +individual container writable layers.
  +
  +The node auto-discovers these file systems using `cAdvisor`.
  +
  +If you store volumes and logs in a dedicated file system, the node will not
  +monitor that file system at this time.
   
   [NOTE]
   ====
  -In this release, the node supports the ability to trigger eviction decisions
  -based on disk pressure.  Operators must opt-in to enable disk based evictions this
  -release.  Prior to evicting pods due to disk pressure, the node will also perform
  -container and image garbage collection.  For more detail on garbage collection, see
  +As of {product-title} 3.4, the node supports the ability to trigger eviction
  +decisions based on disk pressure. Operators must opt in to enable disk-based
  +evictions. Prior to evicting pods due to disk pressure, the node will also
  +perform
   xref:../admin_guide/garbage_collection.adoc#admin-guide-garbage-collection[container
  -and image garbage collection].  In future releases, garbage collection will be deprecated
  -in favor of a pure disk eviction based configuration.
  +and image garbage collection]. In future releases, garbage collection will be
  +deprecated in favor of a pure disk eviction based configuration.
   ====
   
   [[out-of-resource-eviction-thresholds]]
  
positive.code: 
  As a result, if a pod is evicted as a consequence of consuming too much disk in
  an `EmptyDir` volume, the pod will be evicted, but the local volume usage will
  not be reclaimed by the node.  The node will keep evicting pods on the node to
  prevent total exhaustion of disk.  Operators can reclaim the disk by manually
  deleting the evicted pods from the node once terminated.
  
  This will be remedied in a future release.
  
negative.code: the strategy targets the largest consumer of the starved resource.
  * `Guaranteed`: pods that consume the most of the starved resource relative to
  their request are failed first. If no pod has exceeded its request, the strategy
  targets the largest consumer of the starved resource.
  
  A `Guaranteed` pod will never be evicted because of another pod's resource
  consumption unless a system daemon (node, *docker*, *journald*, etc) is
  