anchor.diff:  		</tr>
   		<tr>
   			<td><code>PUBLIC-BROKER-IP</code></td>
  -			<td>A pre-allocated AWS Elastic IP address</td>
  +			<td>A pre-allocated AWS Elastic IP address.</td>
   		</tr>
   		<tr>
   			<td><code>SECURITY-GROUP</code></td>
  
positive.code: $ cd nfs-volume-release
  </pre>
  
  1. Run the following script to generate a deployment manifest based on your stubs:
  <pre class="terminal">
  $ ./scripts/generate_manifest.sh cf.yml director-uuid.yml iaas.yml creds.yml
  </pre>
  	* Specify the path to each stub file you created.
  
  ###<a id="broker"></a>Deploy the NFS Broker
  
  
negative.code: 
  ###<a id="stubs"></a> Generate a Manifest for the NFS Broker
  
  To create an NFS Service Broker, you must combine several pieces of information into a single BOSH manifest to deploy. Follow the steps below to put this information into stubs, then use a script to combine the stubs into a manifest.
  
  #### Create the Cloud Foundry Stub
  1. Run the following command to list the VMs deployed by your BOSH Director:
  	<pre class="terminal">$ bosh vms </pre>
  	* Examine the output for the Cloud Foundry NATS VM labeled `nats_*` and record the corresponding `deployment name` for use in the next step.
  1. Run the following command using the `deployment name` from the previous step to download your CF deployment manifest:
    <pre class="terminal"> $ bosh download manifest YOUR-CF-DEPLOYMENT-NAME > cf.yml</pre>
  
  