From e8898e9169c851c2b8c98f981c1c4755a5758f8e Mon Sep 17 00:00:00 2001
From: Andres Freund <andres@anarazel.de>
Date: Fri, 8 May 2015 18:00:01 +0200
Subject: Minor ON CONFLICT related comments and doc fixes.

Geoff Winkless, Stephen Frost, Peter Geoghegan and me.
---
 doc/src/sgml/ref/insert.sgml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'doc/src')

diff --git a/doc/src/sgml/ref/insert.sgml b/doc/src/sgml/ref/insert.sgml
index c88d1b7b50a..eff52cb1e0c 100644
--- a/doc/src/sgml/ref/insert.sgml
+++ b/doc/src/sgml/ref/insert.sgml
@@ -76,7 +76,7 @@ INSERT INTO <replaceable class="PARAMETER">table_name</replaceable> [ AS <replac
   <para>
    <literal>ON CONFLICT</> can be used to specify an alternative
    action to raising a unique constraint or exclusion constraint
-   violation error . (See <xref linkend="sql-on-conflict"
+   violation error. (See <xref linkend="sql-on-conflict"
    endterm="sql-on-conflict-title"> below.)
   </para>
 
@@ -397,7 +397,7 @@ INSERT INTO <replaceable class="PARAMETER">table_name</replaceable> [ AS <replac
    <emphasis>unique index inference</emphasis> clause or an explicitly
    named constraint can be used.  For <literal>ON CONFLICT DO
    NOTHING</literal>, it is optional to specify a
-   <parameter>conflict_target</parameter>; when ommitted, conflicts
+   <parameter>conflict_target</parameter>; when omitted, conflicts
    with all usable constraints (and unique indexes) are handled.  For
    <literal>ON CONFLICT DO UPDATE</literal>, a conflict target
    <emphasis>must</emphasis> be specified.
-- 
cgit v1.2.3