X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Ffilesys.texi;h=41f860f63eea2cc53627e0b711d5bd5bf0d263c3;hb=9f013d0930202eea99c21083b71098a0df64be0d;hp=4c77d305fb3a162da64060e10a836770a0b67941;hpb=a03618133f7df0954802a470a4bee7674f7aed45;p=pintos-anon

diff --git a/doc/filesys.texi b/doc/filesys.texi
index 4c77d30..41f860f 100644
--- a/doc/filesys.texi
+++ b/doc/filesys.texi
@@ -11,7 +11,7 @@ You may build project 4 on top of project 2 or project 3.  In either
 case, all of the functionality needed for project 2 must work in your
 filesys submission.  If you build on project 3, then all of the project
 3 functionality must work also, and you will need to edit
-@file{filesys/Make.vars} to enable VM functionality.  You can receive up
+@file{filesys/Make.vars} to enable VM functionality. You can receive up
 to 5% extra credit if you do enable VM.
 
 @menu
@@ -457,7 +457,7 @@ modified by the reference solution.
  30 files changed, 2721 insertions(+), 286 deletions(-)
 @end verbatim
 
-@item Can @code{BLOCk_SECTOR_SIZE} change?
+@item Can @code{BLOCK_SECTOR_SIZE} change?
 
 No, @code{BLOCK_SECTOR_SIZE} is fixed at 512.  For IDE disks, this
 value is a fixed property of the hardware.  Other disks do not