Fix outdated references to Harlequin Dylan and Functional Developer

documentation/source/duim-reference/conventions.rst

@@ -33,10 +33,10 @@ use the interfaces being described. If you wish, you can run these
 examples interactively by typing them into the Dylan Playground.
 
 A number of additional, longer examples are provided as part of the
-Harlequin Dylan installation, and are installed on your hard disk
+Open Dylan installation, and are installed on your hard disk
 automatically. You can look at these examples and load them into the
 environment by clicking on the examples button in the main window of the
-Harlequin Dylan environment.
+Open Dylan environment.
 
 Longer examples are also provided and discussed fully in the *Building
 Applications using DUIM*, which you should refer to for an introduction

documentation/source/duim-reference/frames.rst

@@ -174,28 +174,13 @@ exposed by the DUIM-Gadgets library, two of its subclasses are exposed
 by the DUIM-Frames library: :class:`<wizard-page>` and :class:`<property-page>`. See
 :ref:`gadgets-subclasses-of-page` for an introduction to these classes.
 
-DUIM-Commands Library
-=====================
-
-All commands-related interfaces are now defined directly in the Commands
-library. However, these same interfaces are imported to and re-exported
-from DUIM-Frames, so they can be used in almost the same way as for
-Harlequin Dylan 1.0. You should continue to look for commands-related
-documentation in this chapter.
-
-A consequence of the introduction of the Commands library is that a
-slight change in syntax is required in the definition of commands in
-command tables. In Harlequin Dylan 1.0, two approaches could be taken
-when specifying a command in a table. For example, a menu item could be
-specified by either of the following:
-
-.. code-block:: dylan
-
-   menu-item "My Command" = make(<command>, function: my-command),
-   menu-item "My Command" = my-command,
+Commands Interface
+==================
 
-Beginning with Harlequin Dylan 1.1, only the last of these may be used.
-This may require you to change some of your code.
+The DUIM-Frames library makes extensive use of commands-related
+interfaces defined in the :lib:`commands` library. These interfaces
+are imported to and re-exported from DUIM-Frames, so it is not
+necessary to import :lib:`commands` explicitly.
 
 DUIM-Frames Module
 ==================

documentation/source/duim-reference/gadgets.rst

@@ -3611,7 +3611,7 @@ are exported from the *duim-gadgets* module.
 
    :seealso:
 
-     - :class;`<list-control>`
+     - :class:`<list-control>`
      - :gf:`list-control-view`
      - :type:`<table-control-view>`