diff --git a/doc/MODULE_DESIGN.org b/doc/MODULE_DESIGN.org
index 27cf9d3..af3a1a6 100644
--- a/doc/MODULE_DESIGN.org
+++ b/doc/MODULE_DESIGN.org
@@ -55,9 +55,6 @@ Not all HPI Modules are currently at that level of complexity -- some are simple
 A related concern is [[*An Extendable module structure][how to structure namespace packages]] to allow users to easily extend them, and how this conflicts with single file modules. If a module is converted from a single file module to a namespace with multiple files, it seems this is a breaking change, see [[https://github.com/karlicoss/HPI/issues/89][#89]] for an example of this.
 
 * Adding new modules
-:PROPERTIES:
-:CUSTOM_ID: addingmodules
-:END:
 
   As always, if the changes you wish to make are small, or you just want to add a few modules, you can clone and edit an editable install of HPI. See [[file:SETUP.org::*Adding/modifying modules][adding/modifying modules]]
 
diff --git a/doc/SETUP.org b/doc/SETUP.org
index e585645..79db04b 100644
--- a/doc/SETUP.org
+++ b/doc/SETUP.org
@@ -464,5 +464,4 @@ Also check out [[https://beepb00p.xyz/myinfra.html#hpi][my personal infrastructu
 # TODO eh. doesn't even have to be in 'my' namespace?? need to check it
 - The "proper way" (unless you want to contribute to the upstream) is to create a separate file hierarchy and add your module to =PYTHONPATH=.
 
-  See [[file:MODULE_DESIGN.org::#addingmodules][MODULE_DESIGN/adding modules]] for more information
-
+  See [[file:MODULE_DESIGN.org::*Adding new modules][MODULE_DESIGN/adding modules]] for more information