aboutsummaryrefslogtreecommitdiff
path: root/src/liblzma/api
diff options
context:
space:
mode:
authorLasse Collin <lasse.collin@tukaani.org>2008-05-06 15:15:07 +0300
committerLasse Collin <lasse.collin@tukaani.org>2008-05-06 15:15:07 +0300
commit11de5d5267f7a0a7f0a4d34eec147e65eaf9f9cf (patch)
tree5503159532d56511eb7a0d48812d4f99bc39df69 /src/liblzma/api
parentTypo fix (diff)
downloadxz-11de5d5267f7a0a7f0a4d34eec147e65eaf9f9cf.tar.xz
Bunch of grammar fixes from meyering.
Diffstat (limited to 'src/liblzma/api')
-rw-r--r--src/liblzma/api/lzma/memlimit.h6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/liblzma/api/lzma/memlimit.h b/src/liblzma/api/lzma/memlimit.h
index 6b07679d..7a856a27 100644
--- a/src/liblzma/api/lzma/memlimit.h
+++ b/src/liblzma/api/lzma/memlimit.h
@@ -22,7 +22,7 @@
/**
- * \brief Opaque data type used with the memory usage limitting functions
+ * \brief Opaque data type used with the memory usage limiting functions
*/
typedef struct lzma_memlimit_s lzma_memlimit;
@@ -39,7 +39,7 @@ typedef struct lzma_memlimit_s lzma_memlimit;
* to these functions can be used in lzma_allocator structure, which makes
* it easy to limit memory usage with liblzma.
*
- * The memory limiter functions are not tied to limitting memory usage
+ * The memory limiter functions are not tied to limiting memory usage
* with liblzma itself. You can use them with anything you like.
*
* In multi-threaded applications, only one thread at once may use the same
@@ -161,7 +161,7 @@ extern void *lzma_memlimit_alloc(
/**
- * \brief Removes the pointer from memory limitting list
+ * \brief Removes the pointer from memory limiting list
*
* \param mem Pointer to a lzma_memlimit structure returned
* earlier by lzma_memry_limit_create().