[Solr Wiki] Trivial Update of "FAQ" by noodl

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.

The following page has been changed by noodl:
http://wiki.apache.org/solr/FAQ

The comment on the change is:
Various typos

------------------------------------------------------------------------------
  
  Solr is a stand alone enterprise search server which applications communicate with using XML and HTTP to index documents, or execute searches.  Solr supports a rich schema specification that allows for a wide range of flexibility in dealing with different document fields, and has an extensive search plugin API for developing custom search behavior.
  
- For more information pleae read this [http://lucene.apache.org/solr/features.html overview of Solr features].
+ For more information please read this [http://lucene.apache.org/solr/features.html overview of Solr features].
  
  == Are there Mailing lists for Solr? ==
  
@@ -131, +131 @@

  
  == Why don't International Characters Work? ==
  
- Solr can index any characters expressed in the UTF-8 charset (see [http://issues.apache.org/jira/browse/SOLR-96 SOLR-96]). There are no known bugs with Solr's character handling, but there have been some reported issues with the way different application servers (and different versions of the same application server) treat incoming and outgoing multibyte characters.  In particular, people have reported better success with Tomcat then with Jetty...
+ Solr can index any characters expressed in the UTF-8 charset (see [http://issues.apache.org/jira/browse/SOLR-96 SOLR-96]). There are no known bugs with Solr's character handling, but there have been some reported issues with the way different application servers (and different versions of the same application server) treat incoming and outgoing multibyte characters.  In particular, people have reported better success with Tomcat than with Jetty...
  
   * "[http://www.nabble.com/International-Charsets-in-embedded-XML-tf1780147.html#a4897795 International Charsets in embedded XML]" (Jetty 5.1)
   * "[http://www.nabble.com/Problem-with-surrogate-characters-in-utf-8-tf3920744.html Problem with surrogate characters in utf-8]" (Jetty 6)
@@ -139, +139 @@

  If you notice a problem with multibyte characters, the first step to ensure that it is not a true Solr bug would be to write a unit test that bypasses the application server directly using the [http://lucene.apache.org/solr/api/org/apache/solr/util/AbstractSolrTestCase.html AbstractSolrTestCase].
  
  The most important points are:
-  * The document has to be indexed as UTF-8 encoded on the solr server. For example, if you send a ISO encoded document, then the special ISO characters get a byte added (screwing up the final encoding, only reindexing with UTF-8 can fix this).
+  * The document has to be indexed as UTF-8 encoded on the solr server. For example, if you send an ISO encoded document, then the special ISO characters get a byte added (screwing up the final encoding, only reindexing with UTF-8 can fix this).
   * The client needs UTF-8 URL encoding when forwarding the search request to the solr server. 
  
  If you just forward doing:
@@ -166, +166 @@

  
  == Solr started, and i can POST documents to it, but the admin screen doesn't work ==
  
- The admin screens are implemented using JSPs which require a JDK (instead of just a JRE) to be compiled on the fly.  If you encounter errors trying to load the admin pages, and the stack traces of these errors seem to relate to compilation of JSPs, make sure you have a JDK installed, and make sure the it is the instance of java being used.
+ The admin screens are implemented using JSPs which require a JDK (instead of just a JRE) to be compiled on the fly.  If you encounter errors trying to load the admin pages, and the stack traces of these errors seem to relate to compilation of JSPs, make sure you have a JDK installed, and make sure it is the instance of java being used.
  
  NOTE: Some Servlet Containers (like Tomcat5.5 and Jetty6) don't require a JDK for JSPs.
  
@@ -206, +206 @@

  
  == Why Isn't Sorting Working on my Text Fields? ==
  
- Lucene Sorting requires that the field you want to sort on be indexed, but it cannot contain more then one "token" per document.  Most Analyzers used on Text fields result in more then one token, so the simplest thing to do is to use copyField to index a second version of your field using the !StrField class.
+ Lucene Sorting requires that the field you want to sort on be indexed, but it cannot contain more than one "token" per document.  Most Analyzers used on Text fields result in more than one token, so the simplest thing to do is to use copyField to index a second version of your field using the !StrField class.
  
  If you need to do some processing on the field value using !TokenFilters, you can also use the !KeywordTokenizer, see the Solr example schema for more information.