From 631fbcc32090d22c1c36ffdfd1efb0c5a6e5ab97 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Pat=20M=C3=A4chler?= Date: Wed, 8 Nov 2017 10:48:55 +0100 Subject: [PATCH] fixing 2 typos --- docs/spec/08_referential_integrity.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/spec/08_referential_integrity.md b/docs/spec/08_referential_integrity.md index 97f4901b..01aa1942 100644 --- a/docs/spec/08_referential_integrity.md +++ b/docs/spec/08_referential_integrity.md @@ -56,7 +56,7 @@ necessary to maintain data integrity. `INSERT`/`INSERT_OR_REPLACE` * Same as in the `RESTRICT` mode. Note that for `insertOrReplace()` queries, - there is no cascading. If cascading is desrired an `update()` query should + there is no cascading. If cascading is desired an `update()` query should be used instead. `DELETE` @@ -81,7 +81,7 @@ When in `RESTRICT` constraint mode, constraints can be marked as `DEFERRABLE` or therefore `IMMEDIATE` will be used. Timing enforcement should be exposed via the schema creation API as an optional -enum parameter. The enum is named `lf.ConstraintTiming` The default value, if +enum parameter. The enum is named `lf.ConstraintTiming`. The default value, if such parameter is not provided, is `IMMEDIATE`. #### 8.3.1 DEFERRABLE