5 files changed, 11 insertions, 11 deletions
@@ -22,7 +22,7 @@ btrfs-progs-4.17.1 (2018-08-06)
* beautify progress output
* btrfstune: allow to continue uuid change after unclean interruption
* several fuzz fixes:
- * detect overalpping chunks
+ * detect overlapping chunks
* chunk loading error handling
* don't crash with unexpected root refs to extents
* relax option parsing again to allow mixing options and non-options
@@ -181,7 +181,7 @@ btrfs-progs-4.13 (2017-09-08)
* check: new option --force to allow check of a mounted filesystem (no repair)
* mkfs: --rootdir will now copy special files
* dump-tree: minor output changes
- * inspect rootid: accept file as arugment
+ * inspect rootid: accept file as argument
* dev usage: don't calculate slack space for missing devices
* fi du: don't print error on EMPTY_SUBVOL (inode number 2)
@@ -244,7 +244,7 @@ btrfs-progs-4.11 (2017-05-18)
* check: lowmem mode fix for false alert about lost backrefs
* convert: minor bugfix
- * library: fix build, misisng symbols, added tests
+ * library: fix build, missing symbols, added tests
* receive: handle subvolume in path clone
@@ -355,7 +355,7 @@ btrfs-progs-4.8.3 (2016-11-11)
* convert: also convert file attributes
- * convert: fix wrong tree block alignment for unalianged block group
+ * convert: fix wrong tree block alignment for unaligned block group
* check: quota verify fixes, handle reloc tree
* build: add stub for FIEMAP_EXTENT_SHARED, compiles on ancient kernels
* build: add stub for BUILD_ASSERT when ioctl.h is included
@@ -630,7 +630,7 @@ btrfs-progs-4.3 (2015-11-06)
* test for broken 'subvolume sync'
* basic tests for mkfs, raid option combinations
* basic tests for fuzzed images (check)
- * command intrumentation (eg valgrind)
+ * command instrumentation (eg valgrind)
* print commands if requested
* add README for tests
@@ -62,7 +62,7 @@ documented in the Makefile.
The build utilizes autotools, dependencies for generating the configure
-* autconf, autoheader
+* autoconf, autoheader
* automake, aclocal
@@ -85,7 +85,7 @@ Documentation updates
Documentation fixes or updates do not need much explanation so sticking to the
-code rules in the previous section is not necessary. Github pull requests are
+code rules in the previous section is not necessary. GitHub pull requests are
OK, patches could be sent to me directly and not required to be also in the
mailinglist. Pointing out typos via IRC also works, although might get
accidentally lost in the noise.
diff --git a/libbtrfsutil/README.md b/libbtrfsutil/README.md
index 1dc326de..8abb426d 100644
@@ -452,7 +452,7 @@ A few guidelines:
* Don't require the Btrfs UAPI headers for any interfaces (e.g., instead of
directly exposing a type from `linux/btrfs_tree.h`, abstract it away in a
type specific to `libbtrfsutil`)
-* Preserve API and ABI compatability at all times (i.e., we don't want to bump
+* Preserve API and ABI compatibility at all times (i.e., we don't want to bump
the library major version if we don't have to)
* Include Python bindings for all interfaces
* Write tests for all interfaces
diff --git a/tests/README.md b/tests/README.md
index d14d727c..94c5533d 100644
@@ -170,7 +170,7 @@ how to do mkfs, mount, unmount, check, loop device management etc.
and join by dashes `-`. This will become the directory name, eg. `012-subvolume-sync-must-wait`.
3. Write a short description of the bug and how it's tested to the comment at the
-begining of `test.sh`. You don't need to add the file to git yet. Don't forget
+beginning of `test.sh`. You don't need to add the file to git yet. Don't forget
to make the file executable, otherwise it's not going to be executed by the
@@ -194,7 +194,7 @@ $ TEST=012\* ./misc-tests.sh # from tests/
Most tests should be able to create the test images from scratch, using regular
commands and file operation. The commands also document the testcase and use
-the teste code and kernel of the environment.
+the test code and kernel of the environment.
In other cases, a pre-created image may be the right way if the above does not
work (eg. comparing output, requesting an exact layout or some intermediate
@@ -244,7 +244,7 @@ There are some utilities that are not distributed but are necessary for the
tests. They are in the top level directory of the testsuite and their path
cannot be set.
-The tests assume write acesss to their directories.
+The tests assume write access to their directories.
# Coding style, best practices