summaryrefslogtreecommitdiff
path: root/docs/porting/modscope.html
diff options
context:
space:
mode:
authorLorry Tar Creator <lorry-tar-importer@baserock.org>2015-02-17 17:25:57 +0000
committer <>2015-03-17 16:26:24 +0000
commit780b92ada9afcf1d58085a83a0b9e6bc982203d1 (patch)
tree598f8b9fa431b228d29897e798de4ac0c1d3d970 /docs/porting/modscope.html
parent7a2660ba9cc2dc03a69ddfcfd95369395cc87444 (diff)
downloadberkeleydb-master.tar.gz
Imported from /home/lorry/working-area/delta_berkeleydb/db-6.1.23.tar.gz.HEADdb-6.1.23master
Diffstat (limited to 'docs/porting/modscope.html')
-rw-r--r--docs/porting/modscope.html6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/porting/modscope.html b/docs/porting/modscope.html
index 5161687b..f83fccaf 100644
--- a/docs/porting/modscope.html
+++ b/docs/porting/modscope.html
@@ -14,7 +14,7 @@
<body>
<div xmlns="" class="navheader">
<div class="libver">
- <p>Library Version 11.2.5.3</p>
+ <p>Library Version 12.1.6.1</p>
</div>
<table width="100%" summary="Navigation header">
<tr>
@@ -625,7 +625,7 @@ You need to determine how your target platfrom handles these functions:
<p>
When the target platform does <span class="emphasis"><em>not</em></span> have a POSIX
function required by Berkeley DB, no action is required on your
- part. When Berekely DB cannot find one of these functions on the
+ part. When Berkeley DB cannot find one of these functions on the
target platform, it automatically uses the replacement functions
supplied in the <code class="literal">clib</code> directory of the Berkeley
DB distribution. For example, if the target platform does not have
@@ -636,7 +636,7 @@ You need to determine how your target platfrom handles these functions:
</li>
<li>
<p>
-When the target platform has a function required by Berekely DB, but that
+When the target platform has a function required by Berkeley DB, but that
function operates in a non-standard compliant way, you can code to the
replacement functions supplied in the <code class="literal">clib</code> directory.
</p>