From 32dd3b31349f48adb21bf1923f076755705a508c Mon Sep 17 00:00:00 2001
From: Carl Hetherington <cth@carlh.net>
Date: Thu, 8 Nov 2018 12:55:14 +0000
Subject: [PATCH] Add reference to manual (#1385).

---
 doc/manual/dcpomatic.xml | 17 ++++++++++++-----
 1 file changed, 12 insertions(+), 5 deletions(-)

diff --git a/doc/manual/dcpomatic.xml b/doc/manual/dcpomatic.xml
index 66231090c..98ce4175a 100644
--- a/doc/manual/dcpomatic.xml
+++ b/doc/manual/dcpomatic.xml
@@ -536,7 +536,7 @@ OV&rdquo;.</listitem>
 </section>
 
 
-<section>
+<section xml:id="sec-decrypting">
 <title>Decrypting encrypted DCPs</title>
 
 <para>
@@ -2002,7 +2002,7 @@ delivery message (KDM) can play the DCP.
 
 <!-- ============================================================== -->
 <section>
-<title>How it works (in a nutshell)</title>
+<title>How it works</title>
 
 <para>
 This section attempts to summarise how DCP encryption works.  You can
@@ -2052,9 +2052,16 @@ key from the public key.
 <para>
 Public-key encryption allows us to distribute the DCP's key to Alice
 securely.  The manufacturer of Alice's projector generates a public
-and private key.  They hide the private key deep inside the bowels of
-the projector (inside an integrated circuit) where no-one can read it.
-They then make the public key available to anyone who is interested.
+and private key.  They hide the private key inside the projector where
+no-one can read it.  They then make the public key available to anyone
+who is interested.
+</para>
+
+<para>
+DCP-o-matic has a similar arrangement except that it stores its
+private keys in the user's configuration file. See <xref
+linkend="sec-decrypting"/> for details of how to share DCP-o-matic's
+certificate so that others can make encrypted DCPs for DCP-o-matic.
 </para>
 
 <para>
-- 
2.30.2