Commit 257877448a for openssl.org

commit 257877448ab9498b79635fb65a71e4eb0dd9280f
Author: Neil Horman <nhorman@openssl.org>
Date:   Thu Jan 22 13:48:30 2026 -0500

    Update test/README.md

    Co-authored-by: Matt Caswell <matt@openssl.org>

    Reviewed-by: Saša Nedvědický <sashan@openssl.org>
    Reviewed-by: Norbert Pocs <norbertp@openssl.org>
    MergeDate: Thu Jan 29 16:37:40 2026
    (Merged from https://github.com/openssl/openssl/pull/29573)

diff --git a/test/README.md b/test/README.md
index 71faaac9d7..9865933edb 100644
--- a/test/README.md
+++ b/test/README.md
@@ -190,7 +190,7 @@ Running Tests under Valgrind

 Normally, testing for memory leaks is accomplished by building Openssl with the
 enable-asan option, which links the library with the compiler asan library.  However
-Some people prefer to use valgrind to do dynamic instrumentation for memory leak checking.
+some people prefer to use valgrind to do dynamic instrumentation for memory leak checking.
 OpenSSL also offers a suppression file to suppress reachable memory leaks, that are often
 inappropriately considered to be true leaks.  In order to maintain and test this
 suppression file, OpenSSL tests can be run under valgrind automatically.