peerdb/peers.in.5.in: The magic is spelled `@inherit', not `@inherits'.

diff --git a/peerdb/peers.in.5.in b/peerdb/peers.in.5.in
index 240296e996ebaf405d0ed22d10b49106f04d0306..c92dabbca0ebefa2df1399273fb120b73b5f3947 100644 (file)
--- a/peerdb/peers.in.5.in
+++ b/peerdb/peers.in.5.in
@@ -97,7 +97,7 @@ There is a simple concept of
 .I inheritance
 for sections.  If a section contains an assignment
 .IP
 .I inheritance
 for sections.  If a section contains an assignment
 .IP

-.BI "@inherits = " parent
+.BI "@inherit = " parent

 .PP
 then any lookups which can't be satisfied in that section will be
 satisfied instead from the
 .PP
 then any lookups which can't be satisfied in that section will be
 satisfied instead from the


@@ -113,7 +113,7 @@ detail = in parent
 blurb = expand $(detail)
 .VE
 Apart from its effect on lookups, as just described, the
 blurb = expand $(detail)
 .VE
 Apart from its effect on lookups, as just described, the

-.B @inherits
+.B @inherit

 key is entirely ignored.  In particular, it is never written to the
 database.
 .
 key is entirely ignored.  In particular, it is never written to the
 database.
 .


@@ -237,7 +237,7 @@ Sections whose names have the form
 .BI @ whatever
 are ignored (though their contents may be relevant if the section is
 named in another section's
 .BI @ whatever
 are ignored (though their contents may be relevant if the section is
 named in another section's

-.B @inherits
+.B @inherit

 key).
 .hP \*o
 Sections whose names have the form
 key).
 .hP \*o
 Sections whose names have the form


@@ -245,7 +245,7 @@ Sections whose names have the form
 are written to local-type database records with the same name.  The keys
 and values defined in the section (and its parent section, if it
 contains an
 are written to local-type database records with the same name.  The keys
 and values defined in the section (and its parent section, if it
 contains an

-.B @inherits
+.B @inherit

 key) are stored in the record using
 .B form-urlencoding
 as defined in RFC1822, except that the key-value pairs are separated by
 key) are stored in the record using
 .B form-urlencoding
 as defined in RFC1822, except that the key-value pairs are separated by


@@ -254,7 +254,7 @@ semicolons
 rather than ampersands
 .RB ` & '.
 The
 rather than ampersands
 .RB ` & '.
 The

-.B @inherits
+.B @inherit

 key-value pair is not written to the database.
 .hP \*o
 Other sections are written to peer-type database records, named
 key-value pair is not written to the database.
 .hP \*o
 Other sections are written to peer-type database records, named