From b6ecfc22a54bb113b0a3cc4823b7b28f6c49084c Mon Sep 17 00:00:00 2001
From: Hiroki Uchikawa <31908137+HirokiUchikawa@users.noreply.github.com>
Date: Tue, 20 Mar 2018 00:18:48 +0900
Subject: [PATCH] Updated Design: Persistable Context (markdown)

---
 Design:-Persistable-Context.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/Design:-Persistable-Context.md b/Design:-Persistable-Context.md
index 511c9e5..ca51a77 100644
--- a/Design:-Persistable-Context.md
+++ b/Design:-Persistable-Context.md
@@ -66,7 +66,7 @@ contextStorage : {
         }
     }
     // you can use `file` as the `default`.
-    // get default(){ return this.file }
+    // defalut: "file"
 }
 ```
 
@@ -86,7 +86,8 @@ The value set in the config is passed to the plugin. These items are defined by
     default: "redis",
 
 > So that you can swap default easily ?
->> NOL: Either/or - default could be an alias for another config, or a full options object.
+>> NOL: Either/or - default could be an alias for another config, or a full options object.  
+>> HU: You're right. it is easily and simple. I changed above settings.js.
 
 > DCJ: Do we need to think about passwords in the clear in these settings ? Is the whole of settings object available to other nodes ?
 >> NOL: The settings file contents is not accessible to the whole runtime - only the bits we choose to expose. How the user provides values to the file is up to them, such as env-var etc.