anchor.diff:             instance_type: m3.large
              availability_zone: us-east-1c
   	```
  -#### Credentials Stub
  +
  +1. Replace each of the below parameters in the stub:
  +
  +	<table>
  +		<tr>
  +			<th width="25%">For this value...</th>
  +			<th>Replace with...</th>
  +		</tr>
  +		<tr>
  +			<td><code>PUBLIC-BROKER-IP</code></td>
  +			<td>A pre-allocated AWS Elastic IP address</td>
  +		</tr>
  +		<tr>
  +			<td><code>SECURITY-GROUP</code></td>
  +			<td>A Security Group in which to create the NFS Broker. Ensure this security group can access the security group that your CF deployment is in.</td>
  +		</tr>
  +		<tr>
  +			<td><code>SUBNET</code></td>
  +			<td>A subnet in which to create the NFS Broker. Ensure this subnet can access the subnet that your CF deployment is in.</td>
  +		</tr>
  +		<tr>
  +			<td><code>DNS</code></td>
  +			<td>Typically the DNS for your CF system domain unless you want to host the broker outside of CF.</td>
  +		</tr>
  +		<tr>
  +			<td><code>GATEWAY</code></td>
  +			<td>Typically the gateway address for your CF system domain unless you want to host the broker outside of CF.</td>
  +		</tr>
  +		<tr>
  +			<td><code>SUBNET-RANGE</code></td>
  +			<td>The CIDR range of the subnet in which to create the NFS Broker.</td>
  +		</tr>
  +		<tr>
  +			<td><code>RESERVED-IPs</code></td>
  +			<td>An Array of IP addresses that BOSH cannot use for the NFS Broker, such as <code>10.10.200.0 - 10.10.200.10</code></td>
  +		</tr>
  +		<tr>
  +			<td><code>STATIC-IPs</code></td>
  +			<td>Array of IP addresses that BOSH can use for the NFS Broker, such as <code>10.10.200.10 - 10.10.200.100</code></td>
  +		</tr>
  +	</table>
  +
  +#### Create the Credentials Stub
   
   Create a `creds.yml` file and paste in the following contents, replacing the indicated values with a username and password of your choosing:
   
   ```
  -    ---
  +---
   properties:
     nfsbroker:
  -    username: <BROKER_USERNAME>
  -    password: <BROKER_PASSWORD>
  +    username: BROKER_USERNAME
  +    password: BROKER_PASSWORD
   ```
   
  -#### Step 2: Create NFS Broker VM - Generate the Deployment Manifest
  -
  -1. Download the script from github using the `git cli`
  +#### Generate the Deployment Manifest
  +
  +1. Clone the NFS Volume Release repository:
   <pre class="terminal">
  -$ git clone https://github.com/cloudfoundry-incubator/nfs-volume-release.git
  +$ git clone http<span>s</span>://github.com/cloudfoundry-incubator/nfs-volume-release.git
   </pre>
   
  -Run the following script to generate a deployment manifest based on your stubs:
  -
  +1. Change directories into the repo you just cloned:
   <pre class="terminal">
  -$ ./scripts/generate\_manifest.sh cf.yml director-uuid.yml iaas.yml creds.yml
  +$ cd nfs-volume-release
   </pre>
   
  -###<a id="broker"></a>Step 4: Create NFS Broker VM - Deploy the Broker
  +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>
  +
  +###<a id="broker"></a>Step 4: Deploy the NFS 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
  +1. Register the broker using the credentials specified in the `creds.yml` stub:
   
   	<pre class="terminal">
  -	$ cf create-service-broker nfsbroker <BROKER_USERNAME> <BROKER_PASSWORD> http://nfs-broker.YOUR.DOMAIN.com
  +	$ cf create-service-broker nfsbroker BROKER_USERNAME BROKER_PASSWORD http://nfs-broker.YOUR-SYSTEM-DOMAIN
  +	</pre>
  +
  +1. Grant access to the service of the broker:
  +
  +	<pre class="terminal">
   	$ 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)
  +
  +	CF Developers can now create an NFS service and bind instances to their apps as outlined in [Using an External File System (Volume Services)](../volume-services-v2.10.html)
  
positive.code:      - name: nfsbroker
         networks:
         - name: public
           static_ips: [<--PUBLIC-BROKER-IP-->]
  
       networks:
       - name: nfsvolume-subnet
         subnets:
         - cloud_properties:
             security_groups:
             - <--SECURITY-GROUP-->
             subnet: <--SUBNET-->
           dns:
           - <--DNS-->
           gateway: <--GATEWAY-->
           range: <--SUBNET-RANGE-->
           reserved:
           - <--RESERVED-IPs-->
           static:
           - <--STATIC-IPs-->
  
       resource_pools:
         - name: medium
  
negative.code: 	---
  	```
  
  #### Create the IaaS Settings Stub
  
  <p class="note"><strong>Note</strong>: This is an AWS specific IaaS Settings Stub. If you want to deploy on another IaaS, use the templates available in the <code>templates</code> directory of each volume services release respository.</p>
  
  1. Create an `iaas.yml` stub to for IaaS-specific settings by copying the template below:
  
  	```
  	 ---
  