[master] d020ff29c spelling: everybody's

[Poul-Henning Kamp]

commit d020ff29c43b743795223fb13f9948da53f514a7
Author: Josh Soref <2119212+jsoref at users.noreply.github.com>
Date:   Wed Aug 7 08:30:56 2024 -0400

    spelling: everybody's
    
    Signed-off-by: Josh Soref <2119212+jsoref at users.noreply.github.com>

diff --git a/doc/sphinx/phk/VSV00001.rst b/doc/sphinx/phk/VSV00001.rst
index e7b34409f..3f26ccc77 100644
--- a/doc/sphinx/phk/VSV00001.rst
+++ b/doc/sphinx/phk/VSV00001.rst
@@ -28,7 +28,7 @@ VWV - Vulnerability Workaround in VCL
 Rolling a new Varnish release, even with an trivial one-line patch
 is not a fast operation, getting from patch to packages rolled and
 pushed into operating system respositories takes at least several
-days, provided you can get everybodys attention.
+days, provided you can get everybody's attention.
 
 Being able to offer users a way to mitigate security issues in VCL
 bypasses all that red tape:  The moment you have the advisory in
diff --git a/doc/sphinx/whats-new/changes-6.0.rst b/doc/sphinx/whats-new/changes-6.0.rst
index db0143184..ab147944b 100644
--- a/doc/sphinx/whats-new/changes-6.0.rst
+++ b/doc/sphinx/whats-new/changes-6.0.rst
@@ -83,7 +83,7 @@ as a result.
 
 VMOD functions can take optional arguments, these are different
 from defaulted arguments in that a separate flag tells if they
-were specified or not in the call.  For reasons of everybodys
+were specified or not in the call.  For reasons of everybody's
 sanity, all the arguments gets wrapped in a function-specific
 structure when this is used.