--- a/doc/interpreter/dynamic.txi
+++ b/doc/interpreter/dynamic.txi
@@ -99,7 +99,7 @@
 
 @DOCSTRING(mkoctfile)
 
-Consider the short example:
+Consider the short C++ example:
 
 @example
 @group
@@ -108,10 +108,13 @@
 @end example
 
 This example although short introduces the basics of writing a C++
-function that can be dynamically linked to Octave.  The easiest way to
-make available most of the definitions that might be necessary for an
-oct-file in Octave is to use the @code{#include <octave/oct.h>}
-header.
+function that can be dynamically linked to Octave. The easiest way to
+make available most of the definitions that might be necessary for a C++
+oct-file in Octave is to use the @code{#include <octave/oct.h>} header.
+Note that @file{octave/oct.h} is a C++ header and cannot be directly
+@code{#include}'ed in a C source file, nor any other language. What
+follows is mostly C++, with a discussion of other languages in section
+@ref{Calling External Code from Oct-Files}.
 
 The macro that defines the entry point into the dynamically loaded
 function is @w{@code{DEFUN_DLD}}.  This macro takes four arguments, these being