diff --git a/Design:-Runnable-Project.md b/Design:-Runnable-Project.md
index ec88d45..a97251d 100644
--- a/Design:-Runnable-Project.md
+++ b/Design:-Runnable-Project.md
@@ -23,6 +23,8 @@ We can't quite do this today. Here are the missing pieces:
 
 The package would provide an npm start script that runs node-red with the appropriate command-line args.
 
+> DCJ: If you run the steps above then node-red and other modules will be installed *below* the CWD in node_modules... all good.  If however we want to take our project dir and npm pack it... on re-installing it the project itself will also be in the node_modules dir thus making npm start (or pathing back to node-red) trickier.
+
 ### Runtime settings
 
 When deploying the project, there will also be a need to have the runtime settings provided. These are not normally part of a project generated by Node-RED. The question is whether we have some tooling support to generate, or we just document how to do it. For example, the user would manually add a `settings.js` file to their project repo.
@@ -60,7 +62,8 @@ ENV NODE_PATH=/usr/src/app/node_modules
 
 EXPOSE 1880
 
-CMD ["npm", "start"]```
+CMD ["npm", "start"] 
+```
 
 A really minimal Dockerfile to build an image (but not run) could be as simple as