diff --git a/sections/docker/bootstrap-using-node.md b/sections/docker/bootstrap-using-node.md
index aaf4f0b1..7be2aa90 100644
--- a/sections/docker/bootstrap-using-node.md
+++ b/sections/docker/bootstrap-using-node.md
@@ -2,9 +2,9 @@
 
 ## One paragraph explainer
 
-We are used to see code examples where folks start their app using `CMD 'npm start'`. This is a bad practice. The `npm` binary will not forward signals to your app which prevents graceful shutdown (see [/sections/docker/graceful-shutdown.md]). If you are using child-processes they won’t be cleaned up correctly in case of unexpected shutdown, leaving zombie processes on your host. `npm start` also results in having an extra process for no benefit. To start you app use `CMD ['node','server.js']`. If your app spawns child-processes also use `TINI` as an entrypoint.
+We are used to see code examples where folks start their app using `CMD 'npm start'`. This is a bad practice. The `npm` binary will not forward signals to your app which prevents graceful shutdown [see](/sections/docker/graceful-shutdown.md). If you are using child-processes they won’t be cleaned up correctly in case of unexpected shutdown, leaving zombie processes on your host. `npm start` also results in having an extra process for no benefit. To start you app use `CMD ['node','server.js']`. If your app spawns child-processes also use `TINI` as an entrypoint.
 
-### Code example - Bootsraping using Node
+### Code example - Bootstrapping using Node
 
 ```dockerfile
 FROM node:12-slim AS build