From 06064b444ad745e4742c328dd5d64f9585a449f3 Mon Sep 17 00:00:00 2001
From: Jeff Hill <johill@lanl.gov>
Date: Thu, 22 May 2003 00:03:13 +0000
Subject: [PATCH] small clarification

---
 src/ca/CAref.html | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/src/ca/CAref.html b/src/ca/CAref.html
index af97f6378..6d78220b3 100644
--- a/src/ca/CAref.html
+++ b/src/ca/CAref.html
@@ -1921,10 +1921,10 @@ time.</p>
 
 <p>If ECA_TIMEOUT is returned then get requests may be reissued followed by a
 subsequent call to ca_pend_io().&nbsp;Specifically,&nbsp;the function will
-block&nbsp;only for outstanding outstanding <a href="#ca_get">ca_get</a>
-requests issued, and also any channels created specifying a nill connection
-handler function pointer, after the last call to ca_pend_io() or ca client
-context creation whichever is later. Note that <a
+block&nbsp;only for outstanding <a href="#ca_get">ca_get</a> requests issued,
+and also any channels created specifying a nill connection handler function
+pointer, after the last call to ca_pend_io() or ca client context creation
+whichever is later. Note that <a
 href="#ca_create_channel">ca_create_channel</a> requests generally should not
 be reissued for the same process variable unless <a
 href="#ca_clear_channel">ca_clear_channel</a> is called first.</p>
@@ -2008,6 +2008,9 @@ unlike <code><a href="#ca_pend_io">ca_pend_io</a></code> it does <em>not
 </em>indicate anything about the status of pending IO requests when it
 returns ECA_NORMAL.</p>
 
+<p>See also <a href="#Thread">Thread Safety and Preemptive Callback to User
+Code</a>.</p>
+
 <h4>Arguments</h4>
 <dl>
   <dt><code>TIMEOUT</code></dt>