all: fix typos

docs/linux/external_fuzzing_usb.md

@@ -2,7 +2,7 @@ External USB fuzzing for Linux kernel
 =====================================
 
 syzkaller supports fuzzing the Linux kernel USB subsystem from the external side.
-Instead of relying on external hardware (like [Facedancer](https://github.com/usb-tools/Facedancer)-based boards) or VM management software features (like QEMU [usbredir](https://www.spice-space.org/usbredir.html)), syzkaller fuzzes USB fully within a (potentially-virtualized) enviroment that runs the Linux kernel.
+Instead of relying on external hardware (like [Facedancer](https://github.com/usb-tools/Facedancer)-based boards) or VM management software features (like QEMU [usbredir](https://www.spice-space.org/usbredir.html)), syzkaller fuzzes USB fully within a (potentially-virtualized) environment that runs the Linux kernel.
 
 The USB fuzzing support in syzkaller is based on:
 

docs/linux/setup.md

@@ -67,15 +67,15 @@ Make sure that your GCC meets this requirement, or get a GCC that [syzbot](/docs
 Besides coverage support in GCC, you also need support for it on the kernel side.
 KCOV was added into mainline Linux kernel in version 4.6 and is be enabled by `CONFIG_KCOV=y` kernel configation option.
 For older kernels you need to at least backport commit [kernel: add kcov code coverage](https://github.com/torvalds/linux/commit/5c9a8750a6409c63a0f01d51a9024861022f6593).
-Besides that, it's recomended to backport all kernel patches that touch `kernel/kcov.c`.
+Besides that, it's recommended to backport all kernel patches that touch `kernel/kcov.c`.
 
 To enable more syzkaller features and improve bug detection abilities, it's recommended to use additional config options.
 See [this page](kernel_configs.md) for details.
 
 ### VM Setup
 
 Syzkaller performs kernel fuzzing on worker virtual machines or physical devices.
-These worker enviroments are referred to as VMs.
+These worker environments are referred to as VMs.
 Out-of-the-box syzkaller supports QEMU, kvmtool and GCE virtual machines, Android devices and Odroid C2 boards.
 
 These are the generic requirements for a syzkaller VM:

sys/linux/io_uring.txt

@@ -445,7 +445,7 @@ type io_uring_timeout_completion_event_count int64[0:10]
 # openat and openat2 returns a useful resource (fd) that we can use for other
 # systemcalls. The resulting fds are returned within io_uring_cqe.res. The only way
 # to identify cqes for those operations is to keep track of their user data. Thus,
-# use a seperate set of sqe_user_data range for openat and openat2.
+# use a separate set of sqe_user_data range for openat and openat2.
 sqe_user_data_not_openat = 0, 1
 sqe_user_data_openat = 0x12345, 0x23456
 sqe_user_data = 0, 1, 0x12345, 0x23456

tools/syz-headerparser/headerlib/container.py

@@ -46,7 +46,7 @@ def get_syzkaller_field_body(self):
         Returns the metadata description for a struct field in syzkaller format.
         eg: "len    intptr".
         In cases where more than one syzkaller type maps to a native type, return
-        a string with possible syzkaller types seperated by '|'.
+        a string with possible syzkaller types separated by '|'.
         '''
 
         def _get_syzkaller_type(native_type):