more docu on event logging

2 files changed, 4 insertions, 3 deletions

diff --git a/docs/log/README b/docs/log/README
index 1d705e5..3335978 100644
--- a/docs/log/README
+++ b/docs/log/README
@@ -33,10 +33,10 @@ Other projects:
 
 All of them ignore the message resource and classes of same errors with
 different parameters. Sadly enough also the MS guys themselves (see
-184416764.html). log4j has influenced log4cpp, log4pp, logdriver (UMHO
+184416764.html). log4j has influenced log4cpp, log4pp, logdriver (IMHO
 to the worse!).
 
-The category is usually used for mapping the coarser gained levels of
+The category is usually used for mapping the coarser grained levels of
 the logging API to the event logger (POCO, log4cpp). IMHO this is better
 used for something like subsystems or components.
 
@@ -44,6 +44,7 @@ log4cplus is the only library to handle the current user SID.
 log4cplus adds the event source to the registry.
 
 .NET at least cares to install a dummy message DLL with a %1's in them.
+Also POCO takes the one event message approach.
 
 Good articles:
 - http://www.codeproject.com/KB/dotnet/evtvwr.aspx
diff --git a/docs/log/TODOS b/docs/log/TODOS
index 5ef70c7..3c7e654 100644
--- a/docs/log/TODOS
+++ b/docs/log/TODOS
@@ -1,6 +1,6 @@
-- compare other approaches, disappointing all of them so far!
 - local localized error handling (GetLastError and strerror_r strings)
 - Windows event logger
+  - categories don't work yet
   - audit event log types, especially the effects on syslog and the upper
     abstraction layer
   - event log categories, for instance for components, the idea is that