From 5e605c7a6ee2e1c71a3d10f3f8e7282724c9551e Mon Sep 17 00:00:00 2001
From: ac27182 <42341528+ac27182@users.noreply.github.com>
Date: Tue, 25 Feb 2020 21:50:15 +0000
Subject: [PATCH] Update simple-algebraic-data-types.tex (#244)

turning record in to a new term
---
 src/content/1.6/simple-algebraic-data-types.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/content/1.6/simple-algebraic-data-types.tex b/src/content/1.6/simple-algebraic-data-types.tex
index c2b85c87..4dc6e5e4 100644
--- a/src/content/1.6/simple-algebraic-data-types.tex
+++ b/src/content/1.6/simple-algebraic-data-types.tex
@@ -133,7 +133,7 @@ \section{Product Types}
 Programming with tuples and multi-argument constructors can get messy
 and error prone --- keeping track of which component represents what.
 It's often preferable to give names to components. A product type with
-named fields is called a record in Haskell, and a \code{struct} in C.
+named fields is called a \newterm{record} in Haskell, and a \code{struct} in C.
 
 \section{Records}