diff --git a/reports/2017-03-19.md b/reports/2017-03-19.md
index b3957e13e..8d69a5d4b 100644
--- a/reports/2017-03-19.md
+++ b/reports/2017-03-19.md
@@ -37,17 +37,17 @@ Welcome everyone, looking forward to your contrinutions and working with you. Pl
 
 ## This week
 
-We are working towards a simpler and better documented basic flow. Early next week the `moby` tool will be changed to have `moby build` and `moby run` subcommands. At least initially the `moby run` flow will only be targeted at running locally (hyperkit and kvm, qemu). We may add a third cluster run option later, using infrakit. @rneugeba has been working on Go hyperkit bindings to make this easier in #1327.
+We are working towards a simpler and better documented basic flow. Early next week the `moby` tool will be changed to have `moby build` and `moby run` subcommands. At least initially the `moby run` flow will only be targeted at running locally (hyperkit and kvm, qemu). We may add a third cluster run option later, using infrakit. @rneugeba has been working on Go hyperkit bindings to make this easier in [#1327](https://github.com/docker/moby/pull/1327).
 
-There is a `--name` option to the `moby` tool to allow configuring of the image names that are built see #1318 rather than just using the yaml file name.
+There is a `--name` option to the `moby` tool to allow configuring of the image names that are built see [#1318](https://github.com/docker/moby/pull/1318) rather than just using the yaml file name.
 
-The end to end flow for Google Cloud has been much improved by @justincormack as a model for other providers, see #1323. There is a metadata container that reads the platform metadata, and passes ssh keys to the generic `sshd` container. This makes the workflow much simpler: build moby with a `gcp` target, use `gcloud compute instances create` to run an instance, then `ssh` in to it, see https://github.com/docker/moby/blob/master/docs/gcp.md for details. We will expand this to other providers, in particular porting the metadata providers for other Docker Edition platforms.
+The end to end flow for Google Cloud has been much improved by @justincormack as a model for other providers, see [#1323](https://github.com/docker/moby/pull/1323). There is a metadata container that reads the platform metadata, and passes ssh keys to the generic `sshd` container. This makes the workflow much simpler: build moby with a `gcp` target, use `gcloud compute instances create` to run an instance, then `ssh` in to it, see https://github.com/docker/moby/blob/master/docs/gcp.md for details. We will expand this to other providers, in particular porting the metadata providers for other Docker Edition platforms.
 
-As mentioned above @avsm has worked on initial support for the packet.net instances, both the smaller Intel Atom Xeon machines, and the larger machines with dual 10GbE. #1309 #1325
+As mentioned above @avsm has worked on initial support for the packet.net instances, both the smaller Intel Atom Xeon machines, and the larger machines with dual 10GbE. [#1309](https://github.com/docker/moby/pull/1309) [#1325](https://github.com/docker/moby/pull/1325)
 
-The kernel container build has been improved, with human readable names eg `mobylinux/kernel:4.9.x` and will soon be built again in CI #1295. We upgraded the standard kernel to 4.9.15 #1305. We will add 4.10.x builds shortly.
+The kernel container build has been improved, with human readable names eg `mobylinux/kernel:4.9.x` and will soon be built again in CI [#1295](https://github.com/docker/moby/pull/1295). We upgraded the standard kernel to 4.9.15 [#1305](https://github.com/docker/moby/pull/1305). We will add 4.10.x builds shortly.
 
-@riyazdf has done some more work on making Moby run with a read only rootfs #1298 as well as more containers run read only #1290 #1301. There is also work on splitting out DHCP into a seperate service container so that it can be removed if other networking configuration is being used or if other clients are used #1316.
+@riyazdf has done some more work on making Moby run with a read only rootfs [#1298](https://github.com/docker/moby/pull/1298) as well as more containers run read only [#1290](https://github.com/docker/moby/pull/1290) [#1301](https://github.com/docker/moby/pull/1301). There is also work on splitting out DHCP into a seperate service container so that it can be removed if other networking configuration is being used or if other clients are used [#1316](https://github.com/docker/moby/pull/1316).
 
 ## Next week priorities