common: correct some typos and spelling errors

examples/logfile/README

@@ -29,6 +29,6 @@ example, follow these steps:
 	$ printlog /pmem/logfile
 
 4. The printlog command will throw away the current log file contents
-   aftert printing it if given the -t argument:
+   after printing it if given the -t argument:
 
    	$ printlog -t /pmem/logfile

src/test/README

@@ -56,7 +56,7 @@ file system type, and build type to test.
 
 RUNTESTS takes options to limit what it runs.  The usage is:
 
- RUNTEST [ -nv ] [ -b build-type ] [ -t test-type ] [ -f fs-type ] [test...]
+ RUNTESTS [ -nv ] [ -b build-type ] [ -t test-type ] [ -f fs-type ] [test...]
 
  Build types are: debug, nondebug, static-debug, static-nondebug, all (default)
  Test types are: check (default), short, long
@@ -117,7 +117,7 @@ unit test framework also looks for several other variables:
 DETAILS ON HOW TO WRITE UNIT TESTS
 
 A minimal unit test consists of a sub-directory here with an executable called
-TEST0 in it that exits normally when the test passes.  Mosts tests, however,
+TEST0 in it that exits normally when the test passes.  Most tests, however,
 source the file unittest/unittest.sh to use the utility functions for setting
 up and checking tests.  Additionally, most unit tests build a local test
 program and call it from the TEST* scripts.

src/test/blk_recovery/README

@@ -15,7 +15,7 @@ For example:
 
 this will call pmemblk_pool_open() on file1, call pmemblk_write() for LBA 5
 (causing all the layout to be written), then it will change the memory
-protection on the arean map area to read-only.  Next, pmemblk_write()
+protection on the map area to read-only.  Next, pmemblk_write()
 is called for for LBA 10 and SIGSEGV is caught and reported.  Finally,
 pmemblk_pool_check() is called.
 

src/test/blk_rw_mt/README

@@ -6,7 +6,7 @@ This directory contains a unit test for MT reads & writes.
 
 The program in blk_rw_mt.c takes a block size, a file, a random number
 generator seed (to make the results repeatable), a thread count, and the
-numer of I/Os to do per thread.  For example:
+number of I/Os to do per thread.  For example:
 
 	./blk_rw_mt 4096 file1 123 300 500
 

src/test/log_basic/README

@@ -14,8 +14,8 @@ This directory contains a unit test for:
 - pmemlog_pool_check
 
 
-The program in pmemlog.c takes a filename and a list of
-operations encoded as characters as arugments. For example:
+The program in pmemlog.c takes a file name and a list of
+operations encoded as characters as arguments. For example:
 
 	./log_basic file1 a v r w t n
 

src/test/log_recovery/README

@@ -5,7 +5,7 @@ This is src/test/log_recovery/README.
 This directory contains a unit test for pmemlog recovery. It works only
 in non-debug mode.
 
-The program in log_recovery.c takes a filename and an operation as arugments.
+The program in log_recovery.c takes a file name and an operation as arguments.
 An operation is encoded as a character 'a' or 'v'. The first one means that
 pmemlog_append() will be used to append data and the second one means that
 pmemlog_appendv() will be used to do that. For example:

src/test/log_walker/README

@@ -5,7 +5,7 @@ This is src/test/log_walker/README.
 This directory contains a unit test to verify pool's write-protection
 in debug mode. It works only in debug mode.
 
-The program in log_walker.c takes only a filename as an arugment. For example:
+The program in log_walker.c takes only a file name as an argument. For example:
 
 	./log_walker file1