summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorNiels Möller <nisse@lysator.liu.se>2001-09-18 12:05:55 +0200
committerNiels Möller <nisse@lysator.liu.se>2001-09-18 12:05:55 +0200
commit866981e56849d39919169c5616640cfbba16085a (patch)
tree7da3590062744221631fb4841434287c65a626f9 /README
parent5ee4ad21d881a408f494bafc690a6c0e652058f9 (diff)
downloadnettle-866981e56849d39919169c5616640cfbba16085a.tar.gz
Copied fiexed text from nettle.texinfo.
Rev: src/nettle/README:1.3
Diffstat (limited to 'README')
-rw-r--r--README4
1 files changed, 2 insertions, 2 deletions
diff --git a/README b/README
index f2ad10d2..353ab5a7 100644
--- 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.