anchor.diff:    - name: my-other-network
     ...
   
  -- name: my-static-job
  -  networks:
  -  - name: my-network
  -    # Static IP reservations for `my-job`
  -    static_ips: [IP1]
  +- name: my-manual-job
  +  networks:
  +  - name: my-network
  +    # Manual IP reservations for `my-job`
  +    manual_ips: [IP1]
     ...
   ```
   
   See how to define each network type below.
   
   ---
  -## <a id='manual'></a> Manual Networks
  -
  -Manual networking allows you to specify one or more subnets and let the Director choose available IPs from one of the subnet ranges. A subnet definition specifies the CIDR range and, optionally, the gateway and DNS servers. In addition, certain IPs can be blacklisted (the Director will not use these IPs) via the `reserved` property.
  -
  -Each manual network attached to a job instance is typically represented as its own NIC in the IaaS layer.
  -
  -Schema for manual network definition:
  +## <a id='static'></a> Static Networks
  +
  +Static networking allows you to specify one or more subnets and let the Director choose available IPs from one of the subnet ranges. A subnet definition specifies the CIDR range and, optionally, the gateway and DNS servers. In addition, certain IPs can be blacklisted (the Director will not use these IPs) via the `reserved` property.
  +
  +Each static network attached to a job instance is typically represented as its own NIC in the IaaS layer.
  +
  +Schema for static network definition:
   
   * **name** [String, required]: Name used to reference this network configuration
  -* **type** [String, required]: Value should be `manual`
  +* **type** [String, required]: Value should be `static`
   * **subnets** [Array, required]: Lists subnets in this network
     * **range** [String, required]: Subnet IP range that includes all IPs from this subnet
     * **gateway** [String, optional]: Subnet gateway IP
     * **dns** [Array, optional]: DNS IP addresses for this subnet
     * **reserved** [Array, optional]: Array of reserved IPs and/or IP ranges. BOSH does not assign IPs from this range to any VM
  -  * **static** [Array, optional]: Array of static IPs and/or IP ranges. BOSH assigns IPs from this range to jobs requesting static IPs. Only IPs specified here can be used for static IP reservations.
  +  * **manual** [Array, optional]: Array of manual IPs and/or IP ranges. BOSH assigns IPs from this range to jobs requesting manual IPs. Only IPs specified here can be used for manual IP reservations.
     * **cloud_properties** [Hash, required]: Describes any IaaS-specific properties for the subnet. May be empty.
   
   Example:
  
positive.code: 
  vSphere CPI supports:
  
  - Multiple manual networks for each job instance
  - No dynamic networks since vSphere does not manage IP assignments
  - No vip networks since vSphere does not have an elastic/floating IP concept
  
  AWS CPI supports:
  
  - Single manual network for each job instance
  - Single dynamic network for each job instance
  - Single vip network which corresponds to an elastic IP
  
  OpenStack CPI supports:
  
  - Multiple manual networks for each job instance
  - Single dynamic network for each job instance
  - Single vip network which corresponds to a floating IP
  
  vCloud CPI supports:
  
  - Multiple manual networks for each job instance
  - No dynamic networks since vSphere does not manage IP assignments
  - No vip networks since vSphere does not have an elastic/floating IP concept
  
  
negative.code:   ...
    networks:
    - name: my-network
      manual_ips: [54.47.189.8]
  ```
  
  Unlike the static networking setup, manual IPs for VIP networks are only specified on the deployment job.
  
  ---
  ## <a id='multi-homed'></a> Multi-homed VMs
  