diff --git a/forge.go b/forge.go
index c5a3ab1..5e4d284 100644
--- a/forge.go
+++ b/forge.go
@@ -79,24 +79,6 @@
 //      statement is defined. Includes are in the format 'include "<pattern>";'. The <pattern> can be any glob
 //      like pattern which is compatible with `path.filepath.Match` http://golang.org/pkg/path/filepath/#Match
 //
-// Note about references.
-//
-// References are resolved during parsing not access (they do not act as pointers... today).
-// Meaning that if I have the following config:
-//   setting = "value";
-//   ref_to_setting = setting;
-//
-// During parsing when I get to `ref_to_setting` it will be resolved immediately and it's value will
-// be set to `"value"`.
-//
-// This config example, however, will raise a parsing error since it cannot resolve the reference:
-//   ref_to_setting = setting;
-//   setting = "value";
-//
-// Since `setting` does not exist yet.
-// This is mostly due to the naive implementation of references today. How they work may change in
-// future versions or they may disappear entirely.
-//
 package forge
 
 import (