Update javadoc

src/main/java/com/avaje/ebean/dbmigration/package-info.java

@@ -0,0 +1,8 @@
+/**
+ * Generation DDL migration scripts based on changes to the model.
+ * <p>
+ * You can use <code>DbMigration</code> to compare the entity bean model to its prior state
+ * and generate DDL for the differences - adding tables, columns etc.
+ * </p>
+ */
+package com.avaje.ebean.dbmigration;

src/main/java/com/avaje/ebean/event/changelog/package-info.java

@@ -1,8 +1,13 @@
 /**
- * Generation DDL migration scripts based on changes to the model.
+ * Provides a built in change log mechanism and can audit changes.
  * <p>
- * You can use <code>DbMigration</code> to compare the entity bean model to its prior state
- * and generate DDL for the differences - adding tables, columns etc.
+ * Although you can build something similar using existing event adapters such as <code>BeanPersistController</code>
+ * this is built for purpose to reduce the effort and provide optimal performance for auditing or logging changes.
+ * </p>
+ * <p>
+ * By default you can annotate beans with <code>@ChangeLog</code> and associated change events are logged by default
+ * in a JSON form with appropriate auditing attributes such as who made the changes and ip address of the user etc
+ * via implementation of <code>ChangeLogPrepare</code>
  * </p>
  */
 package com.avaje.ebean.event.changelog;

src/main/java/com/avaje/ebean/event/readaudit/package-info.java

@@ -1,8 +1,8 @@
 /**
- * Generation DDL migration scripts based on changes to the model.
+ * Provides Auditing of read events including queries and L2 cache.
  * <p>
- * You can use <code>DbMigration</code> to compare the entity bean model to its prior state
- * and generate DDL for the differences - adding tables, columns etc.
+ * Provides a built support for supplied an audit of all the 'read events' for beans annotated
+ * with <code>@ReadAudit</code>
  * </p>
  */
 package com.avaje.ebean.event.readaudit;