content/blog/01_types_basics.md

@@ -428,7 +428,6 @@ and already be up-to-speed on a big chunk of the content.
 {{< /block >}}
 
 #### Rules
-{{< foldtable >}}
 | Rule         | Description |
 |--------------|-------------|
 | {{< latex >}}s : \text{string} {{< /latex >}}| String literals have type \\(\\text{string}\\) |

content/blog/10_compiler_polymorphism.md

@@ -58,13 +58,12 @@ __generalization__ and __instantiation__. It's been quite a while since the last
 to present a table with these new rules, as well as all of the ones that we
 {{< sidenote "right" "rules-note" "previously used." >}}
 The rules aren't quite the same as the ones we used earlier;
-note that \(\sigma\) is used in place of \(\tau\) in the first rule,
+note that \\(\sigma\\) is used in place of \\(\tau\\) in the first rule,
 for instance. These changes are slight, and we'll talk about how the
 rules work together below.
 {{< /sidenote >}} I will also give a quick
 summary of each of these rules.
 
-{{< foldtable >}}
 Rule|Name and Description
 -----|-------
 {{< latex >}}

content/blog/coq_dawn.md

@@ -219,7 +219,6 @@ Here, we may as well go through the three constructors to explain what they mean
 Now it's time for some fun! The UCC language specification starts by defining two values:
 true and false. Why don't we do the same thing?
 
-{{< foldtable >}}
 |UCC Spec| Coq encoding |
 |---|----|
 |\\(\\text{false}\\)=\\([\\text{drop}]\\)| {{< codelines "Coq" "dawn/Dawn.v" 41 42 >}}
@@ -258,7 +257,6 @@ element, as specified. The proof for \\(\\text{true}\\) is very similar in spiri
 
 We can also formalize the \\(\\text{or}\\) operator:
 
-{{< foldtable >}}
 |UCC Spec| Coq encoding |
 |---|----|
 |\\(\\text{or}\\)=\\(\\text{clone}\\ \\text{apply}\\)| {{< codelines "Coq" "dawn/Dawn.v" 65 65 >}}

themes/vanilla

@@ -1 +1 @@
-Subproject commit 869f9d12c84ebf38fe8f21611af9d3bf7ff5ea0d
+Subproject commit c5a28bf7ef0ea0ec4f534cf2bff231d1ad43bcea