anchor.diff:  	    release: nfs-volume
   	    properties: {}
   	```
  -1. Update the runtime configuration:
  +1. Update the BOSH runtime configuration:
   	<pre class="terminal">$ bosh update runtime-config runtime-config.yml</pre>
   1. Download the Diego manifest:
  -	<pre class="terminal">$ bosh download manifest <YOUR DIEGO DEPLOYMENT NAME> diego.yml</pre>
  +	<pre class="terminal">$ bosh download manifest YOUR-DIEGO-DEPLOYMENT-NAME > diego.yml</pre>
   1. Deploy Diego:
   	<pre class="terminal"> $ bosh -d diego.yml deploy</pre>
   
  -###<a id="stubs"></a>Step 2: Create Stub Files and Generate Manifest
  +###<a id="stubs"></a>Step 3: Create NFS Broker VM - Create Stub Files
  +
  +In order to create a NFS Service Broker we need to combine pieces of information into a single BOSH manifest that we will deploy. We will put these pieces into stubs and then utilize a script to combine them.
   
   #### Cloud Foundry Stub
  -
  -Run the following command to download your CF deployment manifest:
  -<pre class="terminal"> $ bosh download manifest YOUR-CF-DEPLOYMENT-NAME > cf.yml</pre>
  +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 CF Nats VM labeled `nats_*` and note the corresponding `deployment name` for use in the next step.
  +1. Run the following command using the `deployment name` from the last step to download your CF deployment manifest:
  +  <pre class="terminal"> $ bosh download manifest YOUR-CF-DEPLOYMENT-NAME > cf.yml</pre>
   
   #### Director Stub
   
   1. Run the following command to determine the UUID of your BOSH director:
   	<pre class="terminal"> $ bosh status --uuid</pre>
   
  -2. Create a new `director.yml` file with the following contents:
  +2. Create a new `director.yml` file with the following contents from the last step:
   
   	```
   	---
  
positive.code: 
  #### IaaS Settings Stub
  
  Create an `iaas.yml` file with the following contents, replacing the values where indicated:
  
  GIVE SOME EXPLANATION OF THIS FILE AND THE VALUES TO REPLACE
  
  	```
  	 ---
  
negative.code:     password: <BROKER_PASSWORD>
  ```
  
  #### Step 2: Create NFS Broker VM - Generate the Deployment Manifest
  
  1. Download the script from github using the `git cli`
  <pre class="terminal">
  $ git clone https://github.com/cloudfoundry-incubator/nfs-volume-release.git
  </pre>
  
  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>
  
  ###<a id="broker"></a>Step 4: Create NFS Broker VM - Deploy the Broker
  
  1. Deploy the broker using the generated manifest:
  	<pre class="terminal">
  	$ bosh -d nfsvolume-aws-manifest.yml deploy
  	</pre>
  
  1. Register the broker using the credentials specified in the `creds.yml` and grant access to it's service with the following commands
  
  	<pre class="terminal">
  	$ cf create-service-broker nfsbroker <BROKER_USERNAME> <BROKER_PASSWORD> http://nfs-broker.YOUR.DOMAIN.com
  	$ cf enable-service-access nfs
  	</pre>
  
  	CF Developers can now create an NFS service and bind instances to their apps as outlined in [Using Volume Services](../volume-services-v2.10.html)
  