From 03649c6d6f4d4dd0c06d5ca96451757a55bafe4a Mon Sep 17 00:00:00 2001
From: John Wickerson <j.wickerson@imperial.ac.uk>
Date: Tue, 17 Nov 2020 20:44:25 +0000
Subject: Update on Overleaf.

---
 verilog.tex | 1 -
 1 file changed, 1 deletion(-)

(limited to 'verilog.tex')

diff --git a/verilog.tex b/verilog.tex
index afea449..355b91c 100644
--- a/verilog.tex
+++ b/verilog.tex
@@ -14,7 +14,6 @@ A module can contain multiple always blocks, all of which run in parallel.  Thes
 \NR{We should mention that variables cannot be driven by multiple \alwaysblock{}s, since one might get confused with data races when relating to concurrent processes in software.}
 
 
-
 As hardware designs normally describe events that will be executed periodically for an infinite amount of time, the top-level of the semantics is best described using small-step semantics, whereas the execution of one small step is described using big-step semantics. An example of a rule in the semantics for executing an always block is shown below, where $\Sigma$ is the state of the registers in the module and $s$ is the statement inside the always block:
 
 \begin{equation*}
-- 
cgit 

