diff --git a/Design:-Version-Control.md b/Design:-Version-Control.md
index 2906361..367882f 100644
--- a/Design:-Version-Control.md
+++ b/Design:-Version-Control.md
@@ -138,7 +138,7 @@ Quick mock-up:
 By default, the `localfilesystem` implementation should be entirely file based.
 
  - the base flow/credential files remain unchanged to how they work today
- - a new directory structure is created alongside the flow file:
+ - a new directory structure is created alongside the flow files in the <userDir>:
 
         my-flows.json
         my-flows_cred.json
@@ -165,7 +165,7 @@ need to be exposed.
    that allows it to be maintained externally (eg GitHub).
 
    - User provides **flow file name**, eg `my-flows.json` - as they can today
-   - Node-RED uses a repository under `<userHome>/my-flows` - creating it if needed
+   - Node-RED uses a repository under `<userDir>/my-flows` - creating it if needed
    - Node-RED stores `my-flows.json` and `my-flows_cred.json` under that directory
 
 2. a user wants to maintain a repo that contains more then just the flow files.
@@ -174,7 +174,7 @@ need to be exposed.
      relative path within the repo.
    - If it is a local repo, Node-RED uses that repo directly. A user could configure
      a post-commit hook to handle pushing updates remotely.
-   - Otherwise, Node-RED clones that repo under `<userHome>/.flows` and uses that,
+   - Otherwise, Node-RED clones that repo under `<userDir>/.flows` and uses that,
      ensuring to do `git push` back to the origin
    - The user should be able to provide authentication settings for the git repo
      via settings - or by well-defined environment variables.