Links to new features

src/en/guide/introduction/whatsNew/coreFeatures.gdoc

@@ -14,10 +14,16 @@ h4. Gradle Build System
 
 Grails 3.0 deprecates the older Gant-based build system in favour of a new [Gradle-based|http://gradle.org] build that integrates closely with the [Gradle plugin ecosystem|http://plugins.gradle.org].
 
+See the new section on the new [Gradle build|guide:gradleBuild] for more information.
+
 h4. Application Profiles
 
 Grails 3.0 supports the notion of application profiles via a new [profile repository|https://github.com/grails/grails-profile-repository]. A profile encapsulates an application structure, set of commands, plugins and capabilities. For example the "web" profile allows construction on web applications deployable to a Servlet container. In the future more profiles will be developed targeting different environments.
 
+See the new section on [Profiles|guide:profiles] for more information.
+
 h4. Redesigned API based on Traits
 
 The Grails API has been redesigned so that public API is correctly populated under the @grails.@ package whilst private / internal API that is subject to change can be found in the @org.grails.@ package. The core API has also been rewritten and based around the [Groovy Traits|http://groovy-lang.org/objectorientation.html#_traits].
+
+See the new documentation on Grails 3.0's [core traits|guide:traits] for more information.

src/en/guide/introduction/whatsNew/developmentEnvironmentFeatures.gdoc

@@ -4,10 +4,12 @@ Replacing Gant, Grails 3.0 features a new interactive command line shell that in
 
 The new shell integrates closely with the concept of application profiles with each profile capable defining [profile specific commands|https://github.com/grails/grails-profile-repository/tree/master/profiles/web/commands]. As with previous versions of Grails, plugins can define new shell commands that can invoke Gradle or perform code generation and project automation tasks.
 
+See the new guide on [Creating Custom Scripts|guide:creatingCustomScripts] for more information.
+
 h4. Enhanced IDE Integration
 
 Since Grails 3.0 is built on Gradle, you can now import a Grails project using IntelliJ community edition or GGTS's Gradle tooling support without the need for Grails specific tooling. Grails 3.0 plugins are published as simple JAR files greatly reducing the need for additional IDE support specific to Grails.
 
 h4. Application Main Class
 
-Each new Grails 3.0 project features an @Application@ class that has a traditional @static void main@ signature, meaning to run or debug a Grails 3.0 application from an IDE like IntelliJ or GGTS you can simply right-click on the @Application@ class and execute to start your Grails application. All Grails 3.0 tests can also just be run from the IDE directly without needing to resort to the command line (even integration / functional tests!). 
+Each new Grails 3.0 project features an @Application@ class that has a traditional @static void main@ signature, meaning to run or debug a Grails 3.0 application from an IDE like IntelliJ or GGTS you can simply right-click on the @Application@ class and execute to start your Grails application. All Grails 3.0 tests can also just be run from the IDE directly without needing to resort to the command line (even integration / functional tests!).