[master] e034ec823 spelling: catastrophe

[Nils Goroll]

commit e034ec8234a45d42d047f16c2d9542fb72d180f7
Author: Josh Soref <2119212+jsoref at users.noreply.github.com>
Date:   Mon Aug 19 12:11:25 2024 -0400

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

diff --git a/bin/varnishd/storage/storage_malloc.c b/bin/varnishd/storage/storage_malloc.c
index 7e7a7b8ac..8e245ef17 100644
--- a/bin/varnishd/storage/storage_malloc.c
+++ b/bin/varnishd/storage/storage_malloc.c
@@ -94,7 +94,7 @@ sma_alloc(const struct stevedore *st, size_t size)
 	/*
 	 * Do not collapse the sma allocation with sma->s.ptr: it is not
 	 * a good idea.  Not only would it make ->trim impossible,
-	 * performance-wise it would be a catastropy with chunksized
+	 * performance-wise it would be a catastrophe with chunksized
 	 * allocations growing another full page, just to accommodate the sma.
 	 */
 
diff --git a/bin/varnishd/storage/storage_umem.c b/bin/varnishd/storage/storage_umem.c
index 6d3402246..b1dbdbba2 100644
--- a/bin/varnishd/storage/storage_umem.c
+++ b/bin/varnishd/storage/storage_umem.c
@@ -170,7 +170,7 @@ smu_alloc(const struct stevedore *st, size_t size)
 	/*
 	 * Do not collapse the smu allocation with smu->s.ptr: it is not
 	 * a good idea.  Not only would it make ->trim impossible,
-	 * performance-wise it would be a catastropy with chunksized
+	 * performance-wise it would be a catastrophe with chunksized
 	 * allocations growing another full page, just to accommodate the smu.
 	 */