diff --git a/VScript-:-Basic-I:O-Tutorial.md b/VScript-:-Basic-I:O-Tutorial.md
index 8ba4dea..135e2be 100644
--- a/VScript-:-Basic-I:O-Tutorial.md
+++ b/VScript-:-Basic-I:O-Tutorial.md
@@ -68,7 +68,7 @@ Now that we've written our code, it's time to access it from the map.
 
 Like outputs, an entity can run a VScript file and store its code until the entity is removed.
 
-Entities can run VScript files through a keyvalue (**Entity scripts**) or an input (`RunScriptFile`). Both of them take the filename of the script(s) to run. The extension is optional and you do not need to insert `scripts/vscripts`.
+Entities can run VScript files through a keyvalue (**Entity scripts**) or an input (`RunScriptFile`). Both of these take the filename of the script(s) to run. The extension is optional and you do not need to insert `scripts/vscripts`. For example, if you named your file `test_script.nut` and put the file is already in `scripts/vscripts`, then you will only need to use "test_script" to refer to it in Hammer.
 
 In Hammer, create an entity (e.g. a `logic_relay` or an `info_target`) and use either the keyvalue or the input to run your test file.