Update Angular profile docs to include changes to naming conventions …

…and ability to change asset folder with config

src/en/guide/webServices/REST/angularProfile.gdoc

@@ -34,27 +34,37 @@ Example:
 $ grails create-ng-controller foo
 {code}
 
-This will produce a fooController.js file in @grails-app/assets/javascripts/${default package name}/controllers@.
+This will produce a @fooController.js@ file in @grails-app/assets/javascripts/${default package name}/controllers@.
+
+{note}
+By default the angular profile will create files in the @javascripts@ directory. You can change that behavior in your configuration with the key @grails.codegen.angular.assetDir@.
+{note}
 
 {code}
 $ grails create-ng-domain foo.bar
 {code}
 
-This will produce a Bar.js file in @grails-app/assets/javascripts/foo/domains@. It will also create the "foo" module if it does not already exist.
+This will produce a @Bar.js@ file in @grails-app/assets/javascripts/foo/domains@. It will also create the "foo" module if it does not already exist.
+
+{code}
+$ grails create-ng-module foo.bar
+{code}
+
+This will produce a @foo.bar.js@ file in @grails-app/assets/javascripts/foo/bar@. Note the naming convention for modules is different than other artefacts.
 
 {code}
 $ grails create-ng-service foo.bar --type constant
 {code}
 
-This will produce a bar.js file in @grails-app/assets/javascripts/foo/services@. It will also create the "foo" module if it does not already exist. The @create-ng-service@ command accepts a flag @-type@. The types that can be used are:
+This will produce a @bar.js@ file in @grails-app/assets/javascripts/foo/services@. It will also create the "foo" module if it does not already exist. The @create-ng-service@ command accepts a flag @-type@. The types that can be used are:
 
 * service
 * factory _default_
 * value
 * provider
 * constant
 
-Along with the artefacts themselves, the profile will also produce a skeleton unit test file under @src/test/assets@ for each create command
+Along with the artefacts themselves, the profile will also produce a skeleton unit test file under @src/test/javascripts@ for each create command
 
 h4. Client side dependencies