Refactor: Minor style changes

Author: InfiniteSynthesis

algorithms/extend-policy.tex

@@ -77,8 +77,8 @@
 		\LineComment{Bootstrapping cannot take too much time}
 		\oneLineIf{$\tauLow = 0$ \textbf{and} $\ledgerTime - \tauLow > 2 \cdot \mathtt{maxTime_{window}}$}{\Return \txSeqProposalDefault}
 
-		\LineComment{Old enough, valid transactions should be included}
 		\oneLineIf{$\mathsf{oldValidTxMissing}$}{\Return \txSeqProposalDefault}
+		\Comment{Old enough, valid transactions should be included}
 
 		\State{\Return \txSeqProposal}
 	\end{algorithmic}

content/protocol-details/protocol-desc.tex

@@ -27,7 +27,7 @@ \subsection{A Full Protocol Description}
 %
 In order to issue a transaction \tx, party \party needs to encrypt \tx using a subset of on-chain public keys, computed from a ticket associated with a block in the settled blockchain.
 %
-Additionally, a NIZKPoK that proves the validity of \tx and the correctness of each ciphertext should be attached (See the relation in Equation~\eqref{eq:nizk-relation}).
+Additionally, a NIZKPoK that proves the validity of \tx and the correctness of each ciphertext should be attached (See the relation in~\cref{eq:nizk-relation}).
 
 \input{protocols/issue-nex-tx}
 

content/protocol-details/transaction-encryption.tex

@@ -181,7 +181,7 @@ \subsection{Transaction Encryption from Trusted Hardware}
 
 \paragraph{Issuing a transaction.}
 %
-We elaborate on how a client can issue a transaction, the code description of this procedure is presented in~\cref{algorithm:issue-new-transaction} in~\cref{subsec:protocol-desc}.
+We elaborate on how a client can issue a transaction, the code description of this procedure is presented in~\cref{protocol:issue-new-transaction} in~\cref{subsec:protocol-desc}.
 %
 Recall that clients are not equipped with trusted hardware thus they should encrypt their transactions using the maintainers' public keys.
 %