diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/subsystem.html b/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/subsystem.html
index e539d35cba4..6c06ea77f5c 100755
--- a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/subsystem.html
+++ b/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/subsystem.html
@@ -19,7 +19,7 @@ a connection when a connection is expanded in the Remote Systems view.
For example, here is an iSeries connection with four subsystems,
each created by a subsystem configuration registered with this extension point.
-The extension markup is quite simple for this extension point,
+
The extension markup is quite simple for this extension point,
as it has only one element, <configuration>, with only a few simple attributes to supply:
@@ -54,7 +54,7 @@ interface, as described in the following programming details section.
It is important to remember what the purpose of a subsystem is, and how it fits in the overall RSE model, so as to understand the programming details for supporting
subsystems via this subsystem configuration extension point. Minimally speaking, this extension point requires a class that implements the interface
-ISubSystemFactory.
+ISubSystemConfiguration.
Ultimately, the intent of a subsystem configuration is to provide individual
subsystem instances to each connection, and the intent of a subsystem instance is to present remote resources for display or manipulation purposes. Thus, you must also create a class implementing the interface ISubSystem.
@@ -194,7 +194,7 @@ following summarizes the minimum set of classes you will be creating in order to
and has no eclipse-dependencies, so it can be used in your client subsystem code, or your server-side code.
- Creating a subclass of DefaultSubSystemFactoryImpl.
+ Creating a subclass of SubSystemConfiguration.
Defining your subsystemConfigurations extension in your plugin.xml file.
For each remote resource class you created in step 4, you need to create an adapter class, which extends
AbstractSystemViewAdapter and which
@@ -235,11 +235,11 @@ following summarizes the minimum set of classes you will be creating in order to
and in it calling setFilterStringEditPane
on the given dialog.
Override the getNewFilterPoolFilterAction(SystemFilterPool, Shell)
- method in your subsystem factory, to return an instance of your new-filter action.
+ method in your subsystem configuration, to return an instance of your new-filter action.
You can actually avoid creating an action subclass if you choose, by calling the configuration methods
in the RSE-supplied new-filter action class.
Override the getChangeFilterAction(SystemFilter, Shell)
- method in your subsystem factory, to return an instance of your change-filter action.
+ method in your subsystem configuration, to return an instance of your change-filter action.
You can actually avoid creating an action subclass if you choose, by calling the configuration methods
in the RSE-supplied change-filter action class.
