diff --git a/lucene/CHANGES.txt b/lucene/CHANGES.txt index 377165a312c..d30c96d2fae 100644 --- a/lucene/CHANGES.txt +++ b/lucene/CHANGES.txt @@ -716,6 +716,11 @@ Bug fixes * LUCENE-3589: BytesRef copy(short) didnt set length. (Peter Chang via Robert Muir) +Documentation + +* LUCENE-3958: Javadocs corrections for IndexWriter. + (Iulius Curt via Robert Muir) + ======================= Lucene 3.6.0 ======================= Changes in backwards compatibility policy diff --git a/lucene/core/src/java/org/apache/lucene/index/IndexWriter.java b/lucene/core/src/java/org/apache/lucene/index/IndexWriter.java index e16ca0243bf..93a77887f99 100644 --- a/lucene/core/src/java/org/apache/lucene/index/IndexWriter.java +++ b/lucene/core/src/java/org/apache/lucene/index/IndexWriter.java @@ -1345,7 +1345,7 @@ public class IndexWriter implements Closeable, TwoPhaseCommit { final InfoStream infoStream; /** - * Forces merge policy to merge segments until there's <= + * Forces merge policy to merge segments until there are <= * maxNumSegments. The actual merges to be * executed are determined by the {@link MergePolicy}. * @@ -1371,14 +1371,14 @@ public class IndexWriter implements Closeable, TwoPhaseCommit { *

The actual temporary usage could be much less than * these figures (it depends on many factors).

* - *

In general, once the this completes, the total size of the + *

In general, once this completes, the total size of the * index will be less than the size of the starting index. * It could be quite a bit smaller (if there were many * pending deletes) or just slightly smaller.

* *

If an Exception is hit, for example - * due to disk full, the index will not be corrupt and no - * documents will have been lost. However, it may have + * due to disk full, the index will not be corrupted and no + * documents will be lost. However, it may have * been partially merged (some segments were merged but * not all), and it's possible that one of the segments in * the index will be in non-compound format even when