--- a/doc/interpreter/expr.txi	Thu Oct 16 17:07:02 2008 -0400
+++ b/doc/interpreter/expr.txi	Fri Oct 17 05:48:24 2008 +0100
@@ -187,8 +187,6 @@
 particularly for large matrices because Octave does not have to
 repeatedly resize the result.
 
-@DOCSTRING(subsref)
-
 @DOCSTRING(sub2ind)
 
 @DOCSTRING(ind2sub)
@@ -1010,8 +1008,6 @@
 programs hard to read.  Except in a one-shot program, you should rewrite
 it to get rid of such nesting of assignments.  This is never very hard.
 
-@DOCSTRING(subsasgn)
-
 @cindex increment operator
 @cindex decrement operator
 @cindex operators, increment

--- a/doc/interpreter/func.txi	Thu Oct 16 17:07:02 2008 -0400
+++ b/doc/interpreter/func.txi	Fri Oct 17 05:48:24 2008 +0100
@@ -881,13 +881,13 @@
 @ref{Object Oriented Programming}.
 
 @item Legacy Dispatch
-An overloaded function as defined by @xref{dispatch}.
+An overloaded function as defined by @xref{doc-dispatch}.
 
 @item Command-line Function
 A function that has been defined on the command-line.
 
 @item Autoload function
-A function that is marked as autoloaded with @xref{autoload}.
+A function that is marked as autoloaded with @xref{doc-autoload}.
 
 @item A Function on the Path
 A function that can be found on the users load-path. There can also be

--- a/doc/interpreter/oop.txi	Thu Oct 16 17:07:02 2008 -0400
+++ b/doc/interpreter/oop.txi	Fri Oct 17 05:48:24 2008 +0100
@@ -265,7 +265,7 @@
 @DOCSTRING(subsref)
 
 For example we might decide that indexing with "()" evaluates the
-polynomial and indexing with "{}" returns the @var{n}-th coefficient.
+polynomial and indexing with "@{@}" returns the @var{n}-th coefficient.
 In this case the @code{subsref} method of our polynomial class might look like
 
 @polynomialfile{subsref.m}