import quincy beta 17.1.0

[ceph.git] / ceph / doc / dev / cephx.rst

diff --git a/ceph/doc/dev/cephx.rst b/ceph/doc/dev/cephx.rst
index 27e501f99294f097a1fc793e70fb409e871a4832..e060f7ec88e4baded54b275eb51b7a25f29c5e67 100644 (file)
--- a/ceph/doc/dev/cephx.rst
+++ b/ceph/doc/dev/cephx.rst
@@ -10,7 +10,7 @@ Intro
 The protocol design looks a lot like kerberos.  The authorizer "KDC"
 role is served by the monitor, who has a database of shared secrets
 for each entity.  Clients and non-monitor daemons all start by
-authenticating with the monitor to obtain tickets, mostly referreed to
+authenticating with the monitor to obtain tickets, mostly referred to
 in the code as authorizers.  These tickets provide both
 *authentication* and *authorization* in that they include a
 description of the *capabilities* for the entity, a concise structured
@@ -402,5 +402,5 @@ That is, the new rotating key is simply protected by the daemon's
 rotating secret.
 
 Note that, as an implementation detail, the services keep the current
-key and the prior key on hand so that the can continue to validate
+key and the prior key on hand so that they can continue to validate
 requests while the key is being rotated.