Fix broken markup.

This commit is contained in:
Tom Lane 2007-02-01 22:06:14 +00:00
parent f7e5ecb026
commit dc4c26c37e

View file

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/sources.sgml,v 2.26 2007/02/01 21:28:34 momjian Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/sources.sgml,v 2.27 2007/02/01 22:06:14 tgl Exp $ -->
<chapter id="source">
<title>PostgreSQL Coding Conventions</title>
@ -22,10 +22,10 @@
<para>
The <filename>src/tools</filename> directory contains sample settings
files that can be used with the <productname>emacs</productname>,
<productname>xemacs</productname> or <productname>vim</productname>
editors to help ensure that they format code according to these
conventions.
files that can be used with the <productname>emacs</productname>,
<productname>xemacs</productname> or <productname>vim</productname>
editors to help ensure that they format code according to these
conventions.
</para>
<para>
@ -606,17 +606,13 @@ BETTER: unrecognized node type: 42
</formalpara>
<formalpara>
<title>May/Can/Might</title>
<title>May vs. Can vs. Might</title>
<para>
<quote>May</quote> suggests permission (e.g. "You may borrow my rake.")
<quote>May</quote> suggests permission (e.g. "You may borrow my rake."),
and has little use in documentation or error messages.
<quote>Can</quote> suggests ability (e.g. "I can lift that log."),
and <quote>might</quote> suggests possibility (e.g. "It might rain
today.").
</para>
<para>
Rationale: Using the proper word clarifies meaning and assists
today."). Using the proper word clarifies meaning and assists
translation.
</para>
</formalpara>