Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 85ecedf

Browse files
committed
Fix typos.
Robert Treat
1 parent e185618 commit 85ecedf

File tree

2 files changed

+7
-7
lines changed

2 files changed

+7
-7
lines changed

doc/FAQ_DEV

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11

22
Developer's Frequently Asked Questions (FAQ) for PostgreSQL
33

4-
Last updated: Fri Mar 11 06:43:43 EST 2005
4+
Last updated: Fri Mar 11 06:58:51 EST 2005
55

66
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
77

doc/src/FAQ/FAQ_DEV.html

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@
1313
<H1>Developer's Frequently Asked Questions (FAQ) for
1414
PostgreSQL</H1>
1515

16-
<P>Last updated: Fri Mar 11 06:42:00 EST 2005</P>
16+
<P>Last updated: Fri Mar 11 06:58:51 EST 2005</P>
1717

1818
<P>Current maintainer: Bruce Momjian (<A href=
1919
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR>
@@ -199,7 +199,7 @@ <H3><A name="1.8">1.8</A>) How do I test my changes?</H3>
199199
<P><B>Basic system testing</B></P>
200200

201201
<P>The easiest way to test your code is to ensure that it builds
202-
against the latest verion of the code and that it does not generate
202+
against the latest version of the code and that it does not generate
203203
compiler warnings.</P>
204204

205205
<P>It is worth advised that you pass --enable-cassert to
@@ -217,7 +217,7 @@ <H3><A name="1.8">1.8</A>) How do I test my changes?</H3>
217217
directory of the source tree. If any tests failure,
218218
investigate.</P>
219219

220-
<P>If you've deliberately changed existing behaviour, this change
220+
<P>If you've deliberately changed existing behavior, this change
221221
may cause a regression test failure but not any actual regression.
222222
If so, you should also patch the regression test suite.</P>
223223

@@ -479,7 +479,7 @@ <H3><A name="1.14">1.14</A>) How are RPMs packaged?</H3>
479479

480480
<LI>The initscript;</LI>
481481

482-
<LI>Any other ancilliary scripts and files;</LI>
482+
<LI>Any other ancillary scripts and files;</LI>
483483

484484
<LI>A README.rpm-dist document that tries to adequately document
485485
both the differences between the RPM build and the WHY of the
@@ -608,7 +608,7 @@ <H3><A name="1.15">1.15</A>) How are CVS branches managed?</H3>
608608
cvs ... checkout pgsql
609609
</PRE>
610610

611-
<P>To get a past branch, you cd to whereever you want it and
611+
<P>To get a past branch, you cd to wherever you want it and
612612
say</P>
613613
<PRE>
614614
cvs ... checkout -r BRANCHNAME pgsql
@@ -697,7 +697,7 @@ <H3><A name="1.18">1.18</A>) How go I get involved in PostgreSQL
697697
the source code is available at <A href=
698698
"http://gborg.postgresql.org/project/pgweb/projdisplay.php">http://gborg.postgresql.org/project/pgweb/projdisplay.php</A>
699699
, the code for the next version of the website is under the
700-
"portal" module. You will al so find code for the "techdocs"
700+
"portal" module. You will also find code for the "techdocs"
701701
website if you would like to contribute to that. A temporary todo
702702
list for current website development issues is available at <A
703703
href=

0 commit comments

Comments
 (0)