From 556ac8a9a06325bc4fed15102b63279bc9ab8160 Mon Sep 17 00:00:00 2001
From: Joachim Metz <joachim.metz@gmail.com>
Date: Thu, 29 Aug 2013 08:33:38 +0200
Subject: [PATCH] Fixed some typos
---
tsk/fs/yaffs.cpp | 2 +-
tsk/img/img_io.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/tsk/fs/yaffs.cpp b/tsk/fs/yaffs.cpp
index 77f353972..fbac02c57 100644
--- a/tsk/fs/yaffs.cpp
+++ b/tsk/fs/yaffs.cpp
@@ -2640,7 +2640,7 @@ TSK_FS_INFO *
yaffsfs->spare_size = ssize == 0 ? YAFFS_DEFAULT_SPARE_SIZE : ssize;
yaffsfs->chunks_per_block = 64;
// TODO: Why are 2 different memory allocation methods used in the same code?
- // This make things unnecessary complex.
+ // This makes things unnecessary complex.
yaffsfs->chunkMap = new std::map<uint32_t, YaffsCacheChunkGroup>;
yaffsfs->max_obj_id = 1;
yaffsfs->max_version = 0;
diff --git a/tsk/img/img_io.c b/tsk/img/img_io.c
index c18677f95..6d552b7be 100644
--- a/tsk/img/img_io.c
+++ b/tsk/img/img_io.c
@@ -200,7 +200,7 @@ tsk_img_read(TSK_IMG_INFO * a_img_info, TSK_OFF_T a_off,
// if no error, then set the variables and copy the data
// Although a read_count of -1 indicates an error,
// since read_count is used in the calculation it may not be negative.
- // Also it does not make sence to copy data when the read_count is 0.
+ // Also it does not make sense to copy data when the read_count is 0.
if( read_count > 0 ) {
a_img_info->cache_age[cache_next] = CACHE_AGE;
a_img_info->cache_len[cache_next] = read_count;
--
GitLab