Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 9AE32B5DCE2 for ; Fri, 29 Jul 2011 11:47:55 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 80631-01-2 for ; Fri, 29 Jul 2011 14:47:49 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.216.181]) by mail.postgresql.org (Postfix) with ESMTP id 765D1B5F7C6 for ; Fri, 29 Jul 2011 11:45:01 -0300 (ADT) Received: by qyk9 with SMTP id 9so2177714qyk.19 for ; Fri, 29 Jul 2011 07:45:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.85.134 with SMTP id o6mr967050qcl.238.1311950701261; Fri, 29 Jul 2011 07:45:01 -0700 (PDT) Received: by 10.229.236.136 with HTTP; Fri, 29 Jul 2011 07:45:01 -0700 (PDT) In-Reply-To: <1311950209-sup-9538@alvh.no-ip.org> References: <4E325671.8070602@archidevsys.co.nz> <24447.1311948196@sss.pgh.pa.us> <1311950209-sup-9538@alvh.no-ip.org> Date: Fri, 29 Jul 2011 15:45:01 +0100 Message-ID: Subject: Re: postgres-9.1beta3 typo: recommendable --> recommended From: Dave Page To: Alvaro Herrera Cc: Tom Lane , Gavin Flower , Pg Docs Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-5 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201107/21 X-Sequence-Number: 6888 On Fri, Jul 29, 2011 at 3:41 PM, Alvaro Herrera wrote: > Excerpts from Dave Page's message of vie jul 29 10:13:50 -0400 2011: >> On Fri, Jul 29, 2011 at 3:03 PM, Tom Lane wrote: >> > Gavin Flower writes: >> >> /postgres-9.1/share/doc/html/manage-ag-overview.html >> >> In the folowing partagrasoh 'recommendable' should be 'recommended'. >> > >> > Seems perfectly ok as-is to me ... >> >> Sounds hideous to me. I ran it past one of our tech writers (Susan >> Douglas), who rewrote the sentence as: >> >> If a single PostgreSQL server instance is to house projects or users >> that should be separate (for the most part unaware of each other), we >> recommend storing them in separate databases. > > Except that we don't use the first person in docs, do we? That's easily changed. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company