Copied fiexed text from nettle.texinfo.

Rev: src/nettle/README:1.3

diff --git a/README b/README
index f2ad10d2350f7d393d1a57d144c182fe00363fca..353ab5a774f05857c0d867e7b010da138c1961cf 100644 (file)
--- a/README
+++ b/README
@@ -8,7 +8,7 @@ What is Nettle? A quote from the introduction in the Nettle Manual:
   algorithms, their properties and variants. You often have some algorithm
   selection process, often dictated by a protocol you want to implement.
   
-  And as the requirements of applications differ on subtle and not so
+  And as the requirements of applications differ in subtle and not so
   subtle ways, an API that fits one application well can be a pain to use
   in a different context. And that is why there are so many different
   cryptographic libraries around.
@@ -19,7 +19,7 @@ What is Nettle? A quote from the introduction in the Nettle Manual:
   memory allocation. It doesn't do any I/O.
   
   The idea is that one can build several application and context specific
-  interfaces on top of Nettle, and share the code, testcases, banchmarks,
+  interfaces on top of Nettle, and share the code, testcases, benchmarks,
   documentation, etc. For this first version, the only application using
   Nettle is LSH, and it uses an object-oriented abstraction on top of the
   library.