summaryrefslogtreecommitdiff
path: root/Documentation/admin-guide
diff options
context:
space:
mode:
authorJonathan Corbet <corbet@lwn.net>2026-06-12 13:41:41 -0600
committerJonathan Corbet <corbet@lwn.net>2026-06-12 13:41:41 -0600
commit9347fe187d93c647fa93a708ce990241ee8f3c6e (patch)
treef41cbe901fc4b26511debc5a340cbe8c5184e153 /Documentation/admin-guide
parent738bb6e6c8d992f33335b3cbcce051ab118a33dc (diff)
parentfa34b01aa0f59355206b0807f862cced06c2b7a1 (diff)
downloadlwn-docs-next.tar.gz
lwn-docs-next.zip
Merge branch 'docs-mw' into docs-nextdocs-next
Diffstat (limited to 'Documentation/admin-guide')
-rw-r--r--Documentation/admin-guide/bug-hunting.rst4
-rw-r--r--Documentation/admin-guide/quickly-build-trimmed-linux.rst2
2 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/admin-guide/bug-hunting.rst b/Documentation/admin-guide/bug-hunting.rst
index 3901b43c96df..642bf8474726 100644
--- a/Documentation/admin-guide/bug-hunting.rst
+++ b/Documentation/admin-guide/bug-hunting.rst
@@ -63,8 +63,8 @@ Documentation/admin-guide/tainted-kernels.rst, "being loaded" is
annotated with "+", and "being unloaded" is annotated with "-".
-Where is the Oops message is located?
--------------------------------------
+Where is the Oops message located?
+----------------------------------
Normally the Oops text is read from the kernel buffers by klogd and
handed to ``syslogd`` which writes it to a syslog file, typically
diff --git a/Documentation/admin-guide/quickly-build-trimmed-linux.rst b/Documentation/admin-guide/quickly-build-trimmed-linux.rst
index cb178e0a6208..3432dc8e1a85 100644
--- a/Documentation/admin-guide/quickly-build-trimmed-linux.rst
+++ b/Documentation/admin-guide/quickly-build-trimmed-linux.rst
@@ -217,7 +217,7 @@ again.
There is a catch: 'localmodconfig' is likely to disable kernel features you
did not use since you booted your Linux -- like drivers for currently
- disconnected peripherals or a virtualization software not haven't used yet.
+ disconnected peripherals or virtualization software not currently in use.
You can reduce or nearly eliminate that risk with tricks the reference
section outlines; but when building a kernel just for quick testing purposes
it is often negligible if such features are missing. But you should keep that