--- a/REFERENCE.md Fri Oct 13 12:20:50 2017 -0500
+++ b/REFERENCE.md Fri Oct 13 17:53:15 2017 -0500
@@ -52,7 +52,7 @@
## environment-from-file.yml
-This example shows how to inject variables into the environment from a file in the build container.+This example shows how to inject variables into the environment from a file in the workspace. @@ -181,7 +181,7 @@
An environment task will read a file with environment variables and make them accessible to your plans.
A file is expected to have lines of the form `variable=value`. Empty lines are ignored. Files are read
-from the docker volume, so files generated by the plan do not need to be exported in order to be a target+from the workspace, so files generated by the plan do not need to be exported in order to be a target of an environment task. From the other direction, it is necessary to import files on the host if they are
to be read by an environment task.
@@ -193,10 +193,10 @@
| from-files | | | A list of files that should be read. |
| prefix | | | A prefix to add to each variable read from a file |
-At least one file must be supplied by either the `from-file` or `fromfiles` attributes. If both are supplied,+At least one file must be supplied by either the `from-file` or `from-files` attributes. If both are supplied, `from-file` is inserted to the front of `from-files`. If the files being read are a result of environment variable
expansion, the order that the files are read are not guaranteed to be stable (or in the order supplied). Be cautious
-of this if the environment files have define overlapping variables.+of this if the environment files define overlapping variables. 