svn commit: r1023719 - in /websites/staging/directory/trunk/content: ./ api/dev-guide/1-introduction.html api/dev-guide/2-general-structure.html

[bu...@apache.org]

Author: buildbot
Date: Fri Jan 12 08:42:44 2018
New Revision: 1023719

Log:
Staging update by buildbot for directory

Modified:
    websites/staging/directory/trunk/content/   (props changed)
    websites/staging/directory/trunk/content/api/dev-guide/1-introduction.html
    websites/staging/directory/trunk/content/api/dev-guide/2-general-structure.html

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jan 12 08:42:44 2018
@@ -1 +1 @@
-1820955
+1820958

Modified: websites/staging/directory/trunk/content/api/dev-guide/1-introduction.html
==============================================================================
--- websites/staging/directory/trunk/content/api/dev-guide/1-introduction.html (original)
+++ websites/staging/directory/trunk/content/api/dev-guide/1-introduction.html Fri Jan 12 08:42:44 2018
@@ -184,7 +184,7 @@
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
 <h1 id="1-introduction">1 - Introduction<a class="headerlink" href="#1-introduction" title="Permanent link">&para;</a></h1>
-<p>This Developer Guide teaches developers about the inner logic of the API. It can be useful to those interested in the project, giving them some clues about how it all works and its design, and also to those who want to extend the API by adding Controls, Extended Operations, or schema elements like SyntaxCheckers, Comparators, etc.</p>
+<p>This Developer Guide teaches developers about the inner logic of the API. It can be useful to those interested in the project, giving them some clues about how it all works and its design, and also to those who want to extend the *<em>LDAP API</em> by adding <em>Controls</em>, <em>Extended Operations</em>, or schema elements like <em>SyntaxCheckers</em>, <em>Comparators</em>, etc.</p>
 <h2 id="content">Content<a class="headerlink" href="#content" title="Permanent link">&para;</a></h2>
 <ul>
 <li><a href="2-general-structure.html">2 - General structure</a></li>

Modified: websites/staging/directory/trunk/content/api/dev-guide/2-general-structure.html
==============================================================================
--- websites/staging/directory/trunk/content/api/dev-guide/2-general-structure.html (original)
+++ websites/staging/directory/trunk/content/api/dev-guide/2-general-structure.html Fri Jan 12 08:42:44 2018
@@ -184,7 +184,7 @@
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
 <h1 id="2-general-structure">2 - General Structure<a class="headerlink" href="#2-general-structure" title="Permanent link">&para;</a></h1>
-<p>The <em>LDAP API</em> is split into many modules. Here is their hierarchy :</p>
+<p>The <strong>Apache LDAP API</strong> is split into many modules. Here is their hierarchy :</p>
 <pre>
 LDAP API root
   |
@@ -255,31 +255,31 @@ LDAP API root
 
 <ul>
 <li>
-<p>The <em>all</em> module is just a packaging module, gathering all the other modules in one single jar to simplify the work o those who want to use the API. One can import each module speparately, or the <em>all</em> module only. Note that it does not include the tests and integration modules (<em>integ</em>, <em>integ-osgi</em> and <em>distribution</em>)</p>
+<p>The <em>all</em> module is just a packaging module, gathering all the other modules in one single jar to simplify the work o those who want to use the API. One can import each module speparately, or the <em>all</em> module only. Note that it does not include the tests and integration modules (<strong>integ</strong>, <strong>integ-osgi</strong> and <strong>distribution</strong>)</p>
 </li>
 <li>
-<p>The <em>asn1</em> module contains the code needed to handle <em>ASN/1</em> encoding/decoding.</p>
+<p>The <strong>asn1</strong> module contains the code needed to handle <em>ASN/1</em> encoding/decoding.</p>
 </li>
 <li>
-<p>The <em>distribution</em> module just create the packages</p>
+<p>The <strong>distribution</strong> module just create the packages</p>
 </li>
 <li>
-<p>The <em>dsml</em> module covers <em>DSML</em> features</p>
+<p>The <strong>dsml</strong> module covers <em>DSML</em> features</p>
 </li>
 <li>
-<p>The <em>i18n</em> module contains all the messages, in various languages (english, french and german at the moment)</p>
+<p>The <strong>i18n</strong> module contains all the messages, in various languages (english, french and german at the moment)</p>
 </li>
 <li>
-<p>The <em>integ</em> module is for integration tests, covering many of the existing modules</p>
+<p>The <strong>integ</strong> module is for integration tests, covering many of the existing modules</p>
 </li>
 <li>
-<p>The <em>integ-osgi</em> module covers tests related to <em>OSGi</em> integration. It checks that we can instanciate some component within an <em>OSGi</em> framework.</p>
+<p>The <strong>integ-osgi</strong> module covers tests related to <strong>OSGi</strong> integration. It checks that we can instanciate some component within an <strong>OSGi</strong> framework.</p>
 </li>
 <li>
-<p>The <em>ldap</em> modules are the meat of the <em>API</em> : they contain all the needed modules related to <em>LDAP</em>, and mainly the <em>model</em> module. Note that the <em>net</em> module should not be part of <em>ldap</em>, per se...</p>
+<p>The <strong>ldap</strong> modules are the meat of the <em>API</em> : they contain all the needed modules related to <em>LDAP</em>, and mainly the <em>model</em> module. Note that the <em>net</em> module should not be part of <strong>ldap</strong>, per se...</p>
 </li>
 <li>
-<p>The <em>util</em> module contains classes that are shared across the various modules.</p>
+<p>The <strong>util</strong> module contains classes that are shared across the various modules.</p>
 </li>
 </ul>
 <p>Anyway, from a developer point of view, that does not tell a lot about the inner struture.</p>