anchor.diff:  ----
   ====
   
  -We have a couple different options for consuming this ConfigMap in a volume.  The most basic
  -way is to populate the volume with files where the key is the filename and the content of the file
  -is the value of the key:
  +You have a couple different options for consuming this `*ConfigMap*` in a
  +volume. The most basic way is to populate the volume with files where the key is
  +the file name and the content of the file is the value of the key:
   
   ====
   [source,yaml]
  
positive.code: ----
  ====
  
  We can consume the keys of this ConfigMap in a pod like so:
  
  ====
  [source,yaml]
  
negative.code: ----
  ====
  
  You can also control the paths within the volume where `*ConfigMap*` keys are
  projected:
  
  ====
  [source,yaml]
  