1 files changed, 2 insertions, 2 deletions

diff --git a/fs/xfs/xfs_log_recover.c b/fs/xfs/xfs_log_recover.c
index add13f507ed2..1f0016b0b4ec 100644
--- a/fs/xfs/xfs_log_recover.c
+++ b/fs/xfs/xfs_log_recover.c
@@ -583,7 +583,7 @@ xlog_find_head(
                  *        x | x ... | x - 1 | x
                  * Another case that fits this picture would be
                  *        x | x + 1 | x ... | x
-                 * In this case the head really is somwhere at the end of the
+                 * In this case the head really is somewhere at the end of the
                  * log, as one of the latest writes at the beginning was
                  * incomplete.
                  * One more case is
@@ -2799,7 +2799,7 @@ xlog_recover_do_trans(
                  * we don't need to worry about the block number being
                  * truncated in > 1 TB buffers because in user-land,
                  * we're now n32 or 64-bit so xfs_daddr_t is 64-bits so
-                 * the blkno's will get through the user-mode buffer
+                 * the blknos will get through the user-mode buffer
                  * cache properly.  The only bad case is o32 kernels
                  * where xfs_daddr_t is 32-bits but mount will warn us
                  * off a > 1 TB filesystem before we get here.