Validateable trait has moved

src/en/guide/testing/unitTesting/unitTestingDomains.gdoc

@@ -167,7 +167,7 @@ These are all easily testable in a unit test with no special configuration neces
 // src/groovy/com/demo/MyValidateable.groovy
 package com.demo
 
-class MyValidateable implements grails.validation.trait.Validateable {
+class MyValidateable implements grails.validation.Validateable {
     String name
     Integer age
 

src/en/guide/theWebLayer/controllers/commandObjects.gdoc

@@ -9,7 +9,7 @@ h4. Declaring Command Objects
 Command object classes are defined just like any other class.
 
 {code:java}
-class LoginCommand implements grails.validation.trait.Validateable {
+class LoginCommand implements grails.validation.Validateable {
     String username
     String password
 
@@ -25,7 +25,7 @@ In this example, the command object class implements the @Validateable@ trait. T
 By default, all @Validateable@ object properties are @nullable: false@ which matches the behavior of GORM domain objects. If you want a @Validateable@ that has @nullable: true@ properties by default, you can specify this by defining a @defaultNullable@ method in the class:
 
 {code:java}
-class AuthorSearchCommand implements grails.validation.trait.Validateable {
+class AuthorSearchCommand implements grails.validation.Validateable {
     String  name
     Integer age
 
@@ -133,7 +133,7 @@ h4. Command Objects and Dependency Injection
 Command objects can participate in dependency injection. This is useful if your command object has some custom validation logic which uses a Grails [service|guide:services]:
 
 {code}
-class LoginCommand implements grails.validation.trait.Validateable {
+class LoginCommand implements grails.validation.Validateable {
 
     def loginService