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

diff --git a/yarrg/README.charset b/yarrg/README.charset
index 65aa51a..4650aa0 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.