From 02f0615a77811eb205c070e89330104c3f9fb635 Mon Sep 17 00:00:00 2001
From: jonahbeckford <71855677+jonahbeckford@users.noreply.github.com>
Date: Tue, 31 May 2022 13:22:13 -0700
Subject: [PATCH] Update lg_08_error_handling.md

Switch from `lazy_t` to `Lazy.t`

Guidance at https://v2.ocaml.org/api/Lazy.html says:

> Note: lazy_t is the built-in type constructor used by the compiler for the lazy keyword. You should not use it directly. Always use Lazy.t instead.
---
 data/tutorials/lg_08_error_handling.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/data/tutorials/lg_08_error_handling.md b/data/tutorials/lg_08_error_handling.md
index 79c1d91542..e480ab053f 100644
--- a/data/tutorials/lg_08_error_handling.md
+++ b/data/tutorials/lg_08_error_handling.md
@@ -151,7 +151,7 @@ are:
 
 - `exn`, in which case the result type just makes exceptions explicit.
 - `string`, where the error case is a message that indicates what failed.
-- `string lazy_t`, a more elaborate form of error message that is only evaluated
+- `string Lazy.t`, a more elaborate form of error message that is only evaluated
   if printing is required.
 - some polymorphic variant, with one case per
   possible error. This is very accurate (each error can be dealt with