You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by sa...@apache.org on 2013/01/29 01:36:10 UTC
svn commit: r1439719 - in /lucene/dev/branches/branch_4x: ./ solr/
solr/site/ solr/site/html/tutorial.html
Author: sarowe
Date: Tue Jan 29 00:36:10 2013
New Revision: 1439719
URL: http://svn.apache.org/viewvc?rev=1439719&view=rev
Log:
fix typos in solr tutorial (merge trunk r1439718)
Modified:
lucene/dev/branches/branch_4x/ (props changed)
lucene/dev/branches/branch_4x/solr/ (props changed)
lucene/dev/branches/branch_4x/solr/site/ (props changed)
lucene/dev/branches/branch_4x/solr/site/html/tutorial.html
Modified: lucene/dev/branches/branch_4x/solr/site/html/tutorial.html
URL: http://svn.apache.org/viewvc/lucene/dev/branches/branch_4x/solr/site/html/tutorial.html?rev=1439719&r1=1439718&r2=1439719&view=diff
==============================================================================
--- lucene/dev/branches/branch_4x/solr/site/html/tutorial.html (original)
+++ lucene/dev/branches/branch_4x/solr/site/html/tutorial.html Tue Jan 29 00:36:10 2013
@@ -310,7 +310,7 @@ make many changes to an index in a batch
There is also an <span class="codefrag">optimize</span> command that does the
same things as <span class="codefrag">commit</span>, but also forces all index
segments to be merged into a single segment -- this can be very resource
-intsenive, but may be worthwhile for improving search speed if your index
+intensive, but may be worthwhile for improving search speed if your index
changes very infrequently.
</p>
<p>
@@ -411,7 +411,7 @@ and is useful when testing or debugging
<h2 class="boxed">Highlighting</h2>
<div class="section">
<p>
- Hit highlighting returns relevent snippets of each returned document, and highlights
+ Hit highlighting returns relevant snippets of each returned document, and highlights
terms from the query within those context snippets.
</p>
<p>
@@ -522,7 +522,7 @@ Try it out at
<p>
The <a href="http://wiki.apache.org/solr/SchemaXml">schema</a> defines
the fields in the index and what type of analysis is applied to them. The current schema your collection is using
- may be viewed directly via the <a href="http://localhost:8983/solr/#/collection1/schema">Schema tab</a> in the Admin UI, or explored dynamicly using the <a href="http://localhost:8983/solr/#/collection1/schema-browser">Schema Browser tab</a>.
+ may be viewed directly via the <a href="http://localhost:8983/solr/#/collection1/schema">Schema tab</a> in the Admin UI, or explored dynamically using the <a href="http://localhost:8983/solr/#/collection1/schema-browser">Schema Browser tab</a>.
</p>
<p>
The best analysis components (tokenization and filtering) for your textual
@@ -616,7 +616,7 @@ Mousing over the section label to the le
<p>
When both <a href="http://localhost:8983/solr/#/collection1/analysis?analysis.fieldvalue=Canon+Power-Shot+SD500&analysis.query=power+shot+sd-500&analysis.fieldtype=text_en_splitting&verbose_output=0">Index and Query</a>
values are provided, two tables will be displayed side by side showing the
-results of each chain. Terms in the Index chain results that are equivilent
+results of each chain. Terms in the Index chain results that are equivalent
to the final terms produced by the Query chain will be highlighted.
</p>
<p>