diff --git a/doc/hacking.txt b/doc/hacking.txt
index 2a4979bc..2cd107b2 100644
--- a/doc/hacking.txt
+++ b/doc/hacking.txt
@@ -661,7 +661,7 @@ diff -ru elinks/ elinks+mysuperfeature/ >elinks-mysuperfeature.patch
 Please manually remove any bloat like changes in ./configure, whitespace
 changes etc. ;-).
 
-We also accept output from `cvs diff -u` :).  The statement about bloat
+We also accept output from `git diff` :).  The statement about bloat
 removing above still applies.
 
 Big patches are hard to review so if your feature involves a lot of changes
diff --git a/po/README b/po/README
index 0ff0579e..bf45e98c 100644
--- a/po/README
+++ b/po/README
@@ -107,7 +107,7 @@ reasonable editor.
 In order to compile, get warnings and actually use your updated language file
 you will however need the gettext tools. If you don't have any of these tools
 please don't hesitate to still do the update and send it to the mailinglist or
-bugzilla so it can be added to CVS. By next release or nightly generated tarball
+bugzilla so it can be added to Git. By next release or nightly generated tarball
 you can then make use of your updates.
 
 2.2 The basics of updating:
@@ -185,7 +185,7 @@ translation for each plural form.
 2.3 Synchronizing .po files with the code
 -----------------------------------------
 
-IMPORTANT: if you changed strings in the code, or if you're using a cvs version
+IMPORTANT: if you changed strings in the code, or if you're using a Git version
 of ELinks, take care of synchronization between code and po files.  Before any
 change to a po file, you must synchronize it with code.