From: Kurt Zeilenga <kurt@openldap.org>
Date: Fri, 19 Jan 2001 18:58:00 +0000 (+0000)
Subject: Minor clean up of unpublished section.
X-Git-Tag: LDBM_PRE_GIANT_RWLOCK~1552
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=a728b2c073c7de84e54fc9ca2e14810d9c1d7940;p=openldap

Minor clean up of unpublished section.
---

diff --git a/doc/guide/admin/schema.sdf b/doc/guide/admin/schema.sdf
index 0be8ee628d..5927c5ee4e 100644
--- a/doc/guide/admin/schema.sdf
+++ b/doc/guide/admin/schema.sdf
@@ -395,10 +395,10 @@ any LDAPv3 server and easily construct directives for use with
 
 LDAPv3 servers publish schema elements in special {{subschema}}
 entries (or subentries).  {{slapd}}(8) publishes a single subschema
-entry normally named {{EX:cn=Subschema}}.  If a server which
+entry normally named {{EX:cn=Subschema}}.  In a server which
 supports a single subschema subentry, the DN of the subschema
 subenty can usually be found by examining the value of the
-{{EX:subschemaSubentry}} attribute type in the {{root DSE}}
+{{EX:subschemaSubentry}} attribute type in the {{root DSE}}.
 Other servers may publish multiple subschema entries.  These
 can be located by examining the {{EX:subschemaSubentry}} attribute
 contained in the entry at the root of each administrative context.