Fix some typo.

Documentation-develop/HTML.md

@@ -59,11 +59,12 @@ Use with LDAP: `typeAheadLdap`
  
 ### .data-typeahead-limit
 
-* Defines the limit of entries shown on the client. Default on client is 5. The server will always send a value. The server default is 20.
+* Defines the limit of entries shown on the client. Default on client is 5. The server will always send a value. 
+  The server default is 20.
 
 ### .data-typeahead-minlength
 
-* Defines the string minlegth, typed by the user, before the first lookup is started. Default is 2.
+* Defines the string minlength, typed by the user, before the first lookup is started. Default is 2.
  
 ### data-typeahead-pedantic
 
@@ -72,7 +73,8 @@ Use with LDAP: `typeAheadLdap`
 
 ## Tags Form Element
  
-The tags form element depends on Typeahead by default. The following attributes define the tags form element, additional to the attributes for Typeahead (see above).
+The tags form element depends on Typeahead by default. The following attributes define the tags form element, additional 
+to the attributes for Typeahead (see above).
 
 Mockups can be found in `mockup/typahead.php`
 

Documentation/Manual.rst

@@ -2146,7 +2146,7 @@ This situation also applies in *pedantic* mode to verify the user input after ea
 PerToken
 ^^^^^^^^
-Sometimes a LDAP server only provides attributes like 'sn' and 'givenName', but not 'displayName' or another practial
+Sometimes a LDAP server only provides attributes like 'sn' and 'givenName', but not 'displayName' or another practical
 combination of multiple attributes - than it is difficult to search for 'firstname' *and* (=human AND) 'lastname'.
 E.g. 'John Doe', results to search like `(|(sn=*John Doe*)(givenName=*John Doe*))` which will be probably always be empty.
 Instead, the user input has to be split in token and the search string has to repeated for every token.