anchor.diff:  ### <a id='network'></a> The network block ###
   
   The `network` block is where you specify network configuration information for the deployment.
  -
  -**Note**: This block is named "network" (singular) for MicroBOSH, as opposed to "networks" (plural)
  +This block is named "network" (singular) for MicroBOSH, as opposed to "networks" (plural)
   for multi-VM BOSH.
  +
  +The `type` attribute can be set to either of two values:
  +
  +* `dynamic` means that DHCP is used to assign the MicroBOSH VM an IP address.
  +* `manual` means that you set the IP address for the MicroBOSH VM, in the manifest.
  +
  +The `dns` sub-block is for nameservers you want the operating system of the MicroBOSH VM to use.
  +They are written to the `/etc/resolv.conf` file.
  +MicroBOSH components could use them to resolve IaaS FQDNs, for example.
  +
  +The optional `vip` attribute allows you to assign a floating IP address to the MicroBOSH VM.
  +Then you can access the VM from outside of the its network.
  +If set, `allocated_floating_ip` **must** be a floating IP that was allocated before you deploy.
  +
  +The `network` sub-block is IaaS-dependent, because subnets, and other
  +keys may differ from IaaS to IaaS.
   
   For example:
   
  
positive.code:       private_key: <path_to_microbosh_keypar_private_key>
  ~~~
  
  * The `auth_url` option set your [OpenStack identity](http://www.openstack.org/software/openstack-shared-services/) server.
  * The `username`, `api_key` and `tenant` options sets your OpenStack credentials.
  * The `region` option is optional, and allows you to set the OpenStack region to be used.
  * The `default_security_groups` option set the security groups used by Micro BOSH. The `microbosh_security_group` **must** be an existing security group.
  * The `default_key_name` and `private_key` options sets the key pair used by Micro BOSH. The `microbosh_keypair` **must** be an existing keypair.
  
  ### <a id="ex-vsphere"></a> vSphere ###
  
  Explanatory comments follow this example.
  
  ~~~yaml
  ---
  
negative.code:   netmask: <netmask_for_the_subnet_you_are_deploying_to>
    gateway: <gateway_for_the_subnet_you_are_deploying_to>
    dns:
    # The micro-bosh VM has the following DNS entries in its /etc/resolv.conf, allowing it to resolve, for example, IaaS FQDNs.
    - <ip_for_dns>
    cloud_properties:
      name: <network_name_according_to_vsphere>
  