svn commit: r1646846 - /jena/site/trunk/content/documentation/query/text-query.mdtext

[an...@apache.org]

Author: andy
Date: Fri Dec 19 19:33:12 2014
New Revision: 1646846

URL: http://svn.apache.org/r1646846
Log:
JENA-831: Fix bad text

Modified:
    jena/site/trunk/content/documentation/query/text-query.mdtext

Modified: jena/site/trunk/content/documentation/query/text-query.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/text-query.mdtext?rev=1646846&r1=1646845&r2=1646846&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/text-query.mdtext (original)
+++ jena/site/trunk/content/documentation/query/text-query.mdtext Fri Dec 19 19:33:12 2014
@@ -66,7 +66,7 @@ object and mapping to the subject.
 In this pattern, the data in the text index is indexing literals in the RDF data.  
 Additions to the RDF data are reflected in additions to the index.
 
-(Deletes do not remove text index entries - [see below](#deletion))
+(Deletes do not remove text index entries - [see below](#deletion-of-indexed-entities))
 
 ### Pattern B – External content
 
@@ -90,7 +90,7 @@ text index with SPARQL search.
 ## Query with SPARQL
 
 The property function is `http://jena.apache.org/text#query` more
-conveniently writtern:
+conveniently written:
 
     PREFIX text: <http://jena.apache.org/text#>
 
@@ -164,7 +164,7 @@ index, the name of the lucene/solr field
 itself.
 
 For common RDF use, there will be one field, mapping a property to a text
-index field. More complex setups, with multiple properties per enitity
+index field. More complex setups, with multiple properties per entity
 (URI) are possible.
 
 Once setup this way, any data added to the text dataset is automatically
@@ -264,10 +264,6 @@ Lucene index.  For example:
 will configure the index to analyze values of the 'text' field
 using a `StandardAnalyzer` with the given list of stop words.
 
-Other analyzer types that may be specified are `SimpleAnalyzer` and `KeywordAnalyzer`, 
-neither of which has any configuration parameters.  See the Lucene documentation
-for details of what these analyzers do.
-
 Other analyzer types that may be specified are `SimpleAnalyzer` and `KeywordAnalyzer`,
 neither of which has any configuration parameters. See the Lucene documentation
 for details of what these analyzers do.