3 files changed, 5 insertions, 5 deletions
diff --git a/doc/artsbuilder/faq.docbook b/doc/artsbuilder/faq.docbook
index 8bb7ae4c..65a14c87 100644
--- a/doc/artsbuilder/faq.docbook
+++ b/doc/artsbuilder/faq.docbook
@@ -414,7 +414,7 @@ Short answer: no, &arts; will not work if you compile it with gcc-3.0.
 <para>
 Long answer: In the official release, there are two gcc-3.0 bugs which affect
 &arts;. The first, gcc-3.0 bug c++/2733 is relatively harmless (and has to do
-with problems with the asm statement). It breaks compilation of convert.cc. It
+with problems with the asm statement). It breaks compilation of convert.cpp. It
 has been fixed in the gcc-3.0 CVS, and will no longer be a problem with
 gcc-3.0.1 and higher. A workaround has also been added to the CVS version
 of KDE/aRts.
@@ -1018,7 +1018,7 @@ succeeds, which eventually leads to consuming all CPU power and reporting
 might get supplied with wrong information how much to write. Artsd will then
 <emphasis>stop with an assertion</emphasis> like:
 <screen>
-artsd: audiosubsys.cc:458: void Arts::AudioSubSystem::handleIO(int):
+artsd: audiosubsys.cpp:458: void Arts::AudioSubSystem::handleIO(int):
 Assertion `len == can_write' failed.
 Aborted
 </screen>
diff --git a/doc/artsbuilder/helping.docbook b/doc/artsbuilder/helping.docbook
index 72b2ff2b..dc635701 100644
--- a/doc/artsbuilder/helping.docbook
+++ b/doc/artsbuilder/helping.docbook
@@ -224,7 +224,7 @@ written.
 <para>
 Source files should have no capitalization in the name. They should have
 the name of the class when they implement a single class. Their
-extension is <literal role="extension">.cc</literal> if they refer to
+extension is <literal role="extension">.cpp</literal> if they refer to
 &Qt;/&GUI; independent code, and <literal
 role="extension">.cpp</literal> if they refer to &Qt;/&GUI; dependant
 code. Implementation files for interfaces should be called
diff --git a/doc/artsbuilder/mcop.docbook b/doc/artsbuilder/mcop.docbook
index f140bff9..59d9a011 100644
--- a/doc/artsbuilder/mcop.docbook
+++ b/doc/artsbuilder/mcop.docbook
@@ -1093,7 +1093,7 @@ interface Hello {
 You pass that through the &IDL; compiler by calling
 <userinput><command>mcopidl</command>
 <parameter>hello.idl</parameter></userinput>, which will in turn generate
-<filename>hello.cc</filename> and <filename>hello.h</filename>.  To
+<filename>hello.cpp</filename> and <filename>hello.h</filename>.  To
 implement it, you need to define a C++-class that inherits the skeleton:
 </para>
 
@@ -1991,7 +1991,7 @@ objects</quote> and <quote>the <acronym>CORBA</acronym>
 interface</quote> look natural, but it didn't, because
 <acronym>CORBA</acronym> knew nothing at all about streams. &MCOP;
 does. Look at the code (something like
-<filename>simplesoundserver_impl.cc</filename>). Way better!  Streams
+<filename>simplesoundserver_impl.cpp</filename>). Way better!  Streams
 can be declared in the interface of modules, and implemented in a
 natural looking way.
 </para>