Docs: Fix cmd links from bugpoint docs

docs/source/using_yosys/bugpoint.rst

@@ -185,7 +185,7 @@ the failure, you can use the ``bugpoint_keep`` attribute.  This can be done with
 ``setattr -set bugpoint_keep 1 [selection]`` from a Yosys script.  It is also
 possible to limit `bugpoint` to only removing certain *kinds* of objects, such
 as only removing entire modules or cells (instances of modules).  For more about
-the options available, check ``help bugpoint`` or :doc:`/cmd/bugpoint`.
+the options available, check ``help bugpoint`` or :cmd:title:`bugpoint`.
 
 In some situations, it may also be helpful to use `setenv` before `bugpoint` to
 set environment variables for the spawned processes.  An example of this is

docs/source/using_yosys/more_scripting/load_design.rst

@@ -57,6 +57,7 @@ The `read` command
 Yosys frontends
 ~~~~~~~~~~~~~~~
 
+- :doc:`/cmd/index_frontends`
 - typically start with ``read_``
 - built-in support for heredocs
 
@@ -86,7 +87,12 @@ Yosys frontends
 The `read_verilog` command
 """"""""""""""""""""""""""
 
-- :doc:`/cmd/index_frontends`
+- :cmd:title:`read_verilog`; also
+
+  + :cmd:title:`verilog_defaults`,
+  + :cmd:title:`verilog_defines`, and
+  + :cmd:title:`read_verilog_file_list`
+
 - supports most of Verilog-2005
 - limited support for SystemVerilog
 - some non-standard features/extensions for enabling formal verification
@@ -117,12 +123,12 @@ The `read_verilog` command
 Other built-in ``read_*`` commands
 """"""""""""""""""""""""""""""""""
 
-- :doc:`/cmd/read_rtlil`
-- :doc:`/cmd/read_aiger`
-- :doc:`/cmd/read_blif`
-- :doc:`/cmd/read_json`
-- :doc:`/cmd/read_liberty`
-- :doc:`/cmd/read_xaiger2`
+- :cmd:title:`read_rtlil`
+- :cmd:title:`read_aiger`
+- :cmd:title:`read_blif`
+- :cmd:title:`read_json`
+- :cmd:title:`read_liberty`
+- :cmd:title:`read_xaiger2`
 
 .. TODO:: does `write_file` count?