diff --git a/docs/source/graphics.rst b/docs/source/graphics.rst
index 4ce6619b8..bab6b3332 100644
--- a/docs/source/graphics.rst
+++ b/docs/source/graphics.rst
@@ -11,24 +11,26 @@ NEMO programs also need to display their data of course.
 Here we will make a distinction between *graphics* and *image* data.
 A simple but flexible *graphics* interface has been defined in NEMO and is used
 extensively in programs that need such output.  These are controlled by
-the user via the ``yapp=`` (system) keyword.
+the user via the ``yapp=`` :ref:`system_keywords`.
 
-To display *image* data we rely mostly (but see *ccdplot(1NEMO)* for an exception)
+To display *image* data we rely mostly (but see
+`ccdplot(1NEMO) <https://teuben.github.io/nemo/man_html/ccdplot.1.html>`_
+for an exception)
 on external software.
 Often images would need to be copied to a FITS file for this
-(but see ``nds9`` for an example that can use NEMO's image format).
-
+(but see ``nds9`` for an example that can use NEMO's image format), and
+use 3rd party programs such as *ds9*.
 
 The YAPP graphics interface
 ---------------------------
 
 The programs in NEMO which use *graphics* are rather simple and generally allow no
-interactive processing, except perhaps for a simple 'hit-the-return-key'
-or 'push-a-mouse-button' between successive plots or actions.  A very
+interactive processing, except perhaps for a simple 'hit-the-Enter-key'
+or 'click-a-mouse-button' between successive plots or actions.  A very
 simple interface (API) was defined (**yapp**, Yet Another Plotting Package)
 with basic plot functions.  
 There are currently a few yapp implementations
-available, such as a postscript-only device, and pgplot.  
+available, with a postscript-only device, and pgplot the most common ones.
 If your output device is not supported by the ones available
 in the current yapp directory
 (``$NEMO/src/kernel/yapp``), you may have to write a new one!
@@ -36,7 +38,7 @@ A reasonably experienced programmer writes a functional yapp-interface in
 an hour or so.
 
 Although this method results in a flexible graphics interface, a
-program can currently only be linked with one yapp-interface, which
+program can currently only be linked with one yapp-interface at a time, which
 is selected at NEMO's installation time via the **configure** script.
 This might
 result in the existence of more than one version of the same
@@ -48,16 +50,17 @@ screen,
 Hence we may see program names such as {\tt snapplot} (the default),
 ``snapplot_ps`` (postscript), or
 ``snapplot_cg`` (color Sun screen when this was popular) .
-Again: actual names may differ on your system.
+Again: actual names may differ on your system, and it may never be used.
 
 If programs are linked with the multiplexing libraries
 *yapp_pgplot* interface, several device drivers are transparently present through
 pgplot, and the system keyword ``yapp=`` is then used to select
 a device (a default can be set by using the **YAPP** environment
 variable). 
-See also the :ref:`iface` chapter
-or the
-`yapp <https://teuben.github.io/nemo/man_html/yapp.5.html>`_
+See also the
+:ref:`iface`
+chapter or the
+`yapp(5NEMO) <https://teuben.github.io/nemo/man_html/yapp.5.html>`_
 manual page.
 
 However, despite these grim sounding words, we currently
@@ -65,6 +68,12 @@ almost exclusively use the PGPLOT implementation of yapp, which is very flexible
 You will need to have pgplot installed on your system, which is another story
 in itself.
 
+.. note::
+   The command ``mknemo pgplot`` may work if you cannot find a system package installer.
+   This will install PGPLOT system files in ``$NEMOLIB``.  
+
+
+
 pyplot=: python matplotlib
 --------------------------
 
@@ -81,20 +90,28 @@ General Graphics Display
 Another convenient way to present data in graphical form is by using
 the table format. We have already encountered the *tables* created by
 many NEMO programs. These tables can be used by NEMO programs
-such as *tabplot(1NEMO)*, *tabhist(1NEMO)*, and other packages
+such as
+`tabplot(1NEMO) <https://teuben.github.io/nemo/man_html/tabplot.1.html>`_
+and 
+`tabhist(1NEMO) <https://teuben.github.io/nemo/man_html/tabhist.1.html>`_, 
+and other packages
 such as
 *gnuplot*,
 *xgobi*,
 *xmgrace*, 
-*xgraphic*, and
-*glueviz*.
+*xgraphic*, 
+*glueviz*, and
+*topcat*.
 
 
 Image Display Interface
 -----------------------
 
-Data in *image(5NEMO)* format can be transferred in
-*fits(5NEMO)* format and subsequently displayed and analyzed within
+Data in 
+`image(5NEMO) <https://teuben.github.io/nemo/man_html/image.5.html>`_
+format can be transferred in
+`fits(5NEMO) <https://teuben.github.io/nemo/man_html/fits.5.html>`_
+format and subsequently displayed and analyzed within
 almost any astronomical image processing system.  They are generally much
 better equipped to display and manipulate data of this kind of format. 
 A number of standalone display programs can also understand FITS