From 21cbbda634de8632ec382584c81da75bffb5bf53 Mon Sep 17 00:00:00 2001 From: Gavin Henry Date: Tue, 15 Jan 2008 20:58:44 +0000 Subject: [PATCH] Wee fix. More overlay and replication tomorrow night. --- doc/guide/admin/overlays.sdf | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/guide/admin/overlays.sdf b/doc/guide/admin/overlays.sdf index 99e4d0a866..665854a212 100644 --- a/doc/guide/admin/overlays.sdf +++ b/doc/guide/admin/overlays.sdf @@ -8,12 +8,12 @@ Overlays are software components that provide hooks to functions analogous to those provided by backends, which can be stacked on top of the backend calls and as callbacks on top of backend responses to alter their behavior. -Overlays may be compiled statically into slapd, or when module support +Overlays may be compiled statically into {{slapd}}, or when module support is enabled, they may be dynamically loaded. Most of the overlays are only allowed to be configured on individual databases, but some may also be configured globally. -Essentially they represent a means to: +Essentially, they represent a means to: * customize the behavior of existing backends without changing the backend code and without requiring one to write a new custom backend with @@ -26,9 +26,9 @@ the naming convention is > slapo- -Not all distributed overlays have a man page yet. Feel free to contribute one, -if you think you well understood the behavior of the component and the -implications of all the related configuration directives. +All distributed core overlays have a man page. Feel free to contribute to any, +if you think there is anything missing in describing the behavior of the component +and the implications of all the related configuration directives. Official overlays are located in -- 2.39.5