diff --git a/opensource/code.md b/opensource/code.md
index 82ccb574f3..90b72174a6 100644
--- a/opensource/code.md
+++ b/opensource/code.md
@@ -28,36 +28,36 @@ If you are an experienced open source contributor you may be familiar with this
 workflow. If you are new or just need reminders, the steps below link to more
 detailed documentation in Docker's project contributors guide.
 
-1. <a href="http://docs.docker.com/project/software-required/"
+1. <a href="http://docs.docker.com/opensource/project/software-required/"
 target="_blank">Get the software</a> you need.
 
 	This explains how to install a couple of tools used in our development
 	environment.  What you need (or don't need) might surprise you.
 
-2. <a href="http://docs.docker.com/project/set-up-git/"
+2. <a href="http://docs.docker.com/opensource/project/set-up-git/"
 target="_blank">Configure Git and fork the repo</a>.
 
 	Your Git configuration can make it easier for you to contribute.
 	Configuration is especially key if are new to contributing or to Docker.
 
-3. <a href="http://docs.docker.com/project/set-up-dev-env/"
+3. <a href="http://docs.docker.com/opensource/project/set-up-dev-env/"
 target="_blank">Learn to work with the Docker development container</a>.
 
 	Docker developers run `docker` in `docker`.  If you are a geek,
 	this is a pretty cool experience.
-4. <a href="http://docs.docker.com/project/find-an-issue/"
+4. <a href="http://docs.docker.com/opensource/workflow/find-an-issue/"
 target="_blank">Claim an issue</a> to work on.
 
 	We created a filter listing <a href="http://goo.gl/Hsp2mk" target="_blank">all open
 	and unclaimed issues</a> for Docker.
 
 5. <a
-href="http://docs.docker.com/project/work-issue/" target="_blank">Work on the
+href="http://docs.docker.com/opensource/workflow/work-issue/" target="_blank">Work on the
 issue</a>.
 
 	If you change or add code or docs to a project, you should test your changes
 	as you work. This page explains <a
-	href="http://docs.docker.com/project/test-and-docs/" target="_blank">how to
+	href="http://docs.docker.com/opensource/project/test-and-docs/" target="_blank">how to
 	test in our development environment</a>.
 
 	Also, remember to always **sign your commits** as you work! To sign your
@@ -68,7 +68,7 @@ issue</a>.
 	If you don't sign <a href="https://twitter.com/gordontheturtle"
 	target="_blank">Gordon</a> will get you!
 
-6. <a href="http://docs.docker.com/project/create-pr/" target="_blank">Create a
+6. <a href="http://docs.docker.com/opensource/workflow/create-pr/" target="_blank">Create a
 pull request</a>.
 
 	If you make a change to fix an issue, add reference to the issue in the pull
@@ -81,6 +81,6 @@ pull request</a>.
 	needs](code.md#what-is-the-pre-pull-request-checklist).
 
 
-7. <a href="http://docs.docker.com/project/review-pr/"
+7. <a href="http://docs.docker.com/opensource/workflow/review-pr/"
 target="_blank">Participate in the pull request review</a> till a successful
 merge.