diff --git a/api/compression/compress_chunk.md b/api/compression/compress_chunk.md
index b257bfd757..04cc5ef4ae 100644
--- a/api/compression/compress_chunk.md
+++ b/api/compression/compress_chunk.md
@@ -16,7 +16,7 @@ import Deprecated2180 from "versionContent/_partials/_deprecated_2_18_0.mdx";
 
 <Deprecated2180 /> Replaced by <a href="https://docs.tigerdata.com/api/latest/hypercore/convert_to_columnstore/">convert_to_columnstore()</a>.
 
-The `compress_chunk` function is used to compress (or recompress, if necessary) 
+The `compress_chunk` function is used for synchronous compression (or recompression, if necessary) of 
 a specific chunk. This is most often used instead of the
 [`add_compression_policy`][add_compression_policy] function, when a user
 wants more control over the scheduling of compression. For most users, we
diff --git a/use-timescale/compression/manual-compression.md b/use-timescale/compression/manual-compression.md
index 5b1ec4ac33..9e544966eb 100644
--- a/use-timescale/compression/manual-compression.md
+++ b/use-timescale/compression/manual-compression.md
@@ -8,7 +8,7 @@ keywords: [compression, hypertables]
 # Manually compress chunks
 
 In most cases, an [automated compression policy][add_compression_policy] is sufficient to automatically compress your 
-chunks. However, if you want more control over compression, you can also manually compress specific chunks.
+chunks. However, if you want more control, you can also use manual synchronous compression of specific chunks. 
 
 Before you start, you need a list of chunks to compress. In this example, you
 use a hypertable called `example`, and compress chunks older than three days.