From cb264f77c8f320fcc429b17148f96c88161c536e Mon Sep 17 00:00:00 2001
From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com>
Date: Wed, 26 Jun 2024 12:03:34 +0100
Subject: [PATCH] Update product_docs/docs/pgd/5/durability/camo.mdx

---
 product_docs/docs/pgd/5/durability/camo.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/product_docs/docs/pgd/5/durability/camo.mdx b/product_docs/docs/pgd/5/durability/camo.mdx
index 9526e99b36d..226ff31810b 100644
--- a/product_docs/docs/pgd/5/durability/camo.mdx
+++ b/product_docs/docs/pgd/5/durability/camo.mdx
@@ -272,7 +272,7 @@ CAMO limitations are covered in [Durability limitations](limitations/#camo).
 
 ## Performance implications
 
-CAMO extends the Postgres replication protocol by adding a message round trip at commit. Applications have a higher
+CAMO extends the Postgres replication protocol by adding a message roundtrip at commit. Applications have a higher
 commit latency than with asynchronous replication, mostly determined by the round-trip time between involved nodes. Increasing the number of concurrent sessions can help to increase parallelism to obtain reasonable transaction throughput.
 
 The CAMO partner confirming transactions must store transaction states. Compared to non-CAMO operation, this might require an added seek for each transaction applied from the origin.