btrfs-progs: docs: fix typos in READMEs, INSTALL and CHANGES

Generated by https://github.com/jsoref/spelling

Issue: #154
Author: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: David Sterba <dsterba@suse.com>

1 files changed, 3 insertions, 3 deletions

diff --git a/tests/README.md b/tests/README.md
index d14d727c..94c5533d 100644
--- a/tests/README.md
+++ b/tests/README.md
@@ -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
 infrastructure.
 
@@ -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