diff --git a/Design:-Version-Control.md b/Design:-Version-Control.md
index 4b5fc62..0dc38c3 100644
--- a/Design:-Version-Control.md
+++ b/Design:-Version-Control.md
@@ -7,6 +7,8 @@ When we talk about version control of node-red instances, there are two things t
 
 It is desirable to have a single artefact (or logical set of artefacts) that can be maintained in version control and used to restore a system to a previous known state.
 
+The priority is version control of flows/credentials - and is the main focus of this work. The *Added Nodes* scenarios are for a future piece of work.
+
 ### Added Nodes
 
 Currently, a user simply npm installs nodes in their user directory to add them to the runtime - or uses the admin api to do so. There is no requirement to maintain a `package.json` file. But it is that file that needs to be version controlled in order to have a restorable system.