Thread: pgsql: Doc wording improvment.

pgsql: Doc wording improvment.

From
momjian@postgresql.org (Bruce Momjian)
Date:
Log Message:
-----------
Doc wording improvment.

Modified Files:
--------------
    pgsql/doc/src/sgml:
        runtime.sgml (r1.398 -> r1.399)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/runtime.sgml?r1=1.398&r2=1.399)

Re: pgsql: Doc wording improvment.

From
Tom Lane
Date:
momjian@postgresql.org (Bruce Momjian) writes:
> Doc wording improvment.

-   <filename>postgresql.conf</>.  It is possible to allow authentication
+   <filename>postgresql    .conf</>.  It is possible to have authentication

How is inserting an incorrect space into a filename a "wording
improvement"?

Subsequent commits in this area seem to have changed the surrounding
sentence but not fixed this pretty-fundamental bogosity.

            regards, tom lane

Re: pgsql: Doc wording improvment.

From
Bruce Momjian
Date:
Tom Lane wrote:
> momjian@postgresql.org (Bruce Momjian) writes:
> > Doc wording improvment.
>
> -   <filename>postgresql.conf</>.  It is possible to allow authentication
> +   <filename>postgresql    .conf</>.  It is possible to have authentication
>
> How is inserting an incorrect space into a filename a "wording
> improvement"?

I have no idea how that change got in there.  The change I thought I was
making was to change "overhead of encryption" to "encryption overhead".

> Subsequent commits in this area seem to have changed the surrounding
> sentence but not fixed this pretty-fundamental bogosity.

Anyway, I fixed it in CVS.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://postgres.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +