3 files changed, 2 insertions, 10 deletions
diff --git a/lib/taurus/core/epics/__init__.py b/lib/taurus/core/epics/__init__.py
index b39cf4a2..1f8123a8 100644
--- a/lib/taurus/core/epics/__init__.py
+++ b/lib/taurus/core/epics/__init__.py
@@ -54,11 +54,11 @@ Epics attributes (should) work just as other Taurus attributes and can be
 referred by their model name wherever a Taurus Attribute model is expected. For
 example, you can launch a `TaurusForm` with an epics attribute::
 
-    $> taurusform ca:my:example
+    $> taurus form ca:my:example
 
 Similarly, you can combine epics attributes with attributes from other schemes::
 
-    $> taurusform 'ca:my:example' 'tango:sys/tg_test/1/float_scalar'\
+    $> taurus form 'ca:my:example' 'tango:sys/tg_test/1/float_scalar'\
        'eval:{ca:my:example}*{tango:sys/tg_test/1/float_scalar}'
 
 Currently, the taurus epics scheme just supports epics PVs, implementing them as
diff --git a/lib/taurus/core/epics/epicsattribute.py b/lib/taurus/core/epics/epicsattribute.py
index bba58f84..11680af2 100644
--- a/lib/taurus/core/epics/epicsattribute.py
+++ b/lib/taurus/core/epics/epicsattribute.py
@@ -226,14 +226,6 @@ class EpicsAttribute(TaurusAttribute):
 
     def isUsingEvents(self):
         return True  # TODO: implement this
-
-    def _subscribeEvents(self):
-        raise NotImplementedError("Not allowed to call AbstractClass" +
-                                  " TaurusAttribute._subscribeEvents")
-
-    def _unsubscribeEvents(self):
-        raise NotImplementedError("Not allowed to call AbstractClass" +
-                                  " TaurusAttribute._unsubscribeEvents")
 # ------------------------------------------------------------------------------
 
     def factory(self):
diff --git a/lib/taurus/core/epics/test/test_epicsattribute.py b/lib/taurus/core/epics/test/test_epicsattribute.py
index 3a32c91f..3a32c91f 100755..100644
--- a/lib/taurus/core/epics/test/test_epicsattribute.py
+++ b/lib/taurus/core/epics/test/test_epicsattribute.py