doc: Fix Spelling Error in Developer Guide

Signed-off-by: Li Bingyang <li.bingyang1@zte.com.cn>

diff --git a/doc/dev/blkin.rst b/doc/dev/blkin.rst
index 597124836057b4374240fed6dadbbbc670d0047b..0f61ed473bee6198a05fe3534e850e6cdbba29fe 100644 (file)
--- a/doc/dev/blkin.rst
+++ b/doc/dev/blkin.rst
@@ -64,8 +64,8 @@ Testing Blkin
 
 It's easy to test Ceph's Blkin tracing. Let's assume you don't have
 Ceph already running, and you compiled Ceph with Blkin support but
-you did't install it. Then launch Ceph with the ``vstart.sh`` script
-in Ceph's src directgory so you can see the possible tracepoints.::
+you didn't install it. Then launch Ceph with the ``vstart.sh`` script
+in Ceph's src directory so you can see the possible tracepoints.::
 
   cd src
   OSD=3 MON=3 RGW=1 ./vstart.sh -n

diff --git a/doc/dev/cephfs-snapshots.rst b/doc/dev/cephfs-snapshots.rst
index 367f3e8db002c45a563f18d661469638d66c26df..f1d0083535329c2f6575894be35305d20bd3083a 100644 (file)
--- a/doc/dev/cephfs-snapshots.rst
+++ b/doc/dev/cephfs-snapshots.rst
@@ -118,7 +118,7 @@ out again.
 
 Hard links
 ----------
-Inode with multiple hard links is moved to a dummy gloabl SnapRealm. The
+Inode with multiple hard links is moved to a dummy global SnapRealm. The
 dummy SnapRealm covers all snapshots in the filesystem. The inode's data
 will be preserved for any new snapshot. These preserved data will cover
 snapshots on any linkage of the inode.

diff --git a/doc/dev/development-workflow.rst b/doc/dev/development-workflow.rst
index b2baea178db2d121200aa33d0a17a60265699440..31184663461e6bbcb2afeefdf0d18770f529b044 100644 (file)
--- a/doc/dev/development-workflow.rst
+++ b/doc/dev/development-workflow.rst
@@ -31,7 +31,7 @@ results.
 The workflows are not enforced when they impose an overhead that does
 not make sense. For instance, if the release notes for a point release
 were not written prior to checking all integration tests, they can be
-commited to the stable branch and the result sent for publication
+committed to the stable branch and the result sent for publication
 without going through another run of integration tests.
 
 Release Cycle