summaryrefslogtreecommitdiff
path: root/lang/siod/DESCR
diff options
context:
space:
mode:
authorjmmv <jmmv>2003-05-06 17:40:18 +0000
committerjmmv <jmmv>2003-05-06 17:40:18 +0000
commit5a79423b6feb188f48299ebbaf981575b33d3f48 (patch)
tree37ae7d212f46ef8018a7bd8c13edba7da1a47ed9 /lang/siod/DESCR
parentf58f4f25565243e0fcd6ee359261be2e3cfc7286 (diff)
downloadpkgsrc-5a79423b6feb188f48299ebbaf981575b33d3f48.tar.gz
Drop trailing whitespace. Ok'ed by wiz.
Diffstat (limited to 'lang/siod/DESCR')
-rw-r--r--lang/siod/DESCR4
1 files changed, 2 insertions, 2 deletions
diff --git a/lang/siod/DESCR b/lang/siod/DESCR
index 218d9bb617b..21f59053cd2 100644
--- a/lang/siod/DESCR
+++ b/lang/siod/DESCR
@@ -5,7 +5,7 @@ scripting extensions.
The motivation behind SIOD remains a small footprint, in every sense
of the word, at runtime, at compile time, and in cognitive attention
required to understand how the system works enough to be able to
-extend it as well as the author would have done the work himself.
+extend it as well as the author would have done the work himself.
About eight years have passed since that initial release. It has been
possible to add a feature or two without contributing to the cause of
@@ -13,4 +13,4 @@ software bloat, with the code segment of the libsiod shared library
remaining under 75K bytes on a prototypical comparison machine like a
VAX. Furthermore, as the richness of the C runtime library available
on most systems has improved over time, SIOD remains a useful kind of
-glue to have in a software engineers toolbox.
+glue to have in a software engineers toolbox.