Delta-sync Mirror/MMR is now supported

diff --git a/doc/guide/admin/replication.sdf b/doc/guide/admin/replication.sdf
index adcf276cd8efe57be612025e2281f257c17f7692..4a499d655d122f8366485cdadee265ec50a60819 100644 (file)
--- a/doc/guide/admin/replication.sdf
+++ b/doc/guide/admin/replication.sdf
@@ -426,7 +426,6 @@ is needed to manage which provider is currently active
 - If backing up the Berkeley database itself and periodically backing up the 
 transaction log files, then the same member of the mirror pair needs to be 
 used to collect logfiles until the next database backup is taken 
-* Delta-Syncrepl is not yet supported
 
 For configuration, please see the {{SECT:MirrorMode}} section below
 
@@ -867,8 +866,6 @@ H4: Mirror Node Configuration
 The first step is to configure the syncrepl provider the same as in the 
 {{SECT:Set up the provider slapd}} section.
 
-Note: Delta-syncrepl is not yet supported with MirrorMode.
-
 Here's a specific cut down example using {{SECT:LDAP Sync Replication}} in
 {{refreshAndPersist}} mode:
 

diff --git a/doc/guide/admin/tuning.sdf b/doc/guide/admin/tuning.sdf
index 39fc6a4b5d34b928e4ee4482b574e60cff327c3d..0890c3b13f209c2ac21959fe28b36dd0b245a759 100644 (file)
--- a/doc/guide/admin/tuning.sdf
+++ b/doc/guide/admin/tuning.sdf
@@ -324,7 +324,7 @@ it is generally recommended to be 3x"cachesize".
 
 H2: {{slapd}}(8) Threads
 
-{{slapd}}(8) can process requests via a configurable number of threads, which 
+{{slapd}}(8) can process requests via a configurable number of threads, which
 in turn affects the in/out rate of connections.
 
 This value should generally be a function of the number of "real" cores on