From 443e04e62dd09578759876c560d2a4a1f8bfaad5 Mon Sep 17 00:00:00 2001 From: Pascal Borreli Date: Sat, 16 Nov 2013 11:21:34 +0000 Subject: [PATCH] Fixed typos --- db/db_impl.cc | 2 +- doc/index.html | 4 ++-- tools/db_crashtest2.py | 2 +- tools/ldb_test.py | 2 +- tools/shell/ShellState.h | 4 ++-- util/build_version.h | 2 +- utilities/merge_operators/string_append/stringappend_test.cc | 2 +- utilities/merge_operators/uint64add.cc | 2 +- utilities/redis/redis_lists_test.cc | 4 ++-- utilities/ttl/ttl_test.cc | 2 +- 10 files changed, 13 insertions(+), 13 deletions(-) diff --git a/db/db_impl.cc b/db/db_impl.cc index 6ce7a7439..1241f7743 100644 --- a/db/db_impl.cc +++ b/db/db_impl.cc @@ -2423,7 +2423,7 @@ Status DBImpl::DoCompactionWork(CompactionState* compact, int num_output_files = compact->outputs.size(); if (compact->builder != nullptr) { - // An error occured so ignore the last output. + // An error occurred so ignore the last output. assert(num_output_files > 0); --num_output_files; } diff --git a/doc/index.html b/doc/index.html index 088a73722..8c0c9de5a 100644 --- a/doc/index.html +++ b/doc/index.html @@ -407,7 +407,7 @@ when 1 write buffer is being flushed to storage, new writes can continue to the other write buffer. Options::min_write_buffer_number_to_merge is the minimum number of write buffers that will be merged together before writing to storage. -If set to 1, then all write buffers are fushed to L0 as individual files and +If set to 1, then all write buffers are flushed to L0 as individual files and this increases read amplification because a get request has to check in all of these files. Also, an in-memory merge may result in writing lesser data to storage if there are duplicate records in each of these @@ -661,7 +661,7 @@ that hold all the different options for that compaction. The exact definition is Here we give short overview of options in CompactionOptionsUniversal: