You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@directory.apache.org by el...@apache.org on 2017/01/01 18:13:08 UTC

svn commit: r1776866 - /directory/site/trunk/content/api/user-guide/2.4-adding.mdtext

Author: elecharny
Date: Sun Jan  1 18:13:08 2017
New Revision: 1776866

URL: http://svn.apache.org/viewvc?rev=1776866&view=rev
Log:
Fixed bold format

Modified:
    directory/site/trunk/content/api/user-guide/2.4-adding.mdtext

Modified: directory/site/trunk/content/api/user-guide/2.4-adding.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/api/user-guide/2.4-adding.mdtext?rev=1776866&r1=1776865&r2=1776866&view=diff
==============================================================================
--- directory/site/trunk/content/api/user-guide/2.4-adding.mdtext (original)
+++ directory/site/trunk/content/api/user-guide/2.4-adding.mdtext Sun Jan  1 18:13:08 2017
@@ -162,9 +162,9 @@ Another reason an entry can be rejected
 ## Errors
 
 <DIV class="note" markdown="1">
-At first, you might expect to get an exception if the entry addition has failed. If the server is rejecting the addition, *you will get NO exception*. Exceptions are only thrown client side if the entry is not built correctly, or if the connection is not opened. 
+At first, you might expect to get an exception if the entry addition has failed. If the server is rejecting the addition, <b>you will get NO exception*</b>. Exceptions are only thrown client side if the entry is not built correctly, or if the connection is not opened. 
 
-In any other case, the server will simply return a **[LdapResult]()** instance containing either **SUCCESS** or the cause of the rejection.
+In any other case, the server will simply return a <b>[LdapResult]()</b> instance containing either <b>SUCCESS</b> or the cause of the rejection.
 </DIV>
 
 Usually, if you get an error while adding an entry, the message is hard to read. Most of the errors occur because the entry already exists, or because the entry has an LDAP schema violation.