fixed broken images

Signed-off-by: French Ben <frenchben@docker.com>

docker-for-aws/deploy.md

@@ -23,7 +23,7 @@ the swarm in your AWS console.  Once present on this page, you can see the
 "Public IP" of each manager node in the table and/or "Description" tab if you
 click on the instance.
 
-![](/img/managers.png)
+![](img/managers.png)
 
 ## Connecting via SSH
 

docker-for-aws/scaling.md

@@ -17,17 +17,17 @@ Login to the AWS console, and go to the EC2 dashboard. On the lower left hand si
 
 Look for the Auto Scaling group with the name that looks like $STACK_NAME-NodeASG-* Where `$STACK_NAME` is the name of the stack you created when filling out the CloudFormation template for Docker for AWS. Once you find it, click the checkbox, next to the name. Then Click on the "Edit" button on the lower detail pane.
 
-<img src="/img/autoscale_update.png">
+<img src="img/autoscale_update.png">
 
 Change the "Desired" field to the size of the worker pool that you would like, and hit "Save".
 
-<img src="/img/autoscale_save.png">
+<img src="img/autoscale_save.png">
 
 This will take a few minutes and add the new workers to your swarm automatically. To lower the number of workers back down, you just need to update "Desired" again, with the lower number, and it will shrink the worker pool until it reaches the new size.
 
 ### CloudFormation Update
 Go to the CloudFormation management page, and click the checkbox next to the stack you want to update. Then Click on the action button at the top, and select "Update Stack".
 
-<img src="/img/cloudformation_update.png">
+<img src="img/cloudformation_update.png">
 
 Pick "Use current template", and then click "Next". Fill out the same parameters you have specified before, but this time, change your worker count to the new count, click "Next". Answer the rest of the form questions. CloudFormation will show you a preview of the changes it will make. Review the changes and if they look good, click "Update". CloudFormation will change the worker pool size to the new value you specified. It will take a few minutes (longer for a larger increase / decrease of nodes), but when complete you will have your swarm with the new worker pool size.

docker-for-aws/upgrade.md

@@ -21,7 +21,7 @@ New releases are announced on [Release Notes](release-notes.md) page.
 
 To initiate an update, use either the AWS Console of the AWS cli to initiate a stack update. Use the S3 template URL for the new release and complete the update wizard. This will initiate a rolling upgrade of the Docker swarm, and service state will be maintained during and after the upgrade. Appropriately scaled services should not experience downtime during an upgrade.
 
-![Upgrade in AWS console](/img/cloudformation_update.png)
+![Upgrade in AWS console](img/cloudformation_update.png)
 
 Note that single containers started (for example) with `docker run -d` are **not** preserved during an upgrade. This is because the're not Docker Swarm objects, but are known only to the individual Docker engines.
 

docker-for-azure/deploy.md

@@ -18,13 +18,13 @@ node can be used for administrating the swarm.
 Once you've deployed Docker on Azure, go to the "Outputs" section of the
 resource group deployment.
 
-![](/img/sshtargets.png)
+![](img/sshtargets.png)
 
 The "SSH Targets" output is a URL to a blade that describes the IP address
 (common across all the manager nodes) and the SSH port (unique for each manager
 node) that you can use to log in to each manager node.
 
-![](/img/managers.png)
+![](img/managers.png)
 
 ## Connecting via SSH