# HG changeset patch
# User Rik <rik@octave.org>
# Date 1371780895 25200
# Node ID acd6a21259a95868ff5e9b7464eea4ed54c13ef3
# Parent  d21bf69e49b2afbe9dba7132b990377bc8e61c1d
doc: Use the serial comma in Contributors chapter.

* doc/interpreter/contrib.txi: Use the serial comma.

diff -r d21bf69e49b2 -r acd6a21259a9 doc/interpreter/contrib.txi
--- a/doc/interpreter/contrib.txi	Thu Jun 20 18:12:17 2013 -0700
+++ b/doc/interpreter/contrib.txi	Thu Jun 20 19:14:55 2013 -0700
@@ -41,7 +41,7 @@
 development of Octave core, i.e., code that goes to Octave directly.
 You may consider developing and publishing a package instead; a great
 place for this is the allied Octave-Forge project
-(@url{http://octave.sourceforge.net}).  Note that the Octave project is
+(@url{http://octave.sourceforge.net}).  Note that the Octave core project is
 inherently more conservative and follows narrower rules.
 
 @node Building the Development Sources
@@ -364,7 +364,7 @@
 @node Other Sources
 @section Other Sources
 Apart from C++ and Octave language (m-files), Octave's sources include
-files written in C, Fortran, M4, Perl, Unix shell, AWK, Texinfo and
+files written in C, Fortran, M4, Perl, Unix shell, AWK, Texinfo, and
 @TeX{}.  There are not many rules to follow when using these other
 languages; some of them are summarized below.  In any case, the golden
 rule is: if you modify a source file, try to follow any conventions you