Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
> > On 2015-08-25 20:37:43 +0000, barnettluisa@gmail.com wrote:
> >> "Possibly, your site administrator has already created a database for your
> >> use. He should have told you what the name of your database is. In that case
> >> you can omit this step and skip ahead to the next section."
>
> > Maybe: "Possibly, your site administrator has already created a database
> > for your use, in which case you should already have been told what the
> > name of your database. ..."?
>
> The hard part of getting rid of "he" is to not make the text harder to
> read (you failed at that) or be distracting about it. We're trying to
> write technical documentation, not to be politically correct. (Being
> PC is fine, mind you, I just don't want to be in-your-face about it.)
This is what I suggested:
"Possibly, your site administrators have already created a database for
your use. They should have told you what the name of your database is.
In that case you can omit this step and skip ahead to the next
section."
> I don't mean to dismiss the idea, but I think fixing this without doing
> damage to other worthy goals is going to be a lot harder than just
> "s/he/he or she/g".
Agreed.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
