diff --git a/zip-0324.rst b/zip-0324.rst
index 60688e08..93f861e5 100644
--- a/zip-0324.rst
+++ b/zip-0324.rst
@@ -386,7 +386,7 @@ In the above description, we explicitly list the notes involved in the payment (
 
 Instead, we can have the nodes be implicitly identified by the spending key (or similar) included in the URI. This can make URI shorter, thus less scary and less likely to run into length limits (consider SMS). The following alternatives are feasible:
 
-0. Explicitly list the note commitments within the URI.
+:math:`\hspace{0.9em}`\0. Explicitly list the note commitments within the URI.
 
 1. Include only the spending key(s) in the URI, and have the recipient scan the blockchain using the existing mechanism (trial decryption of the encrypted memo field). This is very slow, and risks denial-of-service attacks. Would be faster in the nominal case if the scanning is done backwards (newest block first), or if told by the sender when the transactions were mined; but scanning the whole chain for nonexistent transactions (perhaps induced by a DoS) would still take very long.