aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorRoman A <121314722+GameRoMan@users.noreply.github.com>2025-06-16 15:35:41 +0100
committerAleksandr Nogikh <nogikh@google.com>2025-06-16 15:22:49 +0000
commitb07d761310f45ec82aafa352739e190d12ab58a0 (patch)
treef8054476e057cc52de828af6ce343f5dda34526b /docs
parente7dd99bade45e7e0cf824f07484e8d34942edfa8 (diff)
all: fix typos
Diffstat (limited to 'docs')
-rw-r--r--docs/linux/external_fuzzing_usb.md2
-rw-r--r--docs/linux/setup.md4
2 files changed, 3 insertions, 3 deletions
diff --git a/docs/linux/external_fuzzing_usb.md b/docs/linux/external_fuzzing_usb.md
index a7a7a6a0f..088bed881 100644
--- a/docs/linux/external_fuzzing_usb.md
+++ b/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:
diff --git a/docs/linux/setup.md b/docs/linux/setup.md
index 1df36a4b2..0c9b4fe4c 100644
--- a/docs/linux/setup.md
+++ b/docs/linux/setup.md
@@ -67,7 +67,7 @@ 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.
@@ -75,7 +75,7 @@ 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: