X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~yarrgweb/git?a=blobdiff_plain;f=yarrg%2FREADME.charset;h=f5926b091d4654a62464e3008d4318417ee96a6a;hb=938e38497928d3f0f4e32c0dcada210dffcac607;hp=65aa51aee70e1cf85be1be3229ed8d3dd54df4cb;hpb=c68fb80a6bbf7acbcac4b2cb2143f5fea745cd2b;p=ypp-sc-tools.db-live.git

diff --git a/yarrg/README.charset b/yarrg/README.charset
index 65aa51a..f5926b0 100644
--- a/yarrg/README.charset
+++ b/yarrg/README.charset
@@ -142,7 +142,7 @@ If you think you have made mistakes answering OCR queries (for
 example, the recognised data is wrong), you should delete the file
 _local-char*.txt, which contains your local updates.  It will then
 only use the centrally provided (and vetted) master file (which is
-automatically updated when you run the PCTB client, by default).
+automatically updated when you run the yarrg client, by default).
 
 It is also possible to have the OCR system reject particular strings.
 If you put a regexp in _local-reject.txt, any OCR result which
@@ -159,7 +159,7 @@ Enabling interactive character set update
 
 Now that you have read this document, you should rerun your OCR job
 with the --edit-charset option.  So run
-    ./ypp-commodities --edit-charset
+    ./yarrg --edit-charset
 In future, this option is not usually needed, because it is the
 default if there is a local character set dictionary _local-<h>.txt
 for the relevant character height.
@@ -180,6 +180,6 @@ server so that they can be checked by me and shared with other users.
 See README.privacy.
 
 If you need help please ask me (ijackson@chiark.greenend.org.uk, or
-Aristarchus on Midnight in game if I'm on line, or ask any pirate of
+Aristarchus on Cerulean in game if I'm on line, or ask any pirate of
 the crew Special Circumstances if they happen to know where I am
 and/or can get in touch).