svn commit: r888414 - in /websites/staging/directory/trunk/content: ./ apacheds/kerberos-ug/4.2-authenticate-studio.html

[bu...@apache.org]

Author: buildbot
Date: Thu Nov 28 18:02:59 2013
New Revision: 888414

Log:
Staging update by buildbot for directory

Modified:
    websites/staging/directory/trunk/content/   (props changed)
    websites/staging/directory/trunk/content/apacheds/kerberos-ug/4.2-authenticate-studio.html

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Nov 28 18:02:59 2013
@@ -1 +1 @@
-1546418
+1546419

Modified: websites/staging/directory/trunk/content/apacheds/kerberos-ug/4.2-authenticate-studio.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/kerberos-ug/4.2-authenticate-studio.html (original)
+++ websites/staging/directory/trunk/content/apacheds/kerberos-ug/4.2-authenticate-studio.html Thu Nov 28 18:02:59 2013
@@ -146,7 +146,7 @@
 <h1 id="41-authenticate-with-studio">4.1 - Authenticate with Studio</h1>
 <p>We will explain how to use the kerberos server to authentify users on a LDAP server. Let's first define the way we will store data in the LDAP server</p>
 <DIV class="info" markdown="1">
-We will suppose that the <strong>Kerberos</strong> server is installed on a server which <em>hostName</em> is <strong>example.net</strong> and the <em>realm/em> is <strong>EXAMPLE.COM</strong> in the following paragraphes.
+We will suppose that the <strong>Kerberos</strong> server is installed on a server which <em>hostName</em> is <strong>example.net</strong> and the <em>realm</em> is <strong>EXAMPLE.COM</strong> in the following paragraphes.
 </DIV>
 
 <h2 id="servers-configuration">Servers configuration</h2>