From: Abhishek Lekshmanan Date: Wed, 9 Jul 2014 05:28:59 +0000 (+0530) Subject: doc: fix a few typos in rbd docs X-Git-Tag: v0.84~132^2~4 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=e23ed9b7dc1dd91fa3658cd51188ac0095a76efa;p=ceph.git doc: fix a few typos in rbd docs Signed-off-by: Abhishek Lekshmanan --- diff --git a/doc/rbd/rbd-config-ref.rst b/doc/rbd/rbd-config-ref.rst index f57477d1fce8..4cc0545ac3fc 100644 --- a/doc/rbd/rbd-config-ref.rst +++ b/doc/rbd/rbd-config-ref.rst @@ -38,7 +38,7 @@ mode, set ``rbd cache max dirty`` to 0. This means writes return only when the data is on disk on all replicas, but reads may come from the cache. The cache is in memory on the client, and each RBD image has its own. Since the cache is local to the client, there's no coherency -if there are others accesing the image. Running GFS or OCFS on top of +if there are others accessing the image. Running GFS or OCFS on top of RBD will not work with caching enabled. The ``ceph.conf`` file settings for RBD should be set in the ``[client]`` diff --git a/doc/rbd/rbd-snapshot.rst b/doc/rbd/rbd-snapshot.rst index 9fb5f8010820..bde9f8547ec1 100644 --- a/doc/rbd/rbd-snapshot.rst +++ b/doc/rbd/rbd-snapshot.rst @@ -220,7 +220,7 @@ clone snapshots from one pool to images in another pool. #. **Template Pool:** One way to use block device layering is to create a pool that contains master images that act as templates, and snapshots of those - templates. You may then extend read-only priveleges to users so that they + templates. You may then extend read-only privileges to users so that they may clone the snapshots without the ability to write or execute within the pool. #. **Image Migration/Recovery:** One way to use block device layering is to migrate @@ -229,7 +229,7 @@ clone snapshots from one pool to images in another pool. Protecting a Snapshot --------------------- -Clones access the parent snapshots. All clones would break if a user inadvertantly +Clones access the parent snapshots. All clones would break if a user inadvertently deleted the parent snapshot. To prevent data loss, you **MUST** protect the snapshot before you can clone it. ::