From 26c5d15f74f101ed49363513d48140cba9f648d5 Mon Sep 17 00:00:00 2001
From: Steve Martin <62676717+marberts@users.noreply.github.com>
Date: Thu, 12 Jun 2025 23:50:49 -0400
Subject: [PATCH] Fixed typo in Conditions.Rmd

---
 Conditions.Rmd | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Conditions.Rmd b/Conditions.Rmd
index cfb3346bf..3b5f833d5 100644
--- a/Conditions.Rmd
+++ b/Conditions.Rmd
@@ -713,7 +713,7 @@ This is an improvement for interactive usage as the error messages are more like
 ### Signalling
 \index{conditions!signalling}
 
-Let's build some infrastructure to improve this situation, We'll start by providing a custom `abort()` function for bad arguments. This is a little over-generalised for the example at hand, but it reflects common patterns that I've seen across other functions. The pattern is fairly simple. We create a nice error message for the user, using `glue::glue()`, and store metadata in the condition call for the developer. 
+Let's build some infrastructure to improve this situation. We'll start by providing a custom `abort()` function for bad arguments. This is a little over-generalised for the example at hand, but it reflects common patterns that I've seen across other functions. The pattern is fairly simple. We create a nice error message for the user, using `glue::glue()`, and store metadata in the condition call for the developer. 
 
 ```{r}
 abort_bad_argument <- function(arg, must, not = NULL) {