git: 1b294500f3 - main - Status/2025Q3: spell

The branch main has been updated by maxim:

URL: https://cgit.FreeBSD.org/doc/commit/?id=1b294500f36891e1648cf6652130ddd8d91e4fb2

commit 1b294500f36891e1648cf6652130ddd8d91e4fb2
Author:     Maxim Konovalov <maxim@FreeBSD.org>
AuthorDate: 2025-10-19 19:27:30 +0000
Commit:     Maxim Konovalov <maxim@FreeBSD.org>
CommitDate: 2025-10-19 19:27:30 +0000

    Status/2025Q3: spell
---
 .../en/status/report-2025-07-2025-09/drm-drivers-slowdowns_fixes.adoc   | 2 +-
 website/content/en/status/report-2025-07-2025-09/group-changes.adoc     | 2 +-
 website/content/en/status/report-2025-07-2025-09/valgrind.adoc          | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/content/en/status/report-2025-07-2025-09/drm-drivers-slowdowns_fixes.adoc b/website/content/en/status/report-2025-07-2025-09/drm-drivers-slowdowns_fixes.adoc
index 42bc045d9e..5358c1de53 100644
--- a/website/content/en/status/report-2025-07-2025-09/drm-drivers-slowdowns_fixes.adoc
+++ b/website/content/en/status/report-2025-07-2025-09/drm-drivers-slowdowns_fixes.adoc
@@ -29,7 +29,7 @@ Unfortunately, `kvzalloc()`, which relied on `kmalloc()` in our implementation (
 
 Some rough profiling of slowdowns was done using `dtrace`.
 It revealed that a fair amount of execution time of the failing allocations came from attempting multiple allocation on the same NUMA domain, and that of succeeding ones came from useless changes to page attributes, triggering expensive TLB shootdowns.
-An analysis of the VM domainset iterators code revealed multiple flaws, in particular leading to re-examining the same domain multiple times (up to 4 times for the common case of machines with a single domain) without any additional guarantees of success for new attemps.
+An analysis of the VM domainset iterators code revealed multiple flaws, in particular leading to re-examining the same domain multiple times (up to 4 times for the common case of machines with a single domain) without any additional guarantees of success for new attempts.
 Some other VM domainset problems have been fixed in the process, such as ensuring that allocation requests prefer domains not on a low memory condition in all situations.
 
 Finally, concerning specifically the amdgpu driver and affecting only Carrizo, Polaris and Vega M based AMD GPUs, a temporary allocation that was unnecessarily physically contiguous was replaced with a regular one, making the remaining, relatively short but noticeable freezes disappear.
diff --git a/website/content/en/status/report-2025-07-2025-09/group-changes.adoc b/website/content/en/status/report-2025-07-2025-09/group-changes.adoc
index 2eba794c5e..8d41d0edbe 100644
--- a/website/content/en/status/report-2025-07-2025-09/group-changes.adoc
+++ b/website/content/en/status/report-2025-07-2025-09/group-changes.adoc
@@ -38,7 +38,7 @@ They are available if and only if the kernel was compiled with `COMPAT_FREEBSD14
 
 We have normally fixed all unwanted impacts of storing the effective group ID separately from the supplementary groups in the kernel, such as:
 
-* Some security policies or access checks would either ignore the effective group ID or the first supplementary group (with lowest numerical ID), affecting process visibility restrictions based on group IDs, the "can debug" and "can export KTLS keys" checks, the man:mac_do[4] and man:mac_bsdextended[4] security policies, and access crontrol to some hardware facilities (tracing: man:hwt[4]; performance monitoring: man:hwpmc[4]) and to NFS-served shares.
+* Some security policies or access checks would either ignore the effective group ID or the first supplementary group (with lowest numerical ID), affecting process visibility restrictions based on group IDs, the "can debug" and "can export KTLS keys" checks, the man:mac_do[4] and man:mac_bsdextended[4] security policies, and access control to some hardware facilities (tracing: man:hwt[4]; performance monitoring: man:hwpmc[4]) and to NFS-served shares.
 * Reporting of process' credentials would omit the effective group ID, affecting all variants of `procstat -s` (on live processes, core files, or system core dump), man:ddb[4].
 
 Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2025-07-2025-09/valgrind.adoc b/website/content/en/status/report-2025-07-2025-09/valgrind.adoc
index ea8fb619fc..9a8a2e1193 100644
--- a/website/content/en/status/report-2025-07-2025-09/valgrind.adoc
+++ b/website/content/en/status/report-2025-07-2025-09/valgrind.adoc
@@ -32,7 +32,7 @@ Here is a list of bugfixes since my last report, Q1 2024.
 * Improvements to `setcontest` argument checking
 * Some more `aio_*` fixes
 * Syscall `_sysctlname` was checking the wrong length of the name argument
-* New syscall wrappers for `kcmp`, `getrlimitusage`, `close_range`, `fchroot`, `setcred`, `exterrctl`, `inotify_add_watch_at`, `inotify_rm_awtch`, `jail_attach_jd` and `jail_remove_jd`
+* New syscall wrappers for `kcmp`, `getrlimitusage`, `close_range`, `fchroot`, `setcred`, `exterrctl`, `inotify_add_watch_at`, `inotify_rm_watch`, `jail_attach_jd` and `jail_remove_jd`
 * Started adding better `ioctl` argument checking
 * Fixes to Valgrinds self-checking modes
 * Support aarch64 auxv AT_HWCAP, AT_CHERI_STATS, AT_HWCAP3 and AT_HWCAP4