Issue #775 typos and bleeding italics

shelley/chain-and-ledger/formal-spec/chain.tex

@@ -755,9 +755,9 @@ \subsection{Block Header Transition}
 The BHEAD rule has two predicate failures:
 \begin{itemize}
 \item If the size of the block header is larger than the maximally allowed size,
-  there is a \em{HeaderSizeTooLarge} failure.
+  there is a \emph{HeaderSizeTooLarge} failure.
 \item If the size of the block body is larger than the maximally allowed size,
-  there is a \em{BlockSizeTooLarge} failure.
+  there is a \emph{BlockSizeTooLarge} failure.
 \end{itemize}
 
 \clearpage
@@ -845,18 +845,18 @@ \subsection{Operational Certificate Transition}
 The OCERT rule has six predicate failures:
 \begin{itemize}
 \item If the KES period is less than the KES period start in the certificate,
-  there is a \em{KESBeforeStart} failure.
+  there is a \emph{KESBeforeStart} failure.
 \item If the KES period is greater than or equal to the KES period end (start +
-  90) in the certificate, there is a \em{KESAfterEnd} failure.
+  90) in the certificate, there is a \emph{KESAfterEnd} failure.
 \item If the period counter in the original key hash counter mapping is larger
-  than the period number in the certificate, there is a \em{KESPeriodWrong}
+  than the period number in the certificate, there is a \emph{KESPeriodWrong}
   failure.
 \item If the signature of the hot key, KES period number and period start is
-  incorrect, there is an \em{InvalidSignature} failure.
+  incorrect, there is an \emph{InvalidSignature} failure.
 \item I the KES signature using the hot key of the block header body is
-  incorrect, there is an \em{InvalideKesSignature} failure.
+  incorrect, there is an \emph{InvalideKesSignature} failure.
 \item If there is no entry in the key hash to counter mapping for the cold key,
-  there is a \em{NoCounterForKeyHash} failure.
+  there is a \emph{NoCounterForKeyHash} failure.
 \end{itemize}
 
 \subsection{Verifiable Random Function}
@@ -1049,15 +1049,15 @@ \subsection{Overlay Schedule}
 The OVERLAY rule has four predicate failures:
 \begin{itemize}
 \item In the case of the slot not being part of a OBFT schedule, if the VRF
-  leader check does not verify, there is a \em{NotPraosLeader} failure.
+  leader check does not verify, there is a \emph{NotPraosLeader} failure.
 \item In the case of the slot being in the OBFT schedule, but without genesis
-  key (i.e., $Nothing$), there is a \em{NotActiveSlot} failure.
+  key (i.e., $Nothing$), there is a \emph{NotActiveSlot} failure.
 \item In the case of the slot being in the OBFT schedule, if there is a
   specified key, but this key is not in the genesis delegation map, there is a
-  \em{NoGenesisStaking} failure.
+  \emph{NoGenesisStaking} failure.
 \item In the case of the slot being in the OBFT schedule, if there is a
   specified genesis key which is not the same key as in the bock header body,
-  there is a \em{NoGenesisColdKey} failure.
+  there is a \emph{NoGenesisColdKey} failure.
 \end{itemize}
 
 \clearpage
@@ -1181,9 +1181,9 @@ \subsection{Protocol Transition}
 The PRTCL rule has two predicate failures:
 \begin{itemize}
 \item If the slot of the block header body is not larger than the last slot or
-  greater than the current slot, there is a \em{WrongSlotInterval} failure.
+  greater than the current slot, there is a \emph{WrongSlotInterval} failure.
 \item If the hash of the previous header of the block header body is not equal
-  to the hash given in the environment, there is a \em{WrongBlockSequence}
+  to the hash given in the environment, there is a \emph{WrongBlockSequence}
   failure.
 \end{itemize}
 
@@ -1317,7 +1317,7 @@ \subsection{Block Body Transition}
 The BBODY rule has one predicate failure:
 \begin{itemize}
 \item if the size of the block body in the header is not equal to the real size
-  of the block body, there is a \em{WrongBlockBodySize} failure.
+  of the block body, there is a \emph{WrongBlockBodySize} failure.
 \end{itemize}
 
 \clearpage

shelley/chain-and-ledger/formal-spec/delegation.tex

@@ -329,7 +329,7 @@ \subsection{Delegation Rules}
     There is a precondition that the key has been registered.
     Delegation causes the following state transformation:
     \begin{itemize}
-      \item The delegation relation is updated so that stake stake key is delegated to the given
+      \item The delegation relation is updated so that stake key is delegated to the given
         stake pool. The use of union override here allows us to use the same rule
         to perform both an initial delegation and an update to an existing delegation.
     \end{itemize}
@@ -507,16 +507,16 @@ \subsection{Delegation Rules}
 The DELEG rule has five predicate failures:
 \begin{itemize}
 \item In the case of a key registration certificate, if the staking key is already
-  registered, there is a a \em{StakeKeyAlreadyRegistered} failure.
+  registered, there is a \emph{StakeKeyAlreadyRegistered} failure.
 \item In the case of a key deregistration certificate, if the key is not
-  registered, there is a \em{StakeKeyNotRegistered} failure.
+  registered, there is a \emph{StakeKeyNotRegistered} failure.
 \item In the case of a non-existing stake pool key in a delegation certificate,
-  there is a \em{StakeDelegationImpossible} failure.
+  there is a \emph{StakeDelegationImpossible} failure.
 \item In the case of a pool delegation certificate, there is a
-  \em{WrongCertificateType} failure.
+  \emph{WrongCertificateType} failure.
 \item  In the case of a genesis key delegation certificate, if the key is not
   in the domain of the genesis delegation mapping, there is a
-  \em{GenesisKeyNotInMapping} failure.
+  \emph{GenesisKeyNotInMapping} failure.
 \end{itemize}
 
 \clearpage
@@ -695,12 +695,12 @@ \subsection{Stake Pool Rules}
 \begin{itemize}
 \item In the case of a pool retirement certificate, if the pool key is not in
   the domain of the stake pools mapping, there is a
-  {\em StakePoolNotRegisteredOnKey} failure.
+  {\emph StakePoolNotRegisteredOnKey} failure.
 \item In the case of a pool retirement certificate, if the retirement epoch is
   not between the current epoch and the relative maximal epoch from the current
-  epoch, there is a {\em StakePoolRetirementWrongEpoch} failure.
+  epoch, there is a {\emph StakePoolRetirementWrongEpoch} failure.
 \item If the delegation certificate is not of one of the pool types, there is a
-  {\em WrongCertificateType} failure.
+  {\emph WrongCertificateType} failure.
 \end{itemize}
 
 \clearpage
@@ -1044,10 +1044,10 @@ \subsection{Delegation and Pool Combined Rules}
 The DELEGS rule has two predicate failures:
 \begin{itemize}
 \item In the case of a key delegation certificate, if the pool key is not
-  registered, there is a \em{DelegateeNotRegistered} failure.
+  registered, there is a \emph{DelegateeNotRegistered} failure.
 \item If the withdrawals mapping of the transaction is not a subset of the
   rewards mapping of the delegation state, there is a
-  \em{WithdrawalsNotInRewards} failure.
+  \emph{WithdrawalsNotInRewards} failure.
 \end{itemize}
 
 \clearpage

shelley/chain-and-ledger/formal-spec/update.tex

@@ -98,12 +98,12 @@ \section{Updates}
 \begin{itemize}
 \item In the case of \var{slot} being smaller than
   $\fun{firstSlot}~((\fun{epoch}~\var{slot}) + 1) - \fun{SlotsPrior}$, there is
-  a {\em PPUpdateTooEarly} failure.
+  a \emph{PPUpdateTooEarly} failure.
 \item In the case of \var{pup} being non-empty, if the check $\dom pup \subseteq
-  \dom dms$ fails, there is a {\em NonGenesisUpdate} failure as only genesis keys
+  \dom dms$ fails, there is a \emph{NonGenesisUpdate} failure as only genesis keys
   can be used in the protocol parameter update.
 \item If a protocol parameter update in \var{pup} cannot follow the current
-  protocol parameter, there is a {\em PVCannotFollow} failure.
+  protocol parameter, there is a \emph{PVCannotFollow} failure.
 \end{itemize}
 
 \clearpage
@@ -331,14 +331,14 @@ \section{Updates}
 The AVUP rule has three predicate failures:
 \begin{itemize}
 \item In the case of \var{aup} being non-empty, if the check $\dom aup \subseteq
-  \dom dms$ fails, there is a {\em NonGenesisUpdate} failure as only genesis keys
+  \dom dms$ fails, there is a \emph{NonGenesisUpdate} failure as only genesis keys
   can be used in the application version update.
 \item In the case of \var{aup} being non-empty, if any of the application names
-  in the proposal are invalid, there is a {\em InvalidName} failure.
+  in the proposal are invalid, there is a \emph{InvalidName} failure.
 \item In the case of \var{aup} being non-empty, if any of the application versions
   in the proposal are not exactly one more than the greatest version for the given
   application name in the current application versions or the future application
-  versions, there is a {\em CannotFollow} failure.
+  versions, there is a \emph{CannotFollow} failure.
 \end{itemize}
 
 \clearpage

shelley/chain-and-ledger/formal-spec/utxo.tex

@@ -357,15 +357,15 @@ \subsection{UTxO Transitions}
 
 The UTXO rule has five predicate failures:
 \begin{itemize}
-\item In the case of any input not being valid, there is a \em{BadInput} failure.
+\item In the case of any input not being valid, there is a \emph{BadInput} failure.
 \item In the case of the current slot being greater than the time-to-live of the
-  current transaction, there is an \em{Expired} failure.
-\item In the case of an empty input set, there is a \em{InputSetEmpty} failure,
+  current transaction, there is an \emph{Expired} failure.
+\item In the case of an empty input set, there is a \emph{InputSetEmpty} failure,
   in order to prevent replay attacks.
 \item If the fees are smaller than the minimal transaction fees, there is a
-  \em{FeeTooSmall} failure.
+  \emph{FeeTooSmall} failure.
 \item If the transaction does not correctly conserve the balance, there is a
-  \em{ValueNotConserved} failure.
+  \emph{ValueNotConserved} failure.
 \end{itemize}
 
 \clearpage
@@ -643,9 +643,9 @@ \subsection{Witnesses}
 
 The UTXOW rule has two predicate failures:
 \begin{itemize}                 %TODO: add multi-sig script failure predicates
-\item In the case of an incorrect witness, there is a \em{InvalidWitnesses}
+\item In the case of an incorrect witness, there is a \emph{InvalidWitnesses}
   failure.
-\item In the case of a missing witness, there is a \em{MissingVKeyWitnesses}
+\item In the case of a missing witness, there is a \emph{MissingVKeyWitnesses}
   failure.
 \end{itemize}