Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iSl5L-0007hV-3e for pgsql-docs@arkaria.postgresql.org; Thu, 07 Nov 2019 16:56:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iSl5I-0007wF-13 for pgsql-docs@arkaria.postgresql.org; Thu, 07 Nov 2019 16:56:36 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iSl5H-0007w8-Mv for pgsql-docs@lists.postgresql.org; Thu, 07 Nov 2019 16:56:35 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1iSl5E-0005XL-Up for pgsql-docs@lists.postgresql.org; Thu, 07 Nov 2019 16:56:34 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id xA7GuV0r012943; Thu, 7 Nov 2019 11:56:32 -0500 From: Tom Lane To: Tatsuo Ishii cc: pgsql-docs@lists.postgresql.org Subject: Re: Small typo in func.sgml In-reply-to: <20191107.081615.575915718972561860.t-ishii@sraoss.co.jp> References: <20191107.081615.575915718972561860.t-ishii@sraoss.co.jp> Comments: In-reply-to Tatsuo Ishii message dated "Thu, 07 Nov 2019 08:16:15 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <12941.1573145791.1@sss.pgh.pa.us> Date: Thu, 07 Nov 2019 11:56:31 -0500 Message-ID: <12942.1573145791@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Tatsuo Ishii writes: > I thinkk a new line is needed after . > - JSON query functions and operators > + > + JSON query functions and operators It doesn't really make any difference, I believe. I agree it's neater with the newline, but I wouldn't bother changing it unless you're making some other nearby change. (There are actually instances of this in quite a few places in our docs, if memory serves. I think somebody uses, or used, an editor that tended to remove newlines in that context.) regards, tom lane