summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPiotr Strzelczyk <piotr@eps.gda.pl>2009-06-30 19:13:07 +0000
committerPiotr Strzelczyk <piotr@eps.gda.pl>2009-06-30 19:13:07 +0000
commite9888ce9680c4486a60bc99aeca20fab17d95205 (patch)
treee74078e37d20e51c89ae8409b8ef3677a56fc050
parent8240da014fb3e032314d313048b6c9d34a8df665 (diff)
a couple of documentation fixes
git-svn-id: svn://tug.org/texlive/trunk@14030 c570f23f-e606-0410-a88d-b1316a301751
-rw-r--r--Master/texmf/scripts/texlive/updater-w32.bat4
1 files changed, 2 insertions, 2 deletions
diff --git a/Master/texmf/scripts/texlive/updater-w32.bat b/Master/texmf/scripts/texlive/updater-w32.bat
index 2984c0564c2..163138bd2a7 100644
--- a/Master/texmf/scripts/texlive/updater-w32.bat
+++ b/Master/texmf/scripts/texlive/updater-w32.bat
@@ -24,7 +24,7 @@ rem
:: abort if it fails to do so. This means that the trigger script
:: has to be created by the current invocation of tlmgr.pl
:: * write_w32_updater subroutine in tlmgr.pl prepares the update
-:: and writes the trigger script. Packages in .lzma archives are
+:: and writes the trigger script. Packages in .xz archives are
:: dowloaded/copied and uncompressed to .tar files. Also .tar
:: backups of the current packages are made. If everything is
:: successful, the trigger script is written, otherwise the update
@@ -53,7 +53,7 @@ rem
:: (2) untar all package backups
:: (3) include .tlpobj files (from backup) into tlpdb
:: (4) print restore info
-:: Any error during (1) or (2) and we go into panic mode. At this
+:: Any error during (2) or (3) and we go into panic mode. At this
:: point there is no guarantee that the installation is still
:: working. There is not much we can do but to print failed restore
:: info and give instructions to download and run