chiark
/
gitweb
/
~ianmdlvl
/
developers-reference.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
typo reported by Neil Spring
[developers-reference.git]
/
developers-reference.sgml
diff --git
a/developers-reference.sgml
b/developers-reference.sgml
index 6b2e7a8ab98a051245becb0bd7049b8b1e536d01..91f3f32646f376b5e93cca5546ab3e130827b6e6 100644
(file)
--- a/
developers-reference.sgml
+++ b/
developers-reference.sgml
@@
-6,7
+6,7
@@
<!ENTITY % commondata SYSTEM "common.ent" > %commondata;
<!-- CVS revision of this document -->
<!ENTITY % commondata SYSTEM "common.ent" > %commondata;
<!-- CVS revision of this document -->
- <!ENTITY cvs-rev "$Revision: 1.21
4
$">
+ <!ENTITY cvs-rev "$Revision: 1.21
5
$">
<!-- if you are translating this document, please notate the CVS
revision of the developers reference here -->
<!--
<!-- if you are translating this document, please notate the CVS
revision of the developers reference here -->
<!--
@@
-3330,9
+3330,9
@@
or, if the package name itself is a plural (such as
<example><var>package-name</var> are <var>synopsis</var>.</example>
<example><var>package-name</var> are <var>synopsis</var>.</example>
-This way of forming a sent
a
nce from the package name and synopsis
+This way of forming a sent
e
nce from the package name and synopsis
should be considered as a heuristic and not a strict rule. There are
should be considered as a heuristic and not a strict rule. There are
-some cases where it doesn't make sense to try to form a sent
a
nce.
+some cases where it doesn't make sense to try to form a sent
e
nce.
</sect1>
<sect1 id="bpp-pkg-desc">
</sect1>
<sect1 id="bpp-pkg-desc">