anchor.diff:  interrupt-parent = < &ipic >;
   ----
   
  -In Figure 2-4, the soc node specifies a ranges property of
  +In Figure 2-4, the ``soc`` node specifies a _ranges_ property of
   
   [listing]
   <0x0 0xe0000000 0x00100000>;
   
   This property value specifies that for an 1024KB range of address space,
   a child node addressed at physical 0x0 maps to a parent address of
  -physical 0xe0000000. With this mapping, the serial device node can be
  +physical 0xe0000000. With this mapping, the ``serial`` device node can be
   addressed by a load or store at address 0xe0004600, an offset of 0x4600
  -(specified in reg) plus the 0xe0000000 mapping specified in _ranges_.
  +(specified in _reg_) plus the 0xe0000000 mapping specified in _ranges_.
   
   ==== dma-ranges
   [cols="10,90"]
   |===
   |Property |_dma-ranges_
  -|Value type |<empty> or <prop-encoded-array> encoded as arbitrary number
  +|Value type |_<empty>_ or _<prop-encoded-array>_ encoded as arbitrary number
   of triplets of (_child-bus-address_, _parent-bus-address_, _length_).
   |===
   .Description
  
positive.code: 
  |virtual-reg |SD |<u32> or <u64> |
  See section 2.3.7. Specifies an effective address that maps to the first
  physical address specified in the reg property. This property is
  required if this device node is the system's console.
  |===
  
  
negative.code: 	reg = <0x000000001 0x00000000 0x00000001 0x00000000>;
  };
  
  The _reg_ property is used to define the address and size of the two
  memory ranges. The 2 GB I/O region is skipped. Note that the
  _#address-cells_ and _#size-cells_ properties of the root node specify a
  value of 2, which means that two 32-bit cells are required to define the
  address and length for the _reg_ property of the memory node.
  
  === Chosen
  The chosen node does not represent a real device in the system but
  