svn commit: r913723 - in /websites/staging/gora/trunk/content: ./ current/tutorial.html

[bu...@apache.org]

Author: buildbot
Date: Wed Jun 25 14:31:10 2014
New Revision: 913723

Log:
Staging update by buildbot for gora

Modified:
    websites/staging/gora/trunk/content/   (props changed)
    websites/staging/gora/trunk/content/current/tutorial.html

Propchange: websites/staging/gora/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jun 25 14:31:10 2014
@@ -1 +1 @@
-1604971
+1605422

Modified: websites/staging/gora/trunk/content/current/tutorial.html
==============================================================================
--- websites/staging/gora/trunk/content/current/tutorial.html (original)
+++ websites/staging/gora/trunk/content/current/tutorial.html Wed Jun 25 14:31:10 2014
@@ -436,7 +436,7 @@ For this tutorial we will be using the f
 </pre></div>
 
 
-<p>Every mapping file starts with the top level element <code><gora-orm></code>. 
+<p>Every mapping file starts with the top level element <code>&lt;gora-otd&gt;</code>. 
 Gora HBase mapping files can have two type of child elements, table and 
 class declarations. All of the table and class definitions should be 
 listed at this level.</p>
@@ -460,7 +460,7 @@ as the column qualifier. Note that map a
 families, so the configuration should be list unique column families for each map and 
 array type, and no qualifier should be given. The exact data model is discussed further 
 at the <a href="/current/gora-hbase.html">gora-hbase</a> documentation. </p>
-<h2 id="basic-api-wzxhzdk78">Basic API </title></h2>
+<h2 id="basic-api-wzxhzdk79">Basic API </title></h2>
 <h3 id="parsing-the-logs">Parsing the logs</h3>
 <p>Now that we have the basic setup, we can see Gora API in action. As you can notice below the API 
 is pretty simple to use. We will be using the class LogManager (which is located at