diff --git a/Design:-external-file-for-function-and-templates-nodes.md b/Design:-external-file-for-function-and-templates-nodes.md
index 080e24d..cbba9a2 100644
--- a/Design:-external-file-for-function-and-templates-nodes.md
+++ b/Design:-external-file-for-function-and-templates-nodes.md
@@ -7,7 +7,9 @@ Doing diffs and merging flow files with a large number of functions or templates
 We know some third party nodes do this but we think this should be integrated in the code.  The main downside of using third party nodes is they need to be kept up to date with the core to reflect changes in the function or template nodes which is not always the case.  Having this in the core would ensure that everything it up to date.
 
 ## Proposition
-We propose the addition of a checkbox named `Load from external file` just above the code field.  Checking this checkbox would make a field appear where the user can type the path to a file, similar to the `file-in` node.  Given the fact some cloud environment are not compatible with a traditional file system, a setting named `allowExternalFiles` could be added in `settings.js` to disable this feature entirely. 
+We propose the addition of a checkbox named `Load from external file` just above the code field.  Checking this checkbox would make a field appear where the user can type the path to a file, similar to the `file-in` node.  Given the fact some cloud environment are not compatible with a traditional file system, a setting named `allowExternalFiles` could be added in `settings.js` to disable this feature entirely.
+
+In that mode, the code editor could show the code but in greyed out mode, similar to how the Arduino IDE works when using external files.
 
 ## Exporting flows
 This brings one problem, what happens when someone exports a flow ?  We propose the addition of a checkbox in the flow export dialog named `Embed external files` that would embed the external file contents within the exported flow making sharing of that flow possible.