From: 李丙洋 10208981 Date: Thu, 13 Sep 2018 01:17:34 +0000 (+0800) Subject: doc: Fix Spelling Error in Developer Guide X-Git-Tag: v14.0.1~302^2 X-Git-Url: http://git.apps.os.sepia.ceph.com/?a=commitdiff_plain;h=da96cc919c15361b4fff3956470fe51bde20a523;p=ceph.git doc: Fix Spelling Error in Developer Guide Signed-off-by: Li Bingyang --- diff --git a/doc/dev/blkin.rst b/doc/dev/blkin.rst index 597124836057b..0f61ed473bee6 100644 --- 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 367f3e8db002c..f1d0083535329 100644 --- 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 b2baea178db2d..31184663461e6 100644 --- 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