More of s/ap_table_t/apr_table_t/g;

Also s/ap_status_t/apr_status_t/;

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@89435 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/developer/debugging.html b/docs/manual/developer/debugging.html
index 4cc3b02e7da0fdbc5c5184653d6807ac8a4744bd..5643de71d4dd7178e2ba3ff02b0c9e45d225f28e 100644 (file)
--- a/docs/manual/developer/debugging.html
+++ b/docs/manual/developer/debugging.html
@@ -47,16 +47,16 @@ the modes available and gives instructions on activating them.</p>
 <h3>POOL_DEBUG</h3>
 <p><em>This is intended to detect cases where the wrong pool is used when assigning data to an object in another pool.</em></p>
 
-<p>In particular, it causes the table_{set,add,merge}n routines to check that their arguments are safe for the ap_table_t they're being placed in.  It currently only works with the unix multiprocess model, but could be extended to others.</p>
+<p>In particular, it causes the table_{set,add,merge}n routines to check that their arguments are safe for the apr_table_t they're being placed in.  It currently only works with the unix multiprocess model, but could be extended to others.</p>
 
 <h2>Table Debugging</h2>
 <h3>MAKE_TABLE_PROFILE</h3>
 <p><em>Provide diagnostic information about make_table() calls which are possibly too small.</em></p>
 
 <p>This requires a recent gcc which supports __builtin_return_address().  The error_log output will be a message such as: </p>
-<pre>table_push: ap_table_t created by 0x804d874 hit limit of 10</pre>
+<pre>table_push: apr_table_t created by 0x804d874 hit limit of 10</pre>
 <p>Use "<em><strong>l *0x804d874</strong></em>" to find the source that corresponds to.  It
- indicates that a ap_table_t allocated by a call at that address has possibly too small an initial ap_table_t size guess.</p>
+ indicates that a apr_table_t allocated by a call at that address has possibly too small an initial apr_table_t size guess.</p>
 
 <h2>Allocation Statistics</h2>
 <h3>ALLOC_STATS</h3>

diff --git a/docs/manual/developer/modules.html b/docs/manual/developer/modules.html
index 7d6c27c3d9ba8270efb26da0d116743b2efac842..d2d898f88ff034a33cdb6fec7943d317f0e41daf 100644 (file)
--- a/docs/manual/developer/modules.html
+++ b/docs/manual/developer/modules.html
@@ -26,7 +26,7 @@ This is a first attempt at writing the lessons I learned when trying to convert
 
 <h3>Cleanup Routines</h3>
 <p>
-These now need to be of type ap_status_t and return a value of that type.  Normally the return value will be APR_SUCCESS unless there is some need to signal an error in the cleanup.  Be aware that even though you signal an error not all code yet checks and acts upon the error.
+These now need to be of type apr_status_t and return a value of that type.  Normally the return value will be APR_SUCCESS unless there is some need to signal an error in the cleanup.  Be aware that even though you signal an error not all code yet checks and acts upon the error.
 </p>
 
 <h3>Initialisation Routines</h3>

diff --git a/docs/manual/developer/modules.html.en b/docs/manual/developer/modules.html.en
index 7d6c27c3d9ba8270efb26da0d116743b2efac842..d2d898f88ff034a33cdb6fec7943d317f0e41daf 100644 (file)
--- a/docs/manual/developer/modules.html.en
+++ b/docs/manual/developer/modules.html.en
@@ -26,7 +26,7 @@ This is a first attempt at writing the lessons I learned when trying to convert
 
 <h3>Cleanup Routines</h3>
 <p>
-These now need to be of type ap_status_t and return a value of that type.  Normally the return value will be APR_SUCCESS unless there is some need to signal an error in the cleanup.  Be aware that even though you signal an error not all code yet checks and acts upon the error.
+These now need to be of type apr_status_t and return a value of that type.  Normally the return value will be APR_SUCCESS unless there is some need to signal an error in the cleanup.  Be aware that even though you signal an error not all code yet checks and acts upon the error.
 </p>
 
 <h3>Initialisation Routines</h3>