summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCarl Hetherington <cth@carlh.net>2015-08-28 09:50:20 +0100
committerCarl Hetherington <cth@carlh.net>2015-08-28 09:50:20 +0100
commit51e2ea8ee216222378e05e62b0ebaf998e3a2ff3 (patch)
treebba832a7eed766d6445bb554598ee2a4a9128d08
parent1b273e2c4a5c022f44ac82cbc662c62473335b88 (diff)
Manual wording tweaks.
-rw-r--r--doc/manual/dcpomatic.xml11
1 files changed, 6 insertions, 5 deletions
diff --git a/doc/manual/dcpomatic.xml b/doc/manual/dcpomatic.xml
index a8065a754..664b05438 100644
--- a/doc/manual/dcpomatic.xml
+++ b/doc/manual/dcpomatic.xml
@@ -1560,8 +1560,8 @@ methods to understand it.
</para>
<para>
-We suppose that we are trying to distribute a DCP, to
-Alice's cinema, without a troublemaker called Mallory being able to
+We suppose that we are trying to send a DCP to
+Alice's cinema without a troublemaker called Mallory being able to
watch it himself.
</para>
@@ -1588,11 +1588,12 @@ happened to know Mallory, she could just send him a copy of the key.
</para>
<para>
-The clever bit in DCP encryption requires the use of public-key
+The clever bit in the process requires the use of public-key
encryption. With this technique we can encrypt a block of data using
some &lsquo;public&rsquo; key. That data can then only be decrypted
-using a <emphasis>different</emphasis> &lsquo;private&rsquo; key. The
-private and public keys are related mathematically, but it is
+using a corresponding private key which is
+<emphasis>different</emphasis> to the public key. The private and
+public keys form a pair which are related mathematically, but it is
extremely hard (or rather, virtually impossible) to derive the private
key from the public key.
</para>