Update Document

[tortoisegit/TortoiseGitJp.git] / doc / source / en / TortoiseGit / tsvn_dug / dug_cleanup.xml

diff --git a/doc/source/en/TortoiseGit/tsvn_dug/dug_cleanup.xml b/doc/source/en/TortoiseGit/tsvn_dug/dug_cleanup.xml
index ad4e2c0..ee618af 100644 (file)
--- a/doc/source/en/TortoiseGit/tsvn_dug/dug_cleanup.xml
+++ b/doc/source/en/TortoiseGit/tsvn_dug/dug_cleanup.xml
@@ -6,7 +6,7 @@
                <primary>cleanup</primary>\r
        </indexterm>\r
        <para>\r
-               If a Subversion command cannot complete successfully, perhaps\r
+               If a Git command cannot complete successfully, perhaps\r
                due to server problems, your working copy can be left in an\r
                inconsistent state. In that case you need to use\r
                <menuchoice>\r
@@ -18,7 +18,7 @@
        </para>\r
        <para>\r
                Cleanup has another useful side effect. If a file date changes\r
-               but its content doesn't, Subversion cannot tell whether it has\r
+               but its content doesn't, Git cannot tell whether it has\r
                really changed except by doing a byte-by-byte comparison with\r
                the pristine copy. If you have a lot of files in this state it\r
                makes acquiring status very slow, which will make many dialogs\r
@@ -29,7 +29,7 @@
        <tip>\r
                <title>Use Commit Timestamps</title>\r
                <para>\r
-                       Some earlier releases of Subversion were affected by a bug\r
+                       Some earlier releases of Git were affected by a bug\r
                        which caused timestamp mismatch when you check out with\r
                        the <guilabel>Use commit timestamps</guilabel> option\r
                        checked. Use the Cleanup command to speed up these\r