X-Git-Url: https://git.dogcows.com/gitweb?a=blobdiff_plain;f=doc%2Fsparse.texi;h=e8a9ea1e8c982d4e3222a6e68c2851377c3f65fc;hb=7efe3850f6e058d33a46ef17cdc95df0469ed887;hp=1194357e289208bb6c93abbf47d5de5929dffb89;hpb=55abc110f57e77109f687bd62347fc2ce5ec0c5b;p=chaz%2Ftar

diff --git a/doc/sparse.texi b/doc/sparse.texi
index 1194357..e8a9ea1 100644
--- a/doc/sparse.texi
+++ b/doc/sparse.texi
@@ -132,8 +132,8 @@ This format presented the following two problems:
 @item
 Whereas the POSIX specification allows a variable to appear multiple
 times in a header, it requires that only the last occurrence be
-meaningful.  Thus, multiple ocurrences of @code{GNU.sparse.offset} and
-@code{GNU.sparse.numbytes} are conficting with the POSIX specs.
+meaningful.  Thus, multiple occurrences of @code{GNU.sparse.offset} and
+@code{GNU.sparse.numbytes} are conflicting with the POSIX specs.
 
 @item
 Attempting to extract such archives using a third-party @command{tar}s
@@ -175,8 +175,9 @@ The real name of the sparse file is stored in the variable
 @code{GNU.sparse.name}.  Thus, those @command{tar} implementations
 that are not aware of GNU extensions will at least extract the files
 into separate directories, giving the user a possibility to expand it
-afterwards @FIXME-ref{how to extract sparse file using third-party
-@command{tar}s}.
+afterwards.  @xref{extracting sparse v.0.x, Extraction of sparse
+members in v.0.1 format}, for the detailed description of how to
+restore such members using non-GNU @command{tar}s.
 
 The resulting @code{GNU.sparse.map} string can be @emph{very} long.
 Although POSIX does not impose any limit on the length of a @code{x}