build-system-guide.txt/c-test-api.txt/c-test-tutorial-simple.txt/c-te…

…st-tutorial-simple.txt: fix typo Signed-off-by: Yang Xu <[email protected]> Reviewed-by: Li Wang <[email protected]>
linux-test-project · Aug 16, 2023 · 004cb10 · 004cb10
1 parent c3fa9f8
commit 004cb10
Show file tree

Hide file tree

Showing 4 changed files with 6 additions and 6 deletions.
diff --git a/doc/build-system-guide.txt b/doc/build-system-guide.txt
@@ -106,7 +106,7 @@ The 'REQ_VERSION_MAJOR' and 'REQ_VERSION_PATCH' describe minimal kernel
 version for which the build system tries to build the module.
 
 The buildsystem is also forward compatible with changes in Linux kernel
-internal API so that if modul fails to build the failure is ignored both on
+internal API so that if module fails to build the failure is ignored both on
 build and installation. If the userspace counterpart of the test fails to load
 the module because the file does not exists, the test is skipped.
 

diff --git a/doc/c-test-api.txt b/doc/c-test-api.txt
@@ -20,7 +20,7 @@ Let's start with an example, following code is a simple test for a 'getenv()'.
  * [Description]
  * Tests basic functionality of getenv().
  *
- *  - create an env variable and verify that getenv() can get get it
+ *  - create an env variable and verify that getenv() can get it
  *  - call getenv() with nonexisting variable name, check that it returns NULL
  */
 
@@ -579,7 +579,7 @@ These two functions are intended for runtime kernel version detection. They
 parse the output from 'uname()' and compare it to the passed values.
 
 The return value is similar to the 'strcmp()' function, i.e. zero means equal,
-negative value means that the kernel is older than than the expected value and
+negative value means that the kernel is older than the expected value and
 positive means that it's newer.
 
 The second function 'tst_kvercmp2()' allows for specifying per-vendor table of
@@ -1949,7 +1949,7 @@ available to the children (see the capabilities (7) manual pages).
 
 However a lot of problems can be solved by using 'tst_cap_action(struct
 tst_cap  *cap)' directly which can be called at any time. This also helps if
-you wish to drop a capability at the begining of setup.
+you wish to drop a capability at the beginning of setup.
 
 1.33 Reproducing race-conditions
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

diff --git a/doc/c-test-tutorial-simple.txt b/doc/c-test-tutorial-simple.txt
@@ -940,7 +940,7 @@ the 'index' where you are then able to un-stage some parts before
 re-committing.
 
 You can also use +edit+ and +git commit --amend+ together to change a commit
-deep in your history, but without reseting the 'index'. The 'index' contains
+deep in your history, but without resetting the 'index'. The 'index' contains
 changes which you have staged with +git add+, but not yet committed.
 
 So now that the commit history has been cleaned up, we need to submit a patch

diff --git a/doc/supported-kernel-libc-versions.txt b/doc/supported-kernel-libc-versions.txt
@@ -62,7 +62,7 @@ Minimal supported kernel version is 3.10.
 [align="center",options="header"]
 |==================================
 | Libc      | Note
-| https://www.gnu.org/software/libc/[GNU C Library (glibc)] | Targetted libc, tested both compilation and actual test results.
+| https://www.gnu.org/software/libc/[GNU C Library (glibc)] | Targeted libc, tested both compilation and actual test results.
 | https://uclibc-ng.org/[uClibc-ng] | Although not being tested it should work as well as it attempt to maintain a glibc compatible interface.
 | https://www.uclibc.org/[uClibc]   | Older https://www.uclibc.org/[uClibc] might have problems.
 | https://musl.libc.org/[musl] | Not yet fully supported (see