[05/17] isis-site git commit: ISIS-1465: tiny doc fix

[da...@apache.org]

http://git-wip-us.apache.org/repos/asf/isis-site/blob/a1b07ded/content/guides/ugfun/ugfun.html
----------------------------------------------------------------------
diff --git a/content/guides/ugfun/ugfun.html b/content/guides/ugfun/ugfun.html
index d05d0a6..b6e8bbd 100644
--- a/content/guides/ugfun/ugfun.html
+++ b/content/guides/ugfun/ugfun.html
@@ -2114,18 +2114,11 @@ table.CodeRay td.code>pre{padding:0}
          <div class="paragraph"> 
           <p>The bootstrapping of Apache Isis also relies on module classes. (Currently) the only role of these classes is to identify a fully qualified package name, for example <code>org.incode.modules.document</code>. The framework then performs classpath scanning across all such packages to locate any domain entities provided by that module (though some modules have no entities), all domain services provided by the module (every module is likely to define at least one), and also any fixture scripts provided by the module.</p> 
          </div> 
-         <div class="admonitionblock tip"> 
-          <table> 
-           <tbody>
-            <tr> 
-             <td class="icon"> <i class="fa icon-tip" title="Tip"></i> </td> 
-             <td class="content"> 
-              <div class="paragraph"> 
-               <p>In the same way that the Java module act as a namespace for domain objects, it’s good practice to map domain entities to their own (database) schemas.</p> 
-              </div> </td> 
-            </tr> 
-           </tbody>
-          </table> 
+         <div class="paragraph"> 
+          <p>In the same way that the Java module act as a namespace for domain objects, it’s good practice to map domain entities to their own (database) schemas.</p> 
+         </div> 
+         <div class="paragraph"> 
+          <p>In previous versions a module class did not need to implement any specific interface; all the framework used was the package of the provided class. As of <code>1.16.0-SNAPSHOT</code> however, the <a href="../rgcms/rgcms.html#_rgcms_classes_Module"><code>Module</code></a> interface allows a module to specify its direct dependencies; from these all transitive dependencies are calculated. This should match the compile-time dependencies declared within Maven. The <code>Module</code> interface also allows a module to declare any configuration properties that should be contributed, as well as fixture scripts for reference data, and to tear down (for integration testing).</p> 
          </div> 
         </div> 
        </div>