Update

Author: mattqual

src/as3/namespaces.md

@@ -7,12 +7,12 @@ ActionScript 3 uses three-dimensional property names: a property consists of a n
 You can use ActionScript namespaces to privatize definitions across class fields and access them from any package as long as the used namespace is in scope:
 
 ```
-// my_lib_internals.as
+// MyLibInternals.as
 package my.lib {
     /**
      * @private
      */
-    public namespace my_lib_internals = "http://my.lib/internals";
+    public namespace MyLibInternals = "http://my.lib/internals";
 }
 
 // Atom.as
@@ -23,7 +23,7 @@ package my.lib.atoms {
         /**
          * @private
          */
-        my_lib_internals var x:Number = 10;
+        MyLibInternals var x:Number = 10;
     }
 }
 
@@ -32,5 +32,5 @@ import my.lib.*;
 import my.lib.atoms.*;
 
 const atom = new Atom();
-trace(atom.my_lib_internals::x);
+trace(atom.MyLibInternals::x);
 ```

src/as3/packages.md

@@ -15,4 +15,17 @@ import me.diantha.*;
 // me.diantha.y
 y
 me.diantha.y
-```
+```
+
+## Source tree
+
+It is allowed to define how many items you wish in a source file. However, it is a good practice to keep the source tree the same as the package inheritance:
+
+```
+// <project>/src/me/someone/lib/SomeConst.as
+package me.someone.lib {
+    public const SomeConst:decimal = 10;
+}
+```
+
+This source tree can be used to insert MXML files at the right package.