anchor.diff:  
   ### <a id="registry"></a>Registry ###
   
  -When a VM is created, it has no "awareness" of its own IP address or other vital information, including:
  -
  -* an ID for the VM
  -* an ID for the volume reserved for the VM
  -* IDs for disks and other devices
  -* the network interface IP
  +VMs have no "awareness" of their own configuration information.
  +This includes IP addresses for the network interface, and IDs for the volume reserved for the VM, for the VM itself, and for disks and other devices.
   
   Agents obtain configuration information for their VMs in different ways, depending on cloud infrastructure.
   Some cloud infrastructures use the Registry for this purpose.
  
positive.code: For internal communication between the VMs that it creates, BOSH allows named DNS records.
  This means that instead of an IP address, one component could communicate with another by a host and domain name, for example:
  
      `http://postgres-db.my-deployment.com`
  
  PowerDNS is the Open Source DNS server that BOSH runs if you use this feature.
  
  ### <a id="postgres"></a> Postgres database ###
  
  
negative.code: Based on data from Health Monitor, two BOSH plugins can attempt to return VMs to a desired state.
  
  * The BOSH Resurrector can be enabled to automatically recreate VMs that disappear or whose Agent becomes unresponsive.
  * BOSH Cloud Check (`bosh cck`) is a CLI command that the user can run to fix a wide variety of issues that can arise in a distributed system.
  
  ### <a id="nats"></a> Messaging (NATS) ###
  
  