DOC: Fix broken intersphinx

docs/cubeviz/import_data.rst

@@ -12,8 +12,8 @@ application:
 
 Cubeviz supports loading the following data formats:
 
-* FITS file, `~astropy.io.fits.HDUList`, `~fits.hdu.hdulist.ImageHDU`, or
-  `~fits.hdu.hdulist.PrimaryHDU` that can be parsed as
+* FITS file, `~astropy.io.fits.HDUList`, `~astropy.io.fits.ImageHDU`, or
+  `~astropy.io.fits.PrimaryHDU` that can be parsed as
   `~specutils.Spectrum1D` 3D object, in which case the application
   will attempt to automatically parse the data into the viewers as described
   in :ref:`cubeviz-display-cubes`. This support includes the ASDF-in-FITS
@@ -67,7 +67,7 @@ method, which takes as input either the name of a local file or a
     >>> cubeviz.load_data("/Users/demouser/data/cube_file.fits")  # doctest: +SKIP
 
 Theoretically, mix-and-match loading might be possible. For instance,
-you may choose to load `~specutils.Spectrum1D` into one viewer, `~fits.hdu.hdulist.ImageHDU`
+you may choose to load `~specutils.Spectrum1D` into one viewer, `~astropy.io.fits.ImageHDU`
 into another, and Numpy array into the third one. However, user must ensure their
 data units and WCS's are compatible. Therefore, while possible, it is not recommended unless
 you know what you are doing.

jdaviz/configs/cubeviz/plugins/parsers.py

@@ -23,7 +23,7 @@ def parse_data(app, file_obj, data_type=None, data_label=None):
     ----------
     app : `~jdaviz.app.Application`
         The application-level object used to reference the viewers.
-    file_obj : str, `~fits.hdu.hdulist.ImageHDU`, `~fits.hdu.hdulist.PrimaryHDU`, `~fits.hdu.hdulist.HDUList`, `~specutils.Spectrum1D`, or ndarray
+    file_obj : str, `~astropy.io.fits.ImageHDU`, `~astropy.io.fits.PrimaryHDU`, `~astropy.io.fits.HDUList`, `~specutils.Spectrum1D`, or ndarray
         The path to a cube-like data FITS file or the data object to be loaded.
     data_type : {'flux', 'uncert', 'mask', `None`}
         The data type used to explicitly differentiate parsed data.