[master] 6cdd5f6c8 spelling: cannot

Poul-Henning Kamp phk at FreeBSD.org
Mon Aug 19 12:47:07 UTC 2024 

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

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

diff --git a/doc/sphinx/phk/cheri4.rst b/doc/sphinx/phk/cheri4.rst
index 26baeb015..6c96038b2 100644
--- a/doc/sphinx/phk/cheri4.rst
+++ b/doc/sphinx/phk/cheri4.rst
@@ -36,7 +36,7 @@ gives you the "capability" to access the memory, and therefore they
 can be restricted separately from the memory they provide access to.
 
 If you could just create your own "capabilities" out of integers,
-that would be no big improvement, but you can not:  Under CHERI you
+that would be no big improvement, but you cannot:  Under CHERI you
 can only make a new capability from another capability, and the new
 one can never be more potent than the one it is derived from.
 
diff --git a/doc/sphinx/phk/gzip.rst b/doc/sphinx/phk/gzip.rst
index 61c4e19b0..0eafa9943 100644
--- a/doc/sphinx/phk/gzip.rst
+++ b/doc/sphinx/phk/gzip.rst
@@ -58,7 +58,7 @@ To always entice the backend into sending us gzip'ed content.
 
 Varnish will not gzip any content on its own (but see below), we trust
 the backend to know what content can be sensibly gzip'ed (html) and what
-can not (jpeg)
+cannot (jpeg)
 
 If in vcl_backend_response{} we find out that we are trying to deliver a
 gzip'ed object to a client that has not indicated willingness to receive
diff --git a/doc/sphinx/phk/vcl_expr.rst b/doc/sphinx/phk/vcl_expr.rst
index e2b18e9c8..4f7ad3b7e 100644
--- a/doc/sphinx/phk/vcl_expr.rst
+++ b/doc/sphinx/phk/vcl_expr.rst
@@ -25,12 +25,12 @@ time (Expires).
 
 Obviously, you can add a TIME and DURATION, the result is a TIME.
 
-Equally obviously, you can not add TIME to TIME, but you can subtract
+Equally obviously, you cannot add TIME to TIME, but you can subtract
 TIME from TIME, resulting in a DURATION.
 
 VCL do also have "naked" numbers, like INT and REAL, but what you
 can do with them is very limited.  For instance you can multiply a
-duration by a REAL, but you can not multiply a TIME by anything.
+duration by a REAL, but you cannot multiply a TIME by anything.
 
 Given that we have our own types, the next question is what
 precedence operators have.
diff --git a/doc/sphinx/reference/varnishncsa.rst b/doc/sphinx/reference/varnishncsa.rst
index dc09410f7..de5ea8428 100644
--- a/doc/sphinx/reference/varnishncsa.rst
+++ b/doc/sphinx/reference/varnishncsa.rst
@@ -149,7 +149,7 @@ Supported formatters are:
   * ``%{msec_frac}``: millisecond fraction
   * ``%{usec_frac}``: microsecond fraction
 
-  The extensions can not be combined with each other or strftime(3) in
+  The extensions cannot be combined with each other or strftime(3) in
   the same specification. Use multiple ``%{X}t`` specifications instead.
 
 %T
diff --git a/doc/sphinx/reference/vcl-backend.rst b/doc/sphinx/reference/vcl-backend.rst
index a62f94586..00904acbf 100644
--- a/doc/sphinx/reference/vcl-backend.rst
+++ b/doc/sphinx/reference/vcl-backend.rst
@@ -197,8 +197,8 @@ Unless specified for *destination*, the ``connect_timeout``,
 ``first_byte_timeout`` and ``between_bytes_timeout`` attributes are
 copied from *proxy* to *destination*.
 
-As of this release, the *proxy* backend used with ``.via`` can not be
-a director, it can not itself use ``.via`` (error: *Can not stack .via
+As of this release, the *proxy* backend used with ``.via`` cannot be
+a director, it cannot itself use ``.via`` (error: *Cannot stack .via
 backends*) and the protocol is fixed to `PROXY2`_.
 
 Implementation detail:
diff --git a/doc/sphinx/reference/vmod.rst b/doc/sphinx/reference/vmod.rst
index 193b9060d..197d91b43 100644
--- a/doc/sphinx/reference/vmod.rst
+++ b/doc/sphinx/reference/vmod.rst
@@ -9,7 +9,7 @@
 VMOD - Varnish Modules
 %%%%%%%%%%%%%%%%%%%%%%
 
-For all you can do in VCL, there are things you can not do.
+For all you can do in VCL, there are things you cannot do.
 Look an IP number up in a database file for instance.
 VCL provides for inline C code, and there you can do everything,
 but it is not a convenient or even readable way to solve such
@@ -89,7 +89,7 @@ that at length in a moment.
 Notice that the third function returns VOID, that makes it a "procedure"
 in VCL lingo, meaning that it cannot be used in expressions, right side
 of assignments and such.  Instead it can be used as a primary action,
-something functions which return a value can not::
+something functions which return a value cannot::
 
 	sub vcl_recv {
 		std.set_ip_tos(32);
@@ -483,7 +483,7 @@ VCL_SUB
 	references never be called from a different VCL.
 
 	``VRT_call()`` fails the VCL for recursive calls and when the
-	``VCL_SUB`` can not be called from the current context
+	``VCL_SUB`` cannot be called from the current context
 	(e.g. calling a subroutine accessing ``req`` from the backend
 	side).
 
diff --git a/doc/sphinx/whats-new/changes-5.0.rst b/doc/sphinx/whats-new/changes-5.0.rst
index 45de81d9a..433386532 100644
--- a/doc/sphinx/whats-new/changes-5.0.rst
+++ b/doc/sphinx/whats-new/changes-5.0.rst
@@ -86,7 +86,7 @@ As useful as this feature is, it has caused a lot of headaches to
 varnish administrators along the lines of "why the *beep* doesn't
 Varnish cache this": A hit-for-pass object stayed in cache for however
 long its ttl dictated and prevented caching whenever it got hit ("for
-that url" in most cases). In particular, as a pass object can not be
+that url" in most cases). In particular, as a pass object cannot be
 turned into something cacheable retrospectively
 (``beresp.uncacheable`` can be changed from ``false`` to ``true``, but
 not the other way around), even responses which would have been
diff --git a/doc/sphinx/whats-new/changes-7.3.rst b/doc/sphinx/whats-new/changes-7.3.rst
index dc6af79fc..164952620 100644
--- a/doc/sphinx/whats-new/changes-7.3.rst
+++ b/doc/sphinx/whats-new/changes-7.3.rst
@@ -159,7 +159,7 @@ avoids duplicates when a custom implementation relied on ``http_*()`` that
 would also log the headers being set up.
 
 The ``VRT_new_backend*()`` functions take an additional backend argument, the
-optional via backend. It can not be a custom backend implementation, but it
+optional via backend. It cannot be a custom backend implementation, but it
 can be a director resolving a native backend.
 
 There is a new ``authority`` field for via backends in ``struct vrt_backend``.
diff --git a/doc/sphinx/whats-new/upgrading-7.1.rst b/doc/sphinx/whats-new/upgrading-7.1.rst
index 86ec9eb89..fc8497e5a 100644
--- a/doc/sphinx/whats-new/upgrading-7.1.rst
+++ b/doc/sphinx/whats-new/upgrading-7.1.rst
@@ -60,7 +60,7 @@ The feature flag is off by default, preserving the existing behavior
 to continue ESI processing despite include failures.
 
 Users of persistent storage engines be advised that objects created
-before the introduction of this change can not carry the
+before the introduction of this change cannot carry the
 ``onerror="continue"`` attribute and, consequently, will be handled as
 if it was not present if the ``+esi_include_onerror`` feature flag is
 enabled.

More information about the varnish-commit mailing list