anchor.diff:      static_ips: [10.10.1.11, 10.10.1.12]
   ```
   
  -<p class="note"><strong>Note</strong>: If deployment job uses static IP reservation, all instances must be given static IPs.</p>
  -
  -A common problem that you may run into is configuring multiple deployments to use overlapping IP range. The Director does _not_ consider an IP as used even if that same Director used that IP in a different deployment. There are two possible solutions for this problem: reconfigure one of the deployments to use a different IP range or use the same IP range but configure each deployment such that reserved IPs exclude each deployment from each other.
  -
  -<p class="note">Note: It is not guranteed which available IP is picked but you might notice that the Director usually picks next available IP.</p>
  +<p class="note"><strong>Note</strong>: If a deployment job uses static IP reservation, all instances must be given static IPs.</p>
  +
  +A common problem that you may run into is configuring multiple deployments to use overlapping IP ranges. The Director does not consider an IP to be "used" even if the Director used that IP in a different deployment. There are two possible solutions for this problem: reconfigure one of the deployments to use a different IP range, or use the same IP range but configure each deployment such that reserved IPs exclude the deployment from each other.
  +
  +<p class="note">Note: While the Director usually selects the next available IP address, this behavior is not guaranteed.</p>
   
   ---
   ## <a id='dynamic'></a> Dynamic Networks
   
  -Dynamic networking defers IP selection to the IaaS. For example, AWS by default assigns a private IP to each instance in the VPC. By associating a deployment job to a dynamic network, BOSH will pick up AWS assigned private IP.
  +Dynamic networking defers IP selection to the IaaS. For example, AWS assigns a private IP to each instance in the VPC by default. By associating a deployment job to a dynamic network, BOSH will pick up AWS-assigned private IP addresses.
   
   Each dynamic network attached to a job instance is typically represented as its own NIC in the IaaS layer.
   
  
positive.code: 
  VIP networking enables the association of an IP address that is not backed by any particular NIC. This flexibility enables users to remap a virtual IP to a different instance in cases of a failure.
  
  VIP network attachment is not represented as a NIC in the IaaS layer. It is implemented by AWS CPI with [elastic IPs](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html), and on OpenStack CPI with [floating IPs](http://docs.openstack.org/user-guide/content/floating_ip_allocate.html).
  
  VIP networking only supports static IP reservations.
  
  Schema for VIP network definition:
  
  * **name** [String, required]: Name used to reference this network configuration.
  * **type** [String, required]: Value should be `vip`.
  * **cloud_properties** [Hash, required]: Describes any IaaS-specific properties for the network. May be empty.
  
  Example:
  
negative.code: title: Networks
  ---
  
  A BOSH network is an IaaS-agnostic representation of the networking layer. The Director is responsible for configuring each deployment job's networks with the help of the BOSH Agent and the IaaS. Networking configuration is usually assigned at the boot of the VM and/or when network configuration changes in the deployment manifest for already-running deployment jobs.
  
  There are three types of networks that BOSH supports:
  
  * **manual**: the Director decides how to assign IPs to each job instance based on the specified network subnets in the deployment manifest
  * **dynamic**: the Director defers IP selection to the IaaS
  * **vip**: the Director allows one-off IP assignments to specific jobs to enable flexible IP routing (e.g. elastic IP)
  
  Each type of network supports one or both IP reservation types:
  
  