[master] 4623d2592 doc: Spelling galore aftermath

[Dridi Boukelmoune]

commit 4623d25925fb453462bfc27d1412ca944ce2b422
Author: Dridi Boukelmoune <dridi.boukelmoune at gmail.com>
Date:   Tue Sep 10 17:43:56 2024 +0200

    doc: Spelling galore aftermath
    
    Better diff with the --word-diff option.

diff --git a/doc/changes.rst b/doc/changes.rst
index 42c850753..60c4559f1 100644
--- a/doc/changes.rst
+++ b/doc/changes.rst
@@ -591,8 +591,7 @@ Varnish Cache 7.4.0 (2023-09-15)
   amount of free workspace for backend connections.
 
 * Object creation failures by the selected storage engine are now
-  logged under the ``Error`` tag as ``Failed to create object object
-  from %s %s``.
+  logged under the ``Error`` tag as ``Failed to create object from %s %s``.
 
 * The limit on the size of ``varnishtest`` macros has been raised to
   2KB.
diff --git a/doc/sphinx/phk/thetoolsweworkwith.rst b/doc/sphinx/phk/thetoolsweworkwith.rst
index b763c8b3c..c8b9cc782 100644
--- a/doc/sphinx/phk/thetoolsweworkwith.rst
+++ b/doc/sphinx/phk/thetoolsweworkwith.rst
@@ -48,7 +48,7 @@ certainly was enough to make me angry.
 
 Let me give you an example of their utter silliness:
 
-The book which defined the C langauge had a list af reserved
+The book which defined the C language had a list of reserved
 identifiers, all of them lower-case words.  The UNIX libraries
 defined a lot of functions, all of them lower-case words.
 
@@ -113,7 +113,7 @@ that, or without wasting a lot of time debugging silly mistakes.
 
 If you look in the Varnish source code, which uses pthreads, you
 will see that I have wrapped pthread mutexes in my own little
-datastructure, to be able to do those asserts, and to get some
+data structure, to be able to do those asserts, and to get some
 usable statistics on lock-contention.
 
 Another example where C1X did not improve on pthreads at all, was
@@ -152,7 +152,7 @@ Because it's not like the call is actually guaranteed to return at
 16:00Z if you ask it to, you are only promised it will not return
 later than that, so you have to wrap the call in a loop.
 
-Whoever defined the select(2) and poll(2) systemcalls knew better
+Whoever defined the select(2) and poll(2) system calls knew better
 than the POSIX and ISO-C group-think:  They specified a maximum
 duration for the call, because then it doesn't matter what time
 it is, only how long time has transpired.
diff --git a/doc/sphinx/reference/vmod.rst b/doc/sphinx/reference/vmod.rst
index bac18cd03..367d7e8ac 100644
--- a/doc/sphinx/reference/vmod.rst
+++ b/doc/sphinx/reference/vmod.rst
@@ -488,7 +488,7 @@ VCL_SUB
 	side).
 
 	For more than one invocation of ``VRT_call()``, VMODs *must*
-	check if ``VRT_handled()`` returns non-zero in between calls:
+	check if ``VRT_handled()`` returns non-zero in-between calls:
 	The called SUB may have returned with an action (any
 	``return(x)`` other than plain ``return``) or may have failed
 	the VCL, and in both cases the calling VMOD *must* return
diff --git a/doc/sphinx/whats-new/changes-7.2.rst b/doc/sphinx/whats-new/changes-7.2.rst
index 0d97bd998..d46e26ad1 100644
--- a/doc/sphinx/whats-new/changes-7.2.rst
+++ b/doc/sphinx/whats-new/changes-7.2.rst
@@ -25,7 +25,7 @@ keep a place ready for it in the overall architecture.
 
 Now a credible use-case finally appeared, and we have implemented
 "Varnish Extensions" (VTLA: "VEXT"), which can both be used to load
-ambient VMODs and to implement entirely new functionally, for instance
+ambient VMODs and to implement entirely new functionality, for instance
 stevedores.
 
 See :ref:`ref-vext` in the reference manual for more information.