adjusting test system debug uart reference

[avr-crypto-lib.git] / USAGE.hashfunctions

diff --git a/USAGE.hashfunctions b/USAGE.hashfunctions
index 145cbc2f792ebc1f80bf6fdb2d15268e4569f596..163cd2d4aa1794d0bdd894fbb6d82c27267eb0ac 100644 (file)
--- a/USAGE.hashfunctions
+++ b/USAGE.hashfunctions
@@ -28,13 +28,13 @@ email:  daniel.otte@rub.de
   * compression algorithm
   * finalization function
  
-3. block cipher API
+3. hash function API
  The API is not always consistent due to the fact that we tried to optimize the
  code for size (flash, heap and stack) and speed (runtime of the different 
  components).
  Generally the API of the implemented block ciphers consists of:
  
- *_init function, which implements the keyschedule
+ *_init      function, which implements the initialisation of the context
  *_nextBlock function, which implements the compression algorithm
  *_lastBlock function, which implements the the padding algorithm
  *_ctx2hash  function, which turns a context into an actual hash value
@@ -45,7 +45,7 @@ email:  daniel.otte@rub.de
  parameter means what. 
   
 3.1.2 sizes in bits and bytes
- Working with cryptographical functions involves working with different 
+ Working with cryptographic functions involves working with different 
  lengths. Some times you want to know it in bits and sometimes in bytes. To 
  reduce frustration and to avoid bugs we suffix a length parameter with either
  _b or _B depending on the meaning. _b means in bits and _B means in bytes 
@@ -55,7 +55,7 @@ email:  daniel.otte@rub.de
  The *_init function generally takes a pointer to the context as parameter.
  This function initializes the context with algorithm specific values.
  
-3.3. *_nexBlock function
+3.3. *_nextBlock function
  The *_nextBlock function is the core of each hash function. It updates the hash 
  state with a given message block. So this function uses a context pointer and 
  a message pointer as parameters. The size of a message block is fixed for each