diff --git a/doc/source/conf.py b/doc/source/conf.py index e5d6cdb5..ea9740bc 100644 --- a/doc/source/conf.py +++ b/doc/source/conf.py @@ -74,7 +74,7 @@ add_function_parentheses = True # If true, the current module name will be prepended to all description # unit titles (such as .. function::). -#add_module_names = True +add_module_names = False # If true, sectionauthor and moduleauthor directives will be shown in the # output. They are ignored by default. diff --git a/doc/source/manual/unittest.rst b/doc/source/manual/unittest.rst index 687c9750..9a60f4ca 100644 --- a/doc/source/manual/unittest.rst +++ b/doc/source/manual/unittest.rst @@ -66,7 +66,7 @@ Unit test development In this section, we will informally explore the application of unit test techniques to hardware design. We will do so by a (small) example: testing a -binary to Gray encoder as introduced in section :ref:`intro-indexing`. +binary to Gray encoder as introduced in section :ref:`hwtypes-indexing`. .. _unittest-req: @@ -260,7 +260,7 @@ one. After the test feedback, a full traceback is shown that can help to debug the test output. Finally, if we use the correct implementation as in section -:ref:`intro-indexing`, the output is:: +:ref:`hwtypes-indexing`, the output is:: % python test_gray.py -v Check that only one bit changes in successive codewords ... ok