updates

1 files changed, 33 insertions, 10 deletions

diff --git a/docs/pysnmp-tutorial.html b/docs/pysnmp-tutorial.html
index 3e54df2..37a7f2d 100644
--- a/docs/pysnmp-tutorial.html
+++ b/docs/pysnmp-tutorial.html
@@ -538,15 +538,19 @@ receiver in Manager Applications.
 </H4>
 
 <P>
-As of this writing, one-line Applications currently cover Manager-side 
-operations. Agent and Proxy roles could be implemented on top of
-native Applications API.
+As of this writing, one-liner Applications support generating Manager-side 
+GET/SET/GETNEXT/GETBULK and issuing Agent-side TRAP/INFORM messages.
+Agent and Manager side responders are more complex and rarely used to fit
+them into the concise one-liner API so these should be implemented on top of
+standard SNMP Applications API.
 </P>
 
 <P>
 There're two kinds of APIs to one-line Applications: synchronous and
-asynchronous. Both are implemented within the
-<STRONG>pysnmp.entity.rfc3413.oneliner.cmdgen</STRONG> module.
+asynchronous. They are very similar in terms of their API and behaviour,
+both are implemented by the
+<STRONG>pysnmp.entity.rfc3413.oneliner.cmdgen</STRONG> module. The
+asynchronous version is more suited for massively parallel SNMP messaging.
 </P>
 
 <A NAME="SYNCH-ONELINER-APPS"></A>
@@ -560,11 +564,16 @@ Applications. It's advised to employ for singular and blocking
 operations as well as for rapid prototyping.
 </P>
 
+<A NAME="CommandGenerator"></A>
+<H4>
+2.1.1.1 Command Generator
+</H4>
+
 <P>
 All Command Generator Applications are implemented by a single class:
+
 </P>
 
-<A NAME="CommandGenerator"></A>
 <DL>
 <DT>class <STRONG>CommandGenerator</STRONG>([<STRONG>snmpEngine</STRONG>])</DT>
 <DD>
@@ -574,9 +583,11 @@ Create a SNMP Command Generator object.
 
 <P>
 Although instantiation of this class is cheap, in the course of its further
-use, SNMP engine configuration is built and maintained though methods invocation.
-Therefore it is advised to keep and reuse CommandGenerator instance (or <STRONG>snmpEngine</STRONG>
-instance if passed as an initializer) for as long as possible within user applicatin.
+use, SNMP engine configuration is built and maintained though methods 
+invocation.
+Therefore it is advised to keep and reuse CommandGenerator instance 
+(or <STRONG>snmpEngine</STRONG> instance if passed as an initializer) 
+for as long as possible within user applicatin.
 </P>
 </DD>
 </DL>
@@ -1043,17 +1054,29 @@ else:
 </PRE>
 </TD></TR></TABLE>
 
+<A NAME="NotificationOriginator"></A>
+<H4>
+2.1.1.2 Notification Originator
+</H4>
+
 <P>
 Notification Originator Applications are implemented within a single class:
 </P>
 
-<A NAME="NotificationOriginator"></A>
 <DL>
 <DT>class <STRONG>NotificationOriginator</STRONG>([<STRONG>snmpContext</STRONG>])</DT>
 <DD>
 <P>
 Create a SNMP Notification Originator object.
 </P>
+<P>
+Although instantiation of this class is cheap, in the course of its further
+use, SNMP engine configuration is built and maintained though methods 
+invocation.
+Therefore it is advised to keep and reuse NotificationOriginator instance 
+(or <STRONG>snmpEngine</STRONG> instance if passed as an initializer) 
+for as long as possible within user applicatin.
+</P>
 </DD>
 </DL>