Clarify that part directives and headers can carry metadata.
R=rmacnak@google.com
Review URL: https://codereview.chromium.org//128613004
git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart@31622 260f80e4-7a28-3924-810f-c04153c831b5
diff --git a/docs/language/dartLangSpec.tex b/docs/language/dartLangSpec.tex
index a445ad9..18932fa 100644
--- a/docs/language/dartLangSpec.tex
+++ b/docs/language/dartLangSpec.tex
@@ -1946,7 +1946,7 @@
It is possible to associate metadata with constructs that may not be accessible via reflection, such as local variables (though it is conceivable that in the future, richer reflective libraries might provide access to these as well). This is not as useless as it might seem. As noted above, the data can be retrieved statically if source code is available.
}
-Metadata can appear before a library, class, typedef, type parameter, constructor, factory, function, field, parameter, or variable declaration and before an import or export directive.
+Metadata can appear before a library, part header, class, typedef, type parameter, constructor, factory, function, field, parameter, or variable declaration and before an import, export or part directive.
The constant expression given in an annotation is type checked and evaluated in the scope surrounding the declaration being annotated.
