[Bug-tar] typos

[Ralf Wildenhues]

Hello there,

I found a couple of typos again.  (Dunno about the preferred spelling
'inumbers' or 'i-numbers', but using both in one sentence seems weird.)

Cheers,
Ralf

2006-12-09  Ralf Wildenhues  <address@hidden>

        * doc/tar.texi: Fix some typos.
        (concatenate): Use name consistently in example.

Index: doc/tar.texi
===================================================================
RCS file: /cvsroot/tar/tar/doc/tar.texi,v
retrieving revision 1.127
diff -u -r1.127 tar.texi
--- doc/tar.texi        7 Dec 2006 14:33:30 -0000       1.127
+++ doc/tar.texi        8 Dec 2006 10:35:15 -0000
@@ -4133,7 +4133,7 @@
 $ @kbd{tar -tvf bluesrock.tar}
 -rw-r--r-- melissa user    105 1997-01-21 19:42 blues
 -rw-r--r-- melissa user     33 1997-01-20 15:34 rock
-$ @kbd{tar -tvf jazzfolk.tar}
+$ @kbd{tar -tvf folkjazz.tar}
 -rw-r--r-- melissa user     20 1996-09-23 16:44 folk
 -rw-r--r-- melissa user     65 1997-01-30 14:15 jazz
 @end smallexample
@@ -4142,11 +4142,11 @@
 
 @smallexample
 $ @kbd{cd ..}
-$ @kbd{tar --concatenate --file=bluesrock.tar jazzfolk.tar}
+$ @kbd{tar --concatenate --file=bluesrock.tar folkjazz.tar}
 @end smallexample
 
 If you now list the contents of the @file{bluesrock.tar}, you will see
-that now it also contains the archive members of @file{jazzfolk.tar}:
+that now it also contains the archive members of @file{folkjazz.tar}:
 
 @smallexample
 $ @kbd{tar --list --file=bluesrock.tar}
@@ -8618,7 +8618,7 @@
 @node Split Recovery
 @subsubsection Extracting Members Split Between Volumes
 
address@hidden Mutli-volume archives, extracting using non-GNU tars
address@hidden Multi-volume archives, extracting using non-GNU tars
 If a member is split between several volumes of an old GNU format archive
 most third party @command{tar} implementation will fail to extract
 it.  To extract it, use @command{tarcat} program (@pxref{Tarcat}).
@@ -8633,7 +8633,7 @@
 $ @kbd{tarcat vol-1.tar vol-2.tar vol-3.tar | tar xf -}
 @end smallexample
 
address@hidden Mutli-volume archives in PAX format, extracting using non-GNU 
tars
address@hidden Multi-volume archives in PAX format, extracting using non-GNU 
tars
 You could use this approach for most (although not all) PAX
 format archives as well.  However, extracting split members from a PAX
 archive is a much easier task, because PAX volumes are constructed in
@@ -8647,7 +8647,7 @@
 @end smallexample
 
 @noindent
-where symbols preceeded by @samp{%} are @dfn{macro characters} that
+where symbols preceded by @samp{%} are @dfn{macro characters} that
 have the following meaning:
 
 @multitable @columnfractions .25 .55
@@ -8729,7 +8729,7 @@
 Any @command{tar} implementation will be able to extract sparse members from a
 PAX archive.  However, the extracted files will be @dfn{condensed},
 i.e., any zero blocks will be removed from them.  When we restore such
-a condensed file to its original form, by adding zero bloks (or
+a condensed file to its original form, by adding zero blocks (or
 @dfn{holes}) back to their original locations, we call this process
 @dfn{expanding} a compressed sparse file.
 
@@ -8806,7 +8806,7 @@
 
 @noindent
 The program behaves the same way all UNIX utilities do: it will keep
-quiet unless it has simething important to tell you (e.g. an error
+quiet unless it has something important to tell you (e.g., an error
 condition or something).  If you wish it to produce verbose output,
 similar to that from the dry run mode, use @option{-v} option:
 
@@ -8978,7 +8978,7 @@
 (4.3-tahoe and later).
 
 @command{tar}'s way of handling multiple hard links to a file can handle
-file systems that support 32-bit inumbers (e.g., the BSD file system);
+file systems that support 32-bit i-numbers (e.g., the BSD file system);
 @command{cpio}s way requires you to play some games (in its "binary"
 format, i-numbers are only 16 bits, and in its "portable ASCII" format,
 they're 18 bits---it would have to play games with the "file system ID"