git: 9d9bb4578c - main - Status/2026Q1/valgrind: spell

The branch main has been updated by maxim:

URL: https://cgit.FreeBSD.org/doc/commit/?id=9d9bb4578c1b5152d99a9477ed0ed4dfc8f7a0e7

commit 9d9bb4578c1b5152d99a9477ed0ed4dfc8f7a0e7
Author:     Maxim Konovalov <maxim@FreeBSD.org>
AuthorDate: 2026-04-16 17:41:48 +0000
Commit:     Maxim Konovalov <maxim@FreeBSD.org>
CommitDate: 2026-04-16 17:41:48 +0000

    Status/2026Q1/valgrind: spell
---
 website/content/en/status/report-2026-01-2026-03/valgrind.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/content/en/status/report-2026-01-2026-03/valgrind.adoc b/website/content/en/status/report-2026-01-2026-03/valgrind.adoc
index 08f6cd12b0..2448ebfeb8 100644
--- a/website/content/en/status/report-2026-01-2026-03/valgrind.adoc
+++ b/website/content/en/status/report-2026-01-2026-03/valgrind.adoc
@@ -6,13 +6,13 @@ link:https://www.valgrind.org/docs/manual/dist.news.html[Valgrind News] URL: lin
 
 Contact: Paul Floyd <pjfloyd@wanadoo.fr>
 
-When FreeBSD 14.4-REELEASE came out and all went smoothely I thought that there would be little to say for this quarterly status report.
+When FreeBSD 14.4-RELEASE came out and all went smoothly I thought that there would be little to say for this quarterly status report.
 Then I started using a couple of 16.0-CURRENT machines that are part of the GCC server farm.
 There I saw several issues.
 At first there were many more failures than I would normally expect.
 A bit later the servers were updated and Valgrind broke quite badly, asserting early on in start up.
 Some of these issues were the usual high maintenance expected with Valgrind.
-A new Helgrind suppresion was required for internal locks used by `pthread_create`.
+A new Helgrind suppression was required for internal locks used by `pthread_create`.
 The servers were built and installed from source which affects the error callstacks occasionally.
 The Valgrind regression tests are quite sensitive to that kind of change and some extra filtering was required.
 The asserts were caused by incorrect assumptions in Valgrind that are used when the tool reads its own binary, mainly to enable it to print its own callstack if there is a crash.