From bbc435595e1cdfd73b878c10d3a264a1c97ebf5e Mon Sep 17 00:00:00 2001
From: Eric Schulte <schulte.eric@gmail.com>
Date: Sat, 8 Jun 2013 12:30:26 -0600
Subject: [PATCH] fix errors building the documentation

---
 doc/org.texi | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/doc/org.texi b/doc/org.texi
index 2297202e7..a042df612 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -13776,10 +13776,10 @@ code originated.
 
 The @code{org-babel-tangle-jump-to-org} function provides this jumping from
 code to Org-mode functionality.  Two header arguments are required for
-jumping to work, first the @xref{padline} option must be set to true (the
-default setting), second the @xref{comments} header argument must be set to
-@code{links}, which will insert comments into the source code buffer which
-point back to the original Org-mode file.
+jumping to work, first the @code{padline} (@ref{padline}) option must be set
+to true (the default setting), second the @code{comments} (@ref{comments})
+header argument must be set to @code{links}, which will insert comments into
+the source code buffer which point back to the original Org-mode file.
 
 @node Evaluating code blocks, Library of Babel, Extracting source code, Working With Source Code
 @section Evaluating code blocks
@@ -15079,11 +15079,11 @@ The @code{tangle-mode} header argument controls the permission set on tangled
 files.  The value of this header argument will be passed to
 @code{set-file-modes}.  For example, to set a tangled file as read only use
 @code{:tangle-mode #o444}, or to set a tangled file as executable use
-@code{:tangle-mode #o755}.  Files with @ref{shebang} header arguments will
-automatically be made executable unless the @code{tangle-mode} header
-argument is also used.  The behavior is undefined if multiple code blocks
-with different values for the @code{tangle-mode} header argument are tangled
-to the same file.
+@code{:tangle-mode #o755}.  Blocks with @code{shebang} (@ref{shebang}) header
+arguments will automatically be made executable unless the @code{tangle-mode}
+header argument is also used.  The behavior is undefined if multiple code
+blocks with different values for the @code{tangle-mode} header argument are
+tangled to the same file.
 
 @node eval, wrap, tangle-mode, Specific header arguments
 @subsubsection @code{:eval}