Typo fixes. Fixes bug#1093

1 files changed, 6 insertions, 6 deletions

diff --git a/doc/sysnotes.texi b/doc/sysnotes.texi
index 56a0db816..a8cea877a 100644
--- a/doc/sysnotes.texi
+++ b/doc/sysnotes.texi
@@ -6,7 +6,7 @@
 @chapter Notes pertaining to certain OSes.
 
 GnuPG has been developed on GNU/Linux systems and is know to work on
-almost all Free OSes.  All modern POSIX systems should be supproted
+almost all Free OSes.  All modern POSIX systems should be supported
 right now, however there are probably a lot of smaller glitches we need
 to fix first.  The major problem areas are:
 
@@ -14,14 +14,14 @@ to fix first.  The major problem areas are:
 @item 
 For logging to sockets and other internal operations the
 @code{fopencookie} function (@code{funopen} under *BSD) is used.  This
-is a very convient function which makes it possible to create outputs in
+is a very convenient function which makes it possible to create outputs in
 a structures and easy maintainable way.  The drawback however is that
 most proprietary OSes don't support this function.  At g10@tie{}Code we
 have looked into several ways on how to overcome this limitation but no
 sufficiently easy and maintainable way has been found.  Porting
 @emph{glibc} to a general POSIX system is of course an option and would
 make writing portable software much easier; this it has not yet been
-done and the system administrator wouldneed to cope with the GNU
+done and the system administrator would need to cope with the GNU
 specific admin things in addition to the generic ones of his system.
 
 We have now settled to use explicit stdio wrappers with a functionality
@@ -30,19 +30,19 @@ similar to funopen.  Although the code for this has already been written
 
 This means that on systems not supporting either @code{funopen} or
 @code{fopencookie}, logging to a socket won't work, prompts are not
-formatted as pretty as theyshould be and @command{gpgsm}'s
+formatted as pretty as they should be and @command{gpgsm}'s
 @code{LISTKEYS} Assuan command does not work.
 
 @item
 We are planning to use file descriptor passing for interprocess
 communication.  This will allow us save a lot of resources and improve
 performance of certain operations a lot.  Systems not supporting this
-won't gain these benefits but we try to keep them working the satndard
+won't gain these benefits but we try to keep them working the standard
 way as it is done today.
 
 @item
 We require more or less full POSIX compatibility.  This has been
-arround for 15 years now and thus we don't believe it makes sense to
+around for 15 years now and thus we don't believe it makes sense to
 support non POSIX systems anymore.  Well, we of course the usual
 workarounds for near POSIX systems well be applied.