[LTP] [PATCH] Typo and grammar corrections in the documentation

[Avinesh Kumar]

Signed-off-by: Avinesh Kumar <akumar@suse.de>
---
 README.md                       | 2 +-
 doc/c-test-tutorial-simple.txt  | 6 +++---
 doc/test-writing-guidelines.txt | 6 +++---
 3 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/README.md b/README.md
index 3a0fd7f96..b86b81942 100644
--- a/README.md
+++ b/README.md
@@ -206,4 +206,4 @@ Although we accept GitHub pull requests, the preferred way is sending patches to
 It's a good idea to test patches on GitHub Actions before posting to mailing
 list. Our GitHub Actions setup covers various architectures and distributions in
 order to make sure LTP compiles cleanly on most common configurations.
-For testing you need to just to push your changes to your own LTP fork on GitHub.
+For testing you need to just push your changes to your own LTP fork on GitHub.
diff --git a/doc/c-test-tutorial-simple.txt b/doc/c-test-tutorial-simple.txt
index 867c26532..06d2ca55d 100644
--- a/doc/c-test-tutorial-simple.txt
+++ b/doc/c-test-tutorial-simple.txt
@@ -228,12 +228,12 @@ the lines starting with a +++.
 --------------------------------------------------------------------------------
  statvfs01 statvfs01
  statvfs02 statvfs02
- 
+
 +statx01 statx01
 +
  stime01 stime01
  stime02 stime02
- 
+
 --------------------------------------------------------------------------------
 
 The +runtest+ files are in a two column format. The first column is the test
@@ -1053,7 +1053,7 @@ systems programming across multiple Kernel and C lib versions as well as
 different hardware architectures. The important thing to take away from this
 is that you have to be conscientious of what will happen on systems different
 from yours. The LTP has a huge and varied user base, so situations you may
-thing are unlikely can and do happen to somebody.
+think are unlikely can and do happen to somebody.
 
 Of course you don't want to spend time allowing for situations which may never
 arise either, so you have to do your research and think about each situation
diff --git a/doc/test-writing-guidelines.txt b/doc/test-writing-guidelines.txt
index 8ca014d45..552bbef63 100644
--- a/doc/test-writing-guidelines.txt
+++ b/doc/test-writing-guidelines.txt
@@ -150,7 +150,7 @@ When writing testcases in shell write in *portable shell* only, it's a good
 idea to try to run the test using alternative shell (alternative to bash, for
 example dash) too.
 
-*Portable shell* means Shell Command Language as defined by POSIX with a
+*Portable shell* means Shell Command Language as defined by POSIX with an
 exception of few widely used extensions, namely 'local' keyword used inside of
 functions and '-o' and '-a' test parameters (that are marked as obsolete in
 POSIX).
@@ -215,7 +215,7 @@ expression of kernel config variables that has to be satisfied in order for a
 test to run. This is mostly used for kernel namespaces at the moment.
 
 Sometimes it also makes sense to define a few macros instead of creating
-configure test. One example are Linux specific POSIX clock ids in
+configure test. One example is Linux specific POSIX clock ids in
 'include/lapi/posix_clocks.h'.
 
 3.1 Dealing with messed up legacy code
@@ -304,7 +304,7 @@ See 'testcases/commands/file/' for example.
 5.3 Subexecutables
 ^^^^^^^^^^^^^^^^^^
 
-If you test needs to execute a binary, place it in the same directory as the
+If your test needs to execute a binary, place it in the same directory as the
 testcase and name the file starting with '${test_binary_name}_'.  Once the
 test is executed by the framework, the path to the directory with all LTP
 binaries is added to the '$PATH' and you can execute it just by its name.
-- 
2.36.1