CD/verify: update the text

Stop talking about CDs!
Improve the wording in general.

1 files changed, 18 insertions, 17 deletions

diff --git a/english/CD/verify.wml b/english/CD/verify.wml
index 4db177514b7..38210499b12 100644
--- a/english/CD/verify.wml
+++ b/english/CD/verify.wml
@@ -1,22 +1,22 @@
-#use wml::debian::cdimage title="Verifying authenticity of Debian CDs" BARETITLE=true
+#use wml::debian::cdimage title="Verifying authenticity of Debian images" BARETITLE=true
 
 <p>
-Official releases of Debian CDs come with signed checksum files;
-look for them alongside the images in the <code>iso-cd</code>,
-<code>jigdo-dvd</code>, <code>iso-hybrid</code> etc. directories.
-These allow you to check that the images you download are correct.
-First of all, the checksum can be used to check that the CDs have not
-been corrupted during download.
-Secondly, the signatures on the checksum files allow you to confirm
-that the files are the ones officially released by the Debian CD /
-Debian Live team and have not been tampered with.
+Official releases of Debian installer and live images come with signed
+checksum files; look for them alongside the images in
+the <code>iso-cd</code>, <code>jigdo-dvd</code>, <code>iso-hybrid</code>
+etc. directories. These files allow you to check that the images you
+download are correct. First of all, the checksum can be used to check
+that the images have not been corrupted during download. Secondly, the
+signatures on the checksum files allow you to confirm that the files
+are the ones created and released by Debian, and have not been tampered
+with.
 </p>
 
 <p>
-To validate the contents of a CD image, just be sure to use the
-appropriate checksum tool.
-Cryptographically strong checksum
-algorithms (SHA256 and SHA512) are available for every releases; you should use the tools
+To validate the contents of an image file, be sure to use the
+appropriate checksum tool. Cryptographically strong checksum
+algorithms (SHA256 and SHA512) are available for every releases; you
+should use the tools
 <code>sha256sum</code> or <code>sha512sum</code> to work with these.
 </p>
 
@@ -26,9 +26,10 @@ verify them against the accompanying signature files (e.g.
 <code>SHA512SUMS.sign</code>). The keys used for these signatures are
 all in the <a href="https://keyring.debian.org">Debian GPG keyring</a>
 and the best way to check them is to use that keyring to validate via
-the web of trust. To make life easier for users, here are the
-fingerprints for the keys that have been used for releases in recent
-years, and links to download the public keys directly:
+the web of trust. To make life easier for people who don't have ready
+access to an existing Debian machine, here are details of the keys
+that have been used to sign releases in recent years, and links to
+download the public keys directly:
 </p>
 
 #include "$(ENGLISHDIR)/CD/CD-keys.data"