[master] 07b2063a5 spelling: anymore

[Poul-Henning Kamp]

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

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

diff --git a/doc/changes.rst b/doc/changes.rst
index 66edf08ac..3ed258aef 100644
--- a/doc/changes.rst
+++ b/doc/changes.rst
@@ -4176,7 +4176,7 @@ Bugs fixed
 * 1404_ - Don't send Content-Length on 304 Not Modified responses.
 * 1401_ - Varnish would crash when retrying a backend fetch too many times.
 * 1399_ - Memory get freed while in use by another thread/object
-* 1398_ - Fix NULL deref related to a backend we don't know any more.
+* 1398_ - Fix NULL deref related to a backend we don't know anymore.
 * 1397_ - Crash on backend fetch while LRUing.
 * 1395_ - End up in vcl_error also if fetch fails vcl_backend_response.
 * 1391_ - Client abort and retry during a streaming fetch would make Varnish assert.
@@ -5945,7 +5945,7 @@ varnishd
    core dumps. Make sure it's set.
 
 -  Doing purge.hash() with an empty string would cause us to dump core.
-   Fixed so we don't do that any more.
+   Fixed so we don't do that anymore.
 
 -  We ran into a problem with glibc's malloc on Linux where it seemed
    like it failed to ever give memory back to the OS, causing the system
diff --git a/doc/sphinx/phk/503aroundtheworld.rst b/doc/sphinx/phk/503aroundtheworld.rst
index c200ba7f5..8b16b4d84 100644
--- a/doc/sphinx/phk/503aroundtheworld.rst
+++ b/doc/sphinx/phk/503aroundtheworld.rst
@@ -109,7 +109,7 @@ Varnish release 2.1.2, May 2010 has the link, release 2.1.3 from
 July same year does not.)
 
 And that, my friends, is why the error message of last resort in
-Varnish Cache does not even contain a link any more.
+Varnish Cache does not even contain a link anymore.
 
 */phk*
 
diff --git a/doc/sphinx/phk/cheri1.rst b/doc/sphinx/phk/cheri1.rst
index 1f519f9eb..2c6d8f476 100644
--- a/doc/sphinx/phk/cheri1.rst
+++ b/doc/sphinx/phk/cheri1.rst
@@ -17,7 +17,7 @@ https://www.cl.cam.ac.uk/research/security/ctsrd/cheri/
 
 The core idea in CHERI is that pointers are not integers, which
 means that you cannot randomly make up or modify pointers to point
-at random things any more, whatever your intentions might be.
+at random things anymore, whatever your intentions might be.
 
 From a security point of view, this circumscribes several large
 classes of commonly used attack-vectors, and Microsoft Research
diff --git a/doc/sphinx/phk/notes.rst b/doc/sphinx/phk/notes.rst
index fc72554d2..79fa43f2a 100644
--- a/doc/sphinx/phk/notes.rst
+++ b/doc/sphinx/phk/notes.rst
@@ -29,7 +29,7 @@ So what's wrong with 1975 programming ?
 ---------------------------------------
 
 The really short answer is that computers do not have two kinds of
-storage any more.
+storage anymore.
 
 It used to be that you had the primary store, and it was anything
 from acoustic delaylines filled with mercury via small magnetic
diff --git a/doc/sphinx/phk/spdy.rst b/doc/sphinx/phk/spdy.rst
index 4cf9db228..e2e69898f 100644
--- a/doc/sphinx/phk/spdy.rst
+++ b/doc/sphinx/phk/spdy.rst
@@ -110,7 +110,7 @@ You should be able to do something like::
 
 And doing that is not really *that* hard, I think.  We just need
 to keep track of all the objects we instantiate and make sure they
-disappear and die when nobody is using them any more.
+disappear and die when nobody is using them anymore.
 
 A lot of the assumptions we made back in 2006 are no longer
 valid under such an architecture, but those same assumptions are
diff --git a/doc/sphinx/whats-new/changes-5.0.rst b/doc/sphinx/whats-new/changes-5.0.rst
index 22ce305d8..45de81d9a 100644
--- a/doc/sphinx/whats-new/changes-5.0.rst
+++ b/doc/sphinx/whats-new/changes-5.0.rst
@@ -137,7 +137,7 @@ Request Body sent always / "cacheable POST"
 Previously, we would only send a request body for passed requests (and
 for pipe mode, but this is special anyway and should be avoided).
 
-Not so any more, but the default behaviour has not changed:
+Not so anymore, but the default behaviour has not changed:
 
 Whenever a request has a body, it will get sent to the backend for a
 cache miss (and pass, as before). This can be prevented by an
diff --git a/doc/sphinx/whats-new/upgrading-6.2.rst b/doc/sphinx/whats-new/upgrading-6.2.rst
index 858b27833..84f64fb17 100644
--- a/doc/sphinx/whats-new/upgrading-6.2.rst
+++ b/doc/sphinx/whats-new/upgrading-6.2.rst
@@ -72,7 +72,7 @@ now also accept suitable numeral or quantitative arguments.
 These type-conversion functions should be fully backwards compatible,
 but the following differences should be noted:
 
-* The *fallback* is not required any more. A conversion failure in the
+* The *fallback* is not required anymore. A conversion failure in the
   absence of a *fallback* argument will now trigger a VCL failure.
 
 * A VCL failure will also be triggered if no or more than one argument