diff --git a/proposals/1756-cross-signing.md b/proposals/1756-cross-signing.md
index a1b3cf55..0bb365e9 100644
--- a/proposals/1756-cross-signing.md
+++ b/proposals/1756-cross-signing.md
@@ -1,3 +1,9 @@
+# Background
+
+FIXME: something something
+
+# Proposal
+
 Each user has a "master identity key" that is used to sign their devices, and
 is signed by all of their devices.  When one user (Alice) verifies another
 user's (Bob's) identity, Alice will sign Bob's master identity key with her
@@ -114,14 +120,18 @@ One way to solve this is by registering a "virtual device", which is used to
 sign other devices.  This solution would be similar to this proposal.  However,
 real devices would still form an integral part of the attestation graph.  For
 example, if Alice's phone verifies Bob's tablet, the attestation graph might
-look like Alice's laptop <-> Alice's virtual device <-> Alice's phone <-> Bob's
-tablet <-> Bob's virtual device <-> Bob's desktop.  So if Bob replaces his
-tablet without re-verifying with Alice, this will split the graph and Alice
-will not be able to verify Bob's other devices.  In contrast, in this proposal,
-Alice and Bob's master keys directly sign each other, and the attestation graph
-would look like Alice's phone <-> Alice's master device <-> Bob's master device
-<-> Bob's tablet.  In this case, Bob's tablet can be replaced without breaking
-the graph.  FIXME: graphviz-ify the attestation graphs
+look like:
+
+![](images/1756-graph1.dot.png)
+
+If Bob replaces his tablet without re-verifying with Alice, this will split the
+graph and Alice will not be able to verify Bob's other devices.  In contrast,
+in this proposal, Alice and Bob's master keys directly sign each other, and the
+attestation graph would look like:
+
+![](images/1756-graph2.dot.png)
+
+In this case, Bob's tablet can be replaced without breaking the graph.
 
 With normal cross-signing, it is not clear how to recover from a stolen device.
 For example, if Mallory steals one of Alice's devices and revokes Alice's other
@@ -133,3 +143,7 @@ whether it should be a statement that the device should not be trusted at all.)
 In contrast, with this proposal, there is a clear way to rebuild the
 attestation graph: create a new master identity key, and re-verify all devices
 with it.
+
+# Conclusion
+
+This proposal presents an alternative cross-signing mechanism to MSC1680.
diff --git a/proposals/images/1756-graph1.dot b/proposals/images/1756-graph1.dot
new file mode 100644
index 00000000..8a8c9641
--- /dev/null
+++ b/proposals/images/1756-graph1.dot
@@ -0,0 +1,13 @@
+graph {
+A1 [label="A's PDP-11"]
+AV [label="A's virtual device"]
+A2 [label="A's Osborne 2"]
+B1 [label="B's Dynabook"]
+BV [label="B's virtual device"]
+B2 [label="B's VAX"]
+A1 -- AV
+AV -- A2
+A2 -- B1
+B1 -- BV
+BV -- B2
+}
\ No newline at end of file
diff --git a/proposals/images/1756-graph1.dot.png b/proposals/images/1756-graph1.dot.png
new file mode 100644
index 00000000..87a78f83
Binary files /dev/null and b/proposals/images/1756-graph1.dot.png differ
diff --git a/proposals/images/1756-graph2.dot b/proposals/images/1756-graph2.dot
new file mode 100644
index 00000000..6a45abe9
--- /dev/null
+++ b/proposals/images/1756-graph2.dot
@@ -0,0 +1,13 @@
+graph {
+A1 [label="A's PDP-11"]
+AM [label="A's master key"]
+A2 [label="A's Osborne 2"]
+B1 [label="B's Dynabook"]
+BM [label="B's master key"]
+B2 [label="B's VAX"]
+A1 -- AM
+AM -- A2
+AM -- BM
+B1 -- BM
+BM -- B2
+}
\ No newline at end of file
diff --git a/proposals/images/1756-graph2.dot.png b/proposals/images/1756-graph2.dot.png
new file mode 100644
index 00000000..93379122
Binary files /dev/null and b/proposals/images/1756-graph2.dot.png differ