As suggested by Otis: Convert TABs to spaces, remove @author javadoc tags

git-svn-id: https://svn.apache.org/repos/asf/lucene/java/trunk@733443 13f79535-47bb-0310-9956-ffa450edef68

contrib/queries/src/java/org/apache/lucene/search/trie/TrieRangeFilter.java

@@ -33,7 +33,6 @@ import org.apache.lucene.util.OpenBitSet;
  * This filter depends on a specific structure of terms in the index that can only be created
  * by {@link TrieUtils} methods.
  * For more information, how the algorithm works, see the package description {@link org.apache.lucene.search.trie}.
- * @author Uwe Schindler (panFMP developer)
  */
 public final class TrieRangeFilter extends Filter {
 

contrib/queries/src/java/org/apache/lucene/search/trie/TrieRangeQuery.java

@@ -31,7 +31,6 @@ import org.apache.lucene.index.IndexReader;
  * by {@link TrieUtils} methods.
  * <p>This class wraps a {@link TrieRangeFilter} using a {@link ConstantScoreQuery}.
  * @see TrieRangeFilter
- * @author Uwe Schindler (panFMP developer)
  */
 public final class TrieRangeQuery extends Query {
 

contrib/queries/src/java/org/apache/lucene/search/trie/TrieUtils.java

@@ -47,7 +47,7 @@ import org.apache.lucene.search.ExtendedFieldCache;
  * By this it is possible to get the correct enumeration of terms in correct precision
  * of the term list by just jumping to the correct fieldname and/or prefix. The full precision value may also be
  * stored in the document. Having the full precision value as term in a separate field with the original name,
- * sorting of query results agains such fields is possible using the original field name.
+ * sorting of query results against such fields is possible using the original field name.
  */
 public final class TrieUtils {