From 7d1d22a712831ab2199e4a8e818aca4497e71130 Mon Sep 17 00:00:00 2001
From: Justin Pryzby <pryzbyj@telsasoft.com>
Date: Wed, 29 Dec 2021 16:43:08 -0600
Subject: [PATCH 29/33] v15 doc review: Some additional information about when
 to use referential actions - 5786fe154b53caef8b226ed863312d3608b32a51

---
 doc/src/sgml/ddl.sgml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml
index e507954c2d0..7cf0f0da3b2 100644
--- a/doc/src/sgml/ddl.sgml
+++ b/doc/src/sgml/ddl.sgml
@@ -1071,7 +1071,7 @@ CREATE TABLE order_items (
     represent independent objects, then <literal>RESTRICT</literal> or
     <literal>NO ACTION</literal> is more appropriate; an application that
     actually wants to delete both objects would then have to be explicit about
-    this and run two delete options.  In the above example, order items are
+    this and run two delete commands.  In the above example, order items are
     part of an order, and it is convenient if they are deleted automatically
     if an order is deleted.  But products and orders are different things, and
     so making a deletion of a product automatically cause the deletion of some
-- 
2.17.1

