From 9d9272273785f9eea4e5219d94cf693f50572c76 Mon Sep 17 00:00:00 2001 From: cha0smaster Date: Fri, 28 Oct 2005 19:00:14 +0000 Subject: [PATCH] Rest fixes from A Costa --- ntfsprogs/ntfscp.8.in | 4 ++-- ntfsprogs/ntfsundelete.8.in | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/ntfsprogs/ntfscp.8.in b/ntfsprogs/ntfscp.8.in index ac64c207..c5cfa393 100644 --- a/ntfsprogs/ntfscp.8.in +++ b/ntfsprogs/ntfscp.8.in @@ -65,7 +65,7 @@ Suppress some debug/warning/error messages. Show the version number, copyright and license .BR ntfscp . .TP -.B \-v, \-\-vebose +.B \-v, \-\-verbose Display more debug/warning/error messages. .SH DATA STREAMS All data on NTFS is stored in streams, which can have names. A file can have more than one data streams, but exactly one must have no name. The size of a file is the size of its unnamed data stream. Usually when you don't specify stream name you are access to unnamed data stream. If you want access to named data stream you need to add ":stream_name" to the filename. For example: by opening "some.mp3:artist" you will open stream "artist" in "some.mp3". But windows usually prevent you from accessing to named data streams, so you need to use some program like FAR or utils from cygwin to access named data streams. @@ -91,7 +91,7 @@ was written by Yura Pakhuchiy. .B ntfscp and this manual page is based on .B ntfscat -and it's manaul page by Richard Russon, so many thanks to him. Information about named data streams was partly taken from +and its manual page by Richard Russon, so many thanks to him. Information about named data streams was partly taken from .B ntfsdoc. .SH DEDICATION With love to Marina Sapego. diff --git a/ntfsprogs/ntfsundelete.8.in b/ntfsprogs/ntfsundelete.8.in index 3dac76a3..a90c327a 100644 --- a/ntfsprogs/ntfsundelete.8.in +++ b/ntfsprogs/ntfsundelete.8.in @@ -78,7 +78,7 @@ display as being 0% recoverable. To recover a file .B ntfsundelete has to read the file's metadata. Unfortunately, this isn't always intact. -When a file is deleted, the metadata can be left in an inconsistant state. e.g. +When a file is deleted, the metadata can be left in an inconsistent state. e.g. the file size may be zero; the dates of the file may be set to the time it was deleted, or random. .br @@ -116,7 +116,7 @@ filled with this byte. The default is zeros. .B \-\-case When scanning an NTFS volume, any filename matching (using the .B \-\-match -option) is case\-insensitive. This option makes the maching case\-sensitive. +option) is case\-insensitive. This option makes the matching case\-sensitive. .TP .BI "\-c " range .br