anchor.diff:  	</P>           
   
   	<P><B>Configure SNMP Data Collection per Interface</b>: This interface will allow you
  -	to configure which non-IP interfaces are used in SNMP Data Collection.
  +	to configure which IP and non-IP interfaces are used in SNMP Data Collection.
   	</P>
   
           <p><b>Manage and Unmanage Interfaces and Services</b>: <em>Managing</em> an interface or service means that
           OpenNMS performs tests on this interface or service. If you want to explicitly enable or disable testing you
  -        can set that up here. A typical case is if a webserver is listening on both the backend and the frontend interface.
  -        If you manage the service on both interfaces, you will get two notifications if it fails. If you only want one,
  +        can set that up here. A typical case is if a web server is listening on both an internal and an external interface.
  +        If you manage the service on both interfaces, you will get two notifications if it fails. If you want only one,
           unmanage the service on one of the interfaces.
           </p>
                 
  
positive.code:         </p>
  
  	<p><b>Manage Provisioning Groups</b>: Manually add nodes, interfaces
  	and services to OpenNMS.  The creation of these nodes are managed completely by you 
  	rather by creating an import file and sending the data to the OpenNMS importer or having OpenNMS
  	discover the network.
  	</p>
  
          <p><b>Import and Export Asset Information</b>: Export and import data into OpenNMS's asset inventory.             
  
negative.code:      <p><b>Manage thresholds</b>: Allows you to configure (add/remove/modify) thresholds. 
  
          <p><b>Configure Notifications</b>: Create and manage notification escalation
              plans, called <em>destination paths</em>. A destination path is associated to
              an OpenNMS event.  Each path can have any arbitrary number of escalations or 
              targets (users or groups) and can send notices through email, pagers, et cetera.  
              Each destination path can be triggered by any number of OpenNMS events and can 
              further be associated with specific interfaces or services.   
          </p>
  
  
  	<p><b>Scheduled Outages</b>: Add and edit scheduled 
  	    outages. You can pause notifications, polling, thresholding and data collection 
              (or any combination of the four) for any interface/node for any time.  
  	</p>
  
  