From 3ed249b74133bc567a4efcfb90eb69d445097c1b Mon Sep 17 00:00:00 2001 From: Heikki Linnakangas Date: Mon, 24 Mar 2014 08:42:13 +0200 Subject: Fix "the the" typos. Erik Rijkers --- doc/src/sgml/json.sgml | 2 +- doc/src/sgml/logicaldecoding.sgml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/json.sgml b/doc/src/sgml/json.sgml index 3068cf2d1ee..5fd24397429 100644 --- a/doc/src/sgml/json.sgml +++ b/doc/src/sgml/json.sgml @@ -24,7 +24,7 @@ There are two JSON data types: json and jsonb. Both accept almost identical sets of values as input. The major practical difference is one of efficiency. The - json data type stores an exact copy of the the input text, + json data type stores an exact copy of the input text, which processing functions must continually reparse, while jsonb data is stored in a decomposed binary format that makes it slightly less efficient to input due to added serialization diff --git a/doc/src/sgml/logicaldecoding.sgml b/doc/src/sgml/logicaldecoding.sgml index 00c47cb3132..965b0e11184 100644 --- a/doc/src/sgml/logicaldecoding.sgml +++ b/doc/src/sgml/logicaldecoding.sgml @@ -169,7 +169,7 @@ CTRL-C Logical Decoding - Logical decoding is the the process of extracting all persistent changes + Logical decoding is the process of extracting all persistent changes to a database's tables into a coherent, easy to understand format which can be interpreted without detailed knowledge of the database's internal state. -- cgit v1.2.3