doc: Fix some typos

Signed-off-by: mooncake <xcoder@tenxcloud.com>

diff --git a/doc/dev/osd_internals/erasure_coding/proposals.rst b/doc/dev/osd_internals/erasure_coding/proposals.rst
index 52f98e87d862bdd73089ca254ee50159139a1f68..a9c541d9df1f7a6671f029de27b7ce59f20103d6 100644 (file)
--- a/doc/dev/osd_internals/erasure_coding/proposals.rst
+++ b/doc/dev/osd_internals/erasure_coding/proposals.rst
@@ -77,7 +77,7 @@ object keys. Perhaps some modeling here can help resolve this
 issue. The data of the temporary object wants to be located as close
 to the data of the base object as possible. This may be best performed
 by adding a new ObjectStore creation primitive that takes the base
-object as an addtional parameter that is a hint to the allocator.
+object as an additional parameter that is a hint to the allocator.
 
 Sam: I think that the short lived thing may be a red herring.  We'll
 be updating the donor and primary objects atomically, so it seems like
@@ -263,7 +263,7 @@ on the prior_version which is not in the log.)  THe PGLog already has
 a way of handling those edge cases (see divergent_priors).  We'd
 simply expand that to contain the entire missing set and maintain it
 atomically with the log and the objects.  This isn't really an
-unreasonable option, the addiitonal keys would be fewer than the
+unreasonable option, the additional keys would be fewer than the
 existing log keys + divergent_priors and aren't updated in the fast
 write path anyway.
 

diff --git a/doc/dev/osd_internals/log_based_pg.rst b/doc/dev/osd_internals/log_based_pg.rst
index 4f4524f8d88e8a77db41647195c602d00a72d01a..51eb8278b3e5474c23583438743c1a85247cd098 100644 (file)
--- a/doc/dev/osd_internals/log_based_pg.rst
+++ b/doc/dev/osd_internals/log_based_pg.rst
@@ -27,7 +27,7 @@ writes on overlapping regions), we might as well serialize writes on
 the whole PG since it lets us represent the current state of the PG
 using two numbers: the epoch of the map on the primary in which the
 most recent write started (this is a bit stranger than it might seem
-since map distribution itself is asyncronous -- see Peering and the
+since map distribution itself is asynchronous -- see Peering and the
 concept of interval changes) and an increasing per-pg version number
 -- this is referred to in the code with type eversion_t and stored as
 pg_info_t::last_update.  Furthermore, we maintain a log of "recent"

diff --git a/doc/dev/osd_internals/osd_throttles.rst b/doc/dev/osd_internals/osd_throttles.rst
index 6739bd9ea5ae303c88585ed761498368556fa567..ee98d24850cb82142cd09b8852a9c7e003221b86 100644 (file)
--- a/doc/dev/osd_internals/osd_throttles.rst
+++ b/doc/dev/osd_internals/osd_throttles.rst
@@ -12,7 +12,7 @@ included in FileStore as FileStore::wbthrottle.  The intention is to
 bound the amount of outstanding IO we need to do to flush the journal.
 At the same time, we don't want to necessarily do it inline in case we
 might be able to combine several IOs on the same object close together
-in time.  Thus, in FileStore::_write, we queue the fd for asyncronous
+in time.  Thus, in FileStore::_write, we queue the fd for asynchronous
 flushing and block in FileStore::_do_op if we have exceeded any hard
 limits until the background flusher catches up.
 

diff --git a/doc/mgr/influx.rst b/doc/mgr/influx.rst
index c9a58a831f4add1c025e169183934dac80f90fb3..e759d5631ef865d4401f88ced29b8715febb73d5 100644 (file)
--- a/doc/mgr/influx.rst
+++ b/doc/mgr/influx.rst
@@ -60,7 +60,7 @@ Additional optional configuration settings are:
 Debugging 
 ---------
 
-By default, a few debugging statments as well as error statements have been set to print in the log files. Users can add more if necessary.
+By default, a few debugging statements as well as error statements have been set to print in the log files. Users can add more if necessary.
 To make use of the debugging option in the module:
 
 - Add this to the ceph.conf file.::