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: 
  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:
  
  * **static**: IP is explicitly requested by the user in the deployment manifest
  * **automatic**: IP is selected automatically based on the network type
  
  ---
  
negative.code: - Configuring the IaaS: outside of BOSH's responsibility
    - Example on AWS: User creates a VPC and subnets with routing tables.
  - Adding networks section to the deployment manifest to define networks used in this deployment
    - Example: User adds a static network with a subnet and adds AWS subnet ID into the subnet's cloud properties.
  - Adding network associations for one or more networks to each deployment job
  
  All deployment manifests have a similar structure in terms of network definitions and associations:
  