[Openvas-commits] r3314 - trunk/openvas-compendium

[scm-commit@wald.intevation.org]

Author: geoff
Date: 2009-05-11 09:56:42 +0200 (Mon, 11 May 2009)
New Revision: 3314

Modified:
   trunk/openvas-compendium/ChangeLog
   trunk/openvas-compendium/openvas-compendium.tex
Log:
Fixed a typo in "singature" line 909 spotted by mattm.  Thanks!



Modified: trunk/openvas-compendium/ChangeLog
===================================================================
--- trunk/openvas-compendium/ChangeLog	2009-05-11 07:01:24 UTC (rev 3313)
+++ trunk/openvas-compendium/ChangeLog	2009-05-11 07:56:42 UTC (rev 3314)
@@ -1,5 +1,10 @@
 2009-05-11 Geoff Galitz <geoff at galitz.org>
+	
+	* openvas-compendium.tex:  Fixed a typo in "singature" line 909
+	spotted by mattm.  Thanks!
 
+2009-05-11 Geoff Galitz <geoff at galitz.org>
+
 	* openvas-compendium.tex:  Edited "What is a Signature" section
 	for grammar and flow.
 

Modified: trunk/openvas-compendium/openvas-compendium.tex
===================================================================
--- trunk/openvas-compendium/openvas-compendium.tex	2009-05-11 07:01:24 UTC (rev 3313)
+++ trunk/openvas-compendium/openvas-compendium.tex	2009-05-11 07:56:42 UTC (rev 3314)
@@ -906,7 +906,7 @@
 If the signature is verified, you must still determine if you trust the
 provider of the NVT file(s) and keys.  There are many ways and tools to manage this.
 
-In summary, an NVT file is paired with a singature (in a seperate signature
+In summary, an NVT file is paired with a signature (in a seperate signature
 file) and that pair then has a checksum computed.  The checksum verifies the
 integrity of the NVT file.  If the checksum does not match
 the expected result, the NVT file should be considered untrustworthy.