DOC: Fix Step ref in devel_io_design

Author: pllim

docs/jwst/stpipe/devel_io_design.rst

@@ -34,19 +34,19 @@ API Summary
 Classes, Methods, Functions
 ---------------------------
 
-* :meth:`stpipe.step.Step.open_model`: Open a ``DataModel``
+* :meth:`stpipe.Step.open_model`: Open a ``DataModel``
 * ``Step.load_as_level2_asn()``: Open a list or file as Level2 association
 * ``Step.load_as_level3_asn()``: Open a list or file as Level3 association
-* :meth:`stpipe.step.Step.make_input_path`: Create a file name to
+* :meth:`stpipe.Step.make_input_path`: Create a file name to
   be used as input
-* :meth:`stpipe.step.Step.save_model`: Save a ``DataModel`` immediately
-* :attr:`stpipe.step.Step.make_output_path`: Create a file name
+* :meth:`stpipe.Step.save_model`: Save a ``DataModel`` immediately
+* :attr:`stpipe.Step.make_output_path`: Create a file name
   to be used as output
 
 Design
 ======
 
-The :class:`~stpipe.step.Step` architecture is designed such that
+The :class:`~stpipe.Step` architecture is designed such that
 a ``Step``'s intended sole responsibility is to perform the calculation
 required. Any input/output operations are handled by the surrounding
 ``Step`` architecture. This is to help facilitate the use of ``Step``'s
@@ -69,7 +69,7 @@ best practices.
 To facilitate this design, a basic ``Step`` is suggested to have the
 following structure::
 
-  class MyStep(stpipe.step.Step):
+  class MyStep(stpipe.Step):
 
       spec = ''  # Desired configuration parameters
 
@@ -128,12 +128,12 @@ is expected to accept other object types as well.
 A ``Step``'s primary argument is expected to be either a string containing
 the file path to a data file, or a JWST
 :class:`~jwst.datamodels.JwstDataModel` object. The method
-:meth:`~stpipe.step.Step.open_model` handles either type of
+:meth:`~stpipe.Step.open_model` handles either type of
 input, returning a ``DataModel`` from the specified file or a shallow
 copy of the ``DataModel`` that was originally passed to it. A typical
 pattern for handling input arguments is::
 
-  class MyStep(stpipe.step.Step):
+  class MyStep(stpipe.Step):
 
       def process(self, input_argument):
 
@@ -143,19 +143,19 @@ pattern for handling input arguments is::
 ``input_argument`` can either be a string containing a path to a data
 file, such as FITS file, or a ``DataModel`` directly.
 
-:meth:`~stpipe.step.Step.open_model` handles ``Step``-specific
+:meth:`~stpipe.Step.open_model` handles ``Step``-specific
 issues, such ensuring consistency of input directory handling.
 
 If some other file type is to be opened, the lower level method
-:meth:`~stpipe.step.Step.make_input_path` can be used to specify
+:meth:`~stpipe.Step.make_input_path` can be used to specify
 the input directory location.
 
 Input and Associations
 ----------------------
 
 Many of the JWST calibration steps and pipelines expect an
 :ref:`Association <associations>` file as input. When opened with
-:meth:`~stpipe.step.Step.open_model`, a
+:meth:`~stpipe.Step.open_model`, a
 :class:`~jwst.datamodels.container.ModelContainer` is returned. ``ModelContainer``
 is a list-like object where each element is the
 ``DataModel`` of each member of the association. The ``asn_table`` attribute is
@@ -303,7 +303,7 @@ as their primary input. In general, the association defines what the
 output basename should be. A typical pattern used to handle
 associations is::
 
-  class MyStep(stpipe.step.Step):
+  class MyStep(stpipe.Step):
 
       spec = ''  # Desired configuration parameters
 
@@ -349,7 +349,7 @@ Save That Model: Step.save_model
 ````````````````````````````````
 
 If a ``Step`` needs to save a ``DataModel`` before the step completes, use
-of :meth:`stpipe.step.Step.save_model` is the recommended over
+of :meth:`stpipe.Step.save_model` is the recommended over
 directly calling :meth:`jwst.datamodels.JwstDataModel.save`.
 ``Step.save_model`` uses the ``Step`` framework and hence will honor the
 following:
@@ -374,14 +374,14 @@ results that would have a different suffix::
 
     self.save_model(intermediate_result_datamodel, suffix='intermediate')
 
-See :meth:`stpipe.step.Step.save_model` for further information.
+See :meth:`stpipe.Step.save_model` for further information.
 
 Make That Filename: Step.make_output_path
 `````````````````````````````````````````
 
 For the situations when a filename is needed to be constructed before
 saving, either to know what the filename will be or for data that is
-not a ``DataModel``, use :meth:`stpipe.step.Step.make_output_path`. By default, calling
+not a ``DataModel``, use :meth:`stpipe.Step.make_output_path`. By default, calling
 ``make_output_path`` without any arguments will return what the default
 output file name will be::