aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJia Tan <jiat0218@gmail.com>2023-02-08 20:35:32 +0800
committerJia Tan <jiat0218@gmail.com>2023-02-15 00:20:44 +0800
commit421f2f2e160720f6009e3b6a125cafe2feaa9419 (patch)
tree128dd1421a7b09af3e62e27bc0c79c8ddd63ab0a
parentliblzma: Omit lzma_index_iter's internal field from Doxygen docs. (diff)
downloadxz-421f2f2e160720f6009e3b6a125cafe2feaa9419.tar.xz
liblzma: Reword a comment in index.h.
Diffstat (limited to '')
-rw-r--r--src/liblzma/api/lzma/index.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/liblzma/api/lzma/index.h b/src/liblzma/api/lzma/index.h
index c349b5f7..b478af37 100644
--- a/src/liblzma/api/lzma/index.h
+++ b/src/liblzma/api/lzma/index.h
@@ -307,13 +307,13 @@ typedef enum {
* \brief Calculate memory usage of lzma_index
*
* On disk, the size of the Index field depends on both the number of Records
- * stored and how big values the Records store (due to variable-length integer
+ * stored and the size of the Records (due to variable-length integer
* encoding). When the Index is kept in lzma_index structure, the memory usage
* depends only on the number of Records/Blocks stored in the Index(es), and
* in case of concatenated lzma_indexes, the number of Streams. The size in
* RAM is almost always significantly bigger than in the encoded form on disk.
*
- * This function calculates an approximate amount of memory needed hold
+ * This function calculates an approximate amount of memory needed to hold
* the given number of Streams and Blocks in lzma_index structure. This
* value may vary between CPU architectures and also between liblzma versions
* if the internal implementation is modified.